We now have a beta for the Letta x Zapier integration! This should make it significantly easier to handle agent orchestration and data ingestion.
You can jump into the beta here.
Zapier makes it easy to build automation. It is composed of triggers and actions. Triggers are used to make an action run, such as receiving an email, a Letta agent generating a message, a new calendar invite arriving, etc. Actions are what you do in response to that trigger – in our case, it is mostly used to send an agent a message.
Triggers
We currently support three triggers:
- New agent message. Any time your agent generates a tool call or sends a message, you can pipe messages into any other Zapier action, such as sending an email, making Notion pages, etc.
- New project. Triggers when a new project is made. We use this primarily internally, but let us know if it’s of use to you.
- New template. If a new template is made, you could potentially spin off new agents from the template. This is also primarily internal.
Actions
- Send message to agent, async. This is the primary action you should use – you can send any text to your agent, using information from whatever is in your trigger (such as email addresses, email body, etc.)
- Creating an agent from a template. This is useful if you get an email from a new customer – just create a new CRM agent from an established template.
- Create an identity. Useful for the same reason – new user, create an identity containing their information, and then all new agents can be assigned to that identity.
- Search identities. Useful for checking if something already has an identity, i.e. if you’ve already seen this user before.
Feedback
If you have any actions or triggers you’d like to see, let us know! We hope the Zapier integration helps you move to more passive and useful agents that connect to more of the data you have accessible.