Email agents
can act on.
MailSchema is building an open standard for agents to work with services through email. Messages describe the available actions, so compatible agents and inboxes can take the next step.
Mail Action Protocol · Working Draft 0.1There’s work
in your inbox.
A draft needs feedback. A service needs an answer before it can proceed. MAP gives those requests a structure that agents can recognise, alongside the email people already read.
A request arrives
The message identifies the work and the actions available. For a draft, that might mean requesting changes or approving a particular revision.
Content Review · Revision 3Your agent responds
A compatible agent submits the request to the service, using the permissions you have given it. You can also follow the link and handle the review yourself.
Request changes on revision 3The service confirms
The result tells the agent what happened. Feedback might have been recorded, approval might still be needed, or the draft might have changed since the email arrived.
Feedback recorded for revision 3Describe it once.
With a shared type, a review request has the same meaning across services. Agent and inbox developers can build support for that interaction while each service handles its own permissions and underlying work.
MAP defines how the message describes the action, how a client requests it and what the result means.
Read MAP 0.1Take a draft
through review.
A campaign test email arrives for review. Request a change, create the next revision and approve it. Try the exchange below to see what the person reads and what the agent receives.
Read the type definitionA type gives the request its meaning.
Content Review tells a client how to handle feedback and approval. Other types can describe other kinds of work. Each definition sets out the actions, the information they need and the results a client can expect.
Types
Learn how a type describes an interaction, how it relates to MAP and when an existing definition fits your workflow.
About interaction types Browse the RegistryRegistry
Read type definitions and examples, follow their revisions and see the proposals under discussion. Implementation details belong with the type they support.
Browse type definitionsPropose a type
for your workflow.
If your service asks people to do something by email, describe the exchange. A useful proposal shows what a client needs to know and how the same interaction could work in another service.
Prepare a type proposal