Letta Zapier integrationAutomate Letta with Zapier.
The Letta Zapier integration offers 3 triggers, 3 actions and 1 search. Your AI agents can talk to the rest of your tools: what they say can leave Letta, and messages, new agents and identities can be pushed in. All three triggers poll, so your plan sets the pace.
Verified Trustpilot reviews · AI, automation & growth agency
What the Letta Zapier integration is for
Letta is a platform for building, running and watching AI agents. Through Zapier, those agents stop living in a closed room: their messages, new agents and new projects can start work in other tools, and other tools can message an agent, spin up a new one from a template or register an identity in Letta.
An agent's answers where your team reads. New Message picks up what a chosen agent sends. Post it to your team chat and people see the output without opening Letta.
Agents fed by your other tools. Send Message to Agent passes content from another app to an agent, with the role you pick. A request that lands somewhere else can reach the agent directly, without anyone copying it over.
New agents on demand. Create Agent From a Template builds an agent from a template version inside a project, so a fresh agent can appear when something happens elsewhere.
What Zapier does not do for Letta: there is no instant trigger, so on the free plan a message can wait up to 15 minutes before the Zap sees it. There is no action to update or delete an agent, and the only search looks up identities, not agents or messages. Before building anything serious on this, read our Zapier review to judge whether the platform fits your setup.
Zapier vocabulary in one minute
Eight Zapier words come back on this page. Here they are once, in plain English.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run each time the trigger event happens.
- Trigger
- The event in an app that starts the Zap, such as a new agent. Once the Zap is on, Zapier waits for it.
- Action
- What the Zap does after it starts: the step that writes, sends or creates something on your behalf.
- Task
- The unit Zapier bills: one action your Zap completes successfully. Your plan's allowance is a count of these.
- Polling trigger
- A trigger Zapier checks on a timer: it asks the app for new items at a fixed interval and keeps only unseen ones.
- Filter
- A step that lets the Zap go on only when the incoming data meets the condition you set, and stops it otherwise.
- Search step
- A step that looks up something already in an app, so the steps after it can use what it found.
- Connection
- Your Letta account linked to Zapier once, then reused by every step that works with Letta.
What it really costs
Letta is not a premium app, so it runs on the free plan. You pay in tasks, and only for completed actions.
- Premium appNo, works on the free plan
- Free plan100 tasks a month, two-step Zaps
- Triggers3, all polling, free
- Each successful action1 task
The three triggers never cost a task, and neither do Zapier's regular checks on Letta, however often they run. Each action that goes through counts as one task; a failed one is not counted. The free plan gives 100 tasks a month and two-step Zaps only: one trigger, one action. A filter, a second action or a Get Identities step turns it into a multi-step Zap, which needs a paid plan. Because every Letta trigger polls, your plan also decides how quickly the Zap notices a new agent, project or message.
Connect your Letta account
- 01
Open your connections
In Zapier, go to the Apps page of your account and click + Add connection. You need an existing Letta account first, with access to the agents and projects the Zap will touch.
- 02
Pick Letta
Type the app's name in the dialog that appears, select Letta in the results, then click Add connection. A new browser tab opens on the Letta side to finish.
- 03
Sign in and grant access
Log in to Letta in that tab and allow Zapier to use the account. If the agents or projects the Zap will touch belong to someone else, check that your login can reach them.
Your first Zap: post an agent's messages to your team
GoalEach message a chosen Letta agent sends that meets your condition is posted to your team chat.
- 01
Pick the trigger
Create a Zap, choose Letta as the app that starts it and New Message as the event. Select your connection, then paste the Agent ID of the agent to watch.
- 02
Test with real messages
Run the test. Zapier brings back the three most recent messages from that agent, so you map the next steps on real output rather than a blank sample.
- 03
Add the filter
Click the plus icon, add Filter and fill the three boxes: the field to look at, the rule, the value. A text rule for text, a number rule for numbers.
- 04
Post to the chat
Add your chat tool as the action and drop the message content from the test into the post. The filter makes this a multi-step Zap, so a paid plan is required.
- 05
Test, then publish
Run each step once and check the post as it lands in your chat channel. When it looks right, click Publish to switch the Zap on.
The 3 Letta triggers
3 events start a Zap when something happens in Letta. Zapier checks for them at the interval your plan allows.
New Agent
Polling triggerIn Zapier“Triggers when a new agent is created”
Notices each agent created in your Letta account and passes it to the rest of the Zap, so the people who need to know hear about it.
New Message
Polling triggerIn Zapier“Triggers when an agent uses send_message.”
Fires when the agent you name sends a message, which turns what the agent says into something other tools can use.
New Project
Polling triggerIn Zapier“Triggers when a project is created.”
Picks up each project created in Letta, the container where agents and templates live, and hands it to the next steps.
The 3 Letta actions
Letta gives you 3 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Create Agent From a Template
ActionIn Zapier“Creates an agent from a template”
Builds a new agent from the template version you choose, inside the project you name.
Create Identity
ActionIn Zapier“Creates a Letta identity”
Registers a Letta identity from outside data, with an identifier key of your own, a name and an identity type, all required.
Send Message to Agent
ActionIn Zapier“Send message to an agent.”
Delivers content from another app to a Letta agent, with the message role you set. Agent ID, content and role are all required.
The Letta search
1 search step looks for data that already exists in Letta, so a later step can use it.
A search step looks up something already in Letta and hands it to the following steps. In the editor, searches sit at the bottom of the Action event list, under SEARCH. Three settings decide what happens when the result is not one clean match.
Get Identities
SearchIn Zapier“Searches for identities in your Letta Project”
Looks up identities inside one Letta project and passes them to the next steps, so a later action can reuse an identity that already exists.
The three settings every search exposes
- Successful if no search results are found?Left on its default, a search that finds nothing stops the Zap there and the steps depending on it are skipped. Switched on, the Zap carries on empty-handed.
- Create X if it doesn't exist yet?Ticking this box would turn the search into a find-or-create. Letta offers no such variant on Zapier, so Get Identities only ever looks.
- If multiple search results are found?Three ways out: keep the first match, which is the default, stop the Zap, or pass every match on at once.
When it breaks
Zapier attaches no help article to Letta and documents no limit of its own. What breaks comes from Zapier's rules for polling triggers and from the required IDs of the actions.
Six cases come back. None shows up while you build, which is why they surprise. When a run fails, start from our Zapier troubleshooting page and the task history of the Zap.
Old agents and messages never arrive
A Zap only reacts to what happens after it is published. Agents, projects and messages created before stay where they are.The message shows up late
All Letta triggers poll. On the free plan Zapier checks every 15 minutes, so an agent's message can wait until the next check.The agent talks to itself
New Message followed by Send Message to Agent on the same agent: each reply is a new message, which starts the Zap again and burns tasks.A burst of items is held back
If a bulk import or a migration suddenly creates a huge batch of items, Zapier's flood protection can hold that batch back.The Agent ID is wrong
New Message and Send Message to Agent need the exact Agent ID. A wrong one means nothing is watched, or the message goes nowhere.The same item never runs twice
Zapier remembers what it has seen on a polling trigger, so an agent, project or message that already started the Zap will not start it again.
Need help automating Letta with Zapier?
A person reads every message.
