Integration
Connect Particle to Lettr
When New device event (instant) fires in Particle, your agent runs Add contact in Lettr. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Particle and Lettr to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What Particle can start in Lettr
When New device event (instant) in Particle
then Add contact in Lettr
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with Particle and Lettr
Triggers and actions 1 trigger · 16 actions
- New device event (instant)
Fires when a matching device event is published, delivered via a Particle webhook integration.
- Execute a logic function
Run a configured Particle Logic function and return its result.
- Get ledger instance
Retrieve the current data for a ledger instance (shared cloud/device key-value state).
- List devices
List all devices in your account or product fleet.
- Publish an event
Publish a custom event to the device cloud so other devices or integrations can subscribe to it.
- Set ledger instance data
Update the data stored in a ledger instance.
- Add audience list
Creates a new audience list in Lettr with the given name and returns the created list.
- Add contact
Adds a new contact to your Lettr audience, optionally placing it on a list, setting custom properties, and sending a double opt-in confirmation email.
- Add contact to list
Adds an existing contact to one of your audience lists. Succeeds whether the contact was newly added or was already on the list.
- Add template
Creates a new email template in Lettr from HTML or Topol editor JSON content, and publishes its first version with the merge tags found in the content.
- Delete contact
Permanently deletes a contact from your Lettr audience.
- Get contact
Returns a single audience contact, including its subscription status, custom properties, lists and topics.
- Get template
Returns a single email template by its slug, including its HTML, editor content, purpose, status and version details.
- List audience lists
Returns all audience lists in your Lettr team, with each list's name and contact count.
- List contacts
Returns the contacts in your Lettr audience, optionally narrowed by a search term, subscription status, list or segment.
- List templates
Returns the email templates in a Lettr project, optionally limited to one folder or to transactional or campaign templates.
- Update contact
Updates an existing contact in your Lettr audience, changing its email address, subscription status or custom properties. Fields left blank are not changed.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Particle
Particle to ImprovMXAPI for free email forwarding service
Particle to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Particle to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Particle to Google SheetsGoogle Sheets
Particle to StripeStripe is a payment processing platform for online businesses.
Particle to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
More into Lettr
HubSpot to LettrHubSpot is your all-in-one stop for all of your marketing software needs.
Gmail to LettrGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to LettrGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Particle and Lettr, answered
What can start an automation from Particle?
Any of Particle's 1 trigger in the catalog, including New device event (instant). Describe the moment in plain language and your agent picks the right one.
What can your agent do in Lettr when something happens in Particle?
Any of Lettr's 11 actions, including Update contact, Add audience list, Add contact and Add contact to list. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Lettr to Particle?
Lettr has no triggers in the catalog today, so automations start in Particle. If you need the other direction, ask: your agent reads Lettr's API documentation and adds it.
Do I have to build a connector for Particle or Lettr?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
Can my AI client use Particle and Lettr without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.