Integration
Connect Buttondown and Trengo
When something happens in Buttondown or Trengo, your agent does the next thing in the other. Describe it 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 Buttondown and Trengo to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny 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 Buttondown and Trengo can do together
From Buttondown to Trengo
When New Draft in Buttondown
then Add internal note to ticket in Trengo
When New Scheduled Email in Buttondown
then Add ticket in Trengo
From Trengo to Buttondown
When New Internal Note in Trengo
then Add Segment in Buttondown
When New Outbound Message in Trengo
then Add Survey in Buttondown
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 Buttondown and Trengo
Triggers and actions 7 triggers · 44 actions
Trigger
New DraftTriggers when a new draft is created.
Trigger
New Scheduled EmailTriggers when a new email is scheduled.
Trigger
NewslettersTriggers when a new newsletter is created.
Trigger
New TagTriggers when a new tag is created.
Action
Add SegmentCreate a new subscriber segment.
Action
Add SurveyCreate a new survey.
Action
Create DraftCreates a draft.
Action
Create EmailCreates an email.
Action
Create SubscriberCreates a subscriber.
Action
Delete AutomationDelete an automation by id.
Action
Delete EmailDelete an email by id.
Action
Delete NewsletterDelete a newsletter by id.
Action
Delete SegmentDelete a subscriber segment by id.
Action
Delete SubscriberRemove a subscriber by id or email address.
Action
Delete SurveyDelete a survey by id.
Action
Delete TagDelete a tag by id.
Action
Find TagFinds a tag given its name.
Action
Get AutomationRetrieve a single automation by id.
Action
Get EmailRetrieve a single email by id.
Action
Get NewsletterRetrieve a single newsletter by id.
Action
Get SegmentRetrieve a single subscriber segment by id.
Action
Get SurveyRetrieve a single survey by id.
Action
Get TagRetrieve a single tag by id.
Action
List AutomationsList all automations configured on the account.
Action
List SegmentsList all subscriber segments.
Action
List SurveysList all surveys on the account.
Action
Publish EmailPublish a drafted email so it is sent and made public.
Action
Update AutomationUpdate an automation's configuration.
Action
Update EmailUpdate an existing email's content or metadata.
Action
Update NewsletterUpdate a newsletter's settings.
Action
Update SegmentUpdate a subscriber segment's definition.
Action
Update SurveyUpdate a survey's configuration.
Action
Update TagUpdate a tag's name or metadata.
Trigger
New Internal NoteFires when an internal note is added to a Trengo ticket.
Trigger
New Outbound MessageTriggers when an outbound message is created.
Trigger
Ticket Label AddedTriggers when a label is added to a conversation.
Action
Add internal note to ticketAdds an internal note (visible only to agents) to a Trengo ticket.
Action
Add ticketCreate a new support ticket.
Action
Add ticket labelAttaches an existing label to a Trengo ticket.
Action
Create a ContactCreates a contact on a Trengo channel. If a contact with the same identifier already exists on that channel, Trengo returns the existing contact instead of creating a duplicate.
Action
Create webhookSubscribes a URL to one Trengo webhook event type. Used by Trengo instant triggers to register their delivery URL on activation.
Action
Delete contactDelete a contact by id.
Action
Delete ticketDelete a ticket by id.
Action
Find a ContactReturns the Trengo contacts that match the search term.
Action
Get contactRetrieve a single Trengo contact by its id.
Action
Get webhookFetches a webhook by ID, including the event it listens for, the address it sends to and its signing secret. An error occurs if the webhook is not found.
Action
List contactsList all contacts.
Action
List labelsLists the ticket labels defined in the Trengo account (first page).
Action
List ticketsReturns all tickets the connected user is authorized to see, optionally filtered by status, contact, users, channels, labels, last message type or update time.
Action
Send a MessageSends a reply message on an existing Trengo ticket, over the ticket's own channel.
Action
Update contactUpdate an existing contact by id.
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 Buttondown
Buttondown to HelloSalutHelloSalut returns the word for "hello" in a visitor's own language.
Buttondown to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Buttondown to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Buttondown to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Buttondown to Google SheetsGoogle Sheets
Buttondown to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
More into Trengo
HubSpot to TrengoHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to TrengoSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to TrengoSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to TrengoGoogle Sheets
Gmail to TrengoGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to TrengoGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Buttondown and Trengo, answered
What can start an automation from Buttondown?
Any of Buttondown's 4 triggers in the catalog, including New Draft, New Scheduled Email, New Tag and Newsletters. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Trengo when something happens in Buttondown?
Any of Trengo's 15 actions, including Create a Contact, Create webhook, Send a Message and Update contact. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Trengo to Buttondown?
Yes. When something happens in Trengo, your agent can act in Buttondown too. This page covers both directions: Trengo's triggers and Buttondown's actions are listed here as well.
Do I have to build a connector for Buttondown or Trengo?
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.
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.