Team inbox conversations, internal comments and tasks in Missive, by mailbox, label or customer.
Connect Missive with your API token and Memtro reads conversations by mailbox, label, team or contact, a conversation's latest messages and internal comments, contacts, tasks, users and teams. It sees what you can see in Missive. It reads on demand and there is no hourly sync. When you ask, and once an administrator has granted the action by name, it can send or schedule emails, SMS and WhatsApp messages, create drafts, posts, contacts and tasks, close, assign, label or merge conversations, and update tasks. Sent messages reach people outside the company and cannot be recalled, and merging is permanent.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Missive tool, reads what it needs, and answers with the source cited.
These tools change something in Missive. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Missive, choosing the same kinds; the tab shows Missive's own steps. Each event can start a job, with the event as its input. Missive signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Missive is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
Missive + MemtroWhat conversations are open under the Clients/Acme label?
What has anyone at brightwave.co.uk sent us this month?
Which tasks are due this week, and who are they assigned to?
What did the team say internally about the Northwind contract?
Reply to the BigCo thread that the revised quote follows on Friday
Back from leave, the account manager asks what happened with Northwind. Memtro reads conversations from the northwind.com domain, the latest messages and the team's internal comments on each, and answers with what was agreed and what is still open.
Support reads a complaint from Acme and asks Memtro to follow it up. Memtro adds an internal post on the conversation with the agreed next step, creates a task for Dan Fletcher, and drafts a reply for Priya Nair to review and send. Missive notifies the members and Dan.
The teams that lean on Missive most, a question each of them asks, and what they connect beside it.
A record in Missive is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
AgentMail
Fireflies.ai
SendGrid
Avoma
tl;dv
Grain
Fathom Video
ClickSend
OneSignal
Bird
MeetGeek
Sinch
Telnyx
Textmagic
SMTP2GO
MailerSend
InfobipMissive API tokens need an organisation on the Productive plan
In Missive open Preferences → API, create a new token and copy it, and the token acts as you
In Memtro open Connections → Missive, paste the API token and connect
Ask what is waiting under a shared label
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Missive tools are the same everywhere.
Only when you ask, and only what it has been granted: add an internal post to an existing conversation; create a contact in a contact book; create a task, in a conversation or for a team or teammates; send or schedule an email, SMS or WhatsApp message to named recipients, new or as a reply; create a draft message for a person to review and send from Missive; close, reopen, rename, recolour, assign, label or move a conversation; change a task's title, description, state, assignees, team or due date; merge one conversation into another, permanently; delete a draft, or cancel a scheduled send; delete an internal post from a conversation. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
API token. Missive API tokens need an organisation on the Productive plan.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Missive, choosing the same kinds; the tab shows Missive's own steps. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time
