Ask what was agreed on a recorded call with a customer, and who took the actions.
Connect Grain with a personal access token and Memtro reads your meeting recordings with participants and tags, filtered by title, date, team or internal or external. One recording comes with Grain's AI summary, its action items and the speaker-labelled transcript. 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 tag and rename recordings, share them with people or teams, cut clips and build playlists. A public playlist is open to anyone with the link, and deleting a clip or playlist is permanent.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Grain tool, reads what it needs, and answers with the source cited.
These tools change something in Grain. 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, choose the kinds you want, and Memtro registers its address with Grain for you. Each event can start a job, with the event as its input. Grain signs nothing, so the long random address is the only check: treat it as a password.
Events and webhooksOnce Grain 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.
Grain + MemtroWhat did we agree on yesterday's call with Northwind?
Which action items came out of the BigCo renewal meeting, and who owns them?
What did Dan say about pricing in the Acme demo?
Share the Brightwave Ltd kick-off recording with the onboarding team
Make a clip of the two minutes where BigCo's buyer talks about budget
The account lead asks what was agreed on Tuesday's call with Northwind. Memtro finds the recording, reads Grain's summary and action items, and answers: a revised quote by Friday, owned by Priya Sharma, and a security review booked for next week.
The founder, Tom Becker, asks Memtro to send the product team what BigCo's buyer said about the budget. Memtro finds the pricing discussion in the transcript, cuts a two-minute clip from the recording and shares the recording with the product team in Grain, then gives him the clip's link.
The teams that lean on Grain most, a question each of them asks, and what they connect beside it.
A record in Grain 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
Missive
tl;dv
Fathom Video
ClickSend
OneSignal
Bird
MeetGeek
Sinch
Telnyx
Textmagic
SMTP2GO
MailerSend
InfobipIn grain.com open Account settings → Integrations → Personal API, generate a personal API token and copy it (it starts grain_pat_)
A personal token sees and changes only your own recordings and those shared with you. A Workspace Access Token sees every recording but needs a workspace admin on Business or Enterprise
In Memtro open Connections → Grain, paste the Personal access token and connect
Ask what was agreed on your last call with a customer
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Grain tools are the same everywhere.
Only when you ask, and only what it has been granted: add a tag to a Grain recording; remove a tag from a Grain recording; rename a Grain recording; share a Grain recording with a workspace user; share a Grain recording with a Grain team; cut a clip (highlight) from a Grain recording; delete a Grain clip, permanently; create a Grain playlist; rename a Grain playlist or change who can open its link; add a recording to a Grain playlist; delete a Grain playlist, permanently (its recordings stay). 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.
Personal access token. In grain.com open Account settings → Integrations → Personal API, generate a personal API token and copy it (it starts grain_pat_).
Yes. Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Grain for you. 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
