Integration

Connect Buttondown to HelloSalut

When something happens in Buttondown, your agent does the next thing in HelloSalut. 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 HelloSalut to do together?

Ask the assistant

You'll sign in before anything runs. What you typed comes with you.

Examples

Pick one to fill the box, then change anything: the steps, the wording, even the apps. Go as long as you like.

Connect your AI client

Give your AI client this address.

https://mcp.apiant.ai

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.ai

Start 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)

Buttondown holds your drafts, scheduled emails and tags; HelloSalut returns the word for "hello" in a given language or for a visitor's IP. Joining them lets a newsletter that writes for readers in several languages pull the right greeting and write it into the email in Buttondown, without keeping a translation list of your own.

Example flows

What Buttondown can start in HelloSalut

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 HelloSalut

Triggers and actions 4 triggers · 30 actions

Each app on its own

Reviews

What our customers say

More from Buttondown

More into HelloSalut

Questions

Buttondown and HelloSalut, answered

How does the agent know which language to ask HelloSalut for?

It takes the language from something already in Buttondown, such as a tag name, a newsletter setting or a field on the draft, using Find Tag or Get Newsletter when it needs to read that value. HelloSalut then returns the hello for that language code.

Can the greeting be written back into the email itself?

Yes. After HelloSalut returns the greeting, the agent can use Update Email in Buttondown to put it into the draft's content or metadata, and it tests every scenario, including the case where no language is set.

What can start an automation from Buttondown?

Any of Buttondown's 4 triggers in the catalog, including New Draft, New Scheduled Email, Newsletters and New Tag. Describe the moment in plain language and your agent picks the right one.

What can your agent do in HelloSalut when something happens in Buttondown?

Any of HelloSalut's 1 action, including Get greeting. Your agent maps the data both ways and tests every scenario before it ships.

Can it also run from HelloSalut to Buttondown?

HelloSalut has no triggers in the catalog today, so automations start in Buttondown. If you need the other direction, ask: your agent reads HelloSalut's API documentation and adds it.

Do I have to build a connector for Buttondown or HelloSalut?

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.