Integration
Connect Buttondown to Brand.dev
When New Draft fires in Buttondown, your agent runs Find rows in a collection in Brand.dev. 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 Buttondown and Brand.dev 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 Buttondown can start in Brand.dev
When New Draft in Buttondown
then Find rows in a collection in Brand.dev
When New Scheduled Email in Buttondown
then Add a monitor in Brand.dev
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 Brand.dev
Triggers and actions 4 triggers · 48 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.
Action
Add a monitorCreate a website change monitor.
Action
Delete a collectionDelete a WebDBs data collection.
Action
Delete a monitorDelete a website change monitor.
Action
Extract Products From a Brand's WebsiteBeta feature: Extract product information from a brand's website. Brand.dev will analyze the website and return a list of products with details such as name, description, image, pricing, features, and more.
Action
Find rows in a collectionQuery rows stored in a WebDBs data collection.
Action
Get a batchRetrieve a batch's status by ID.
Action
Get a monitorRetrieve a website change monitor by ID.
Action
Get batch resultsRetrieve the results of a completed batch.
Action
List batchesList submitted batches.
Action
List collectionsList WebDBs data collections.
Action
List monitorsList website change monitors.
Action
Query Website Data Using AIUse AI to extract specific data points from a brand's website. The AI will crawl the website and extract the requested information based on the provided data points.
Action
Retrieve Brand Data by Company NameRetrieve brand information using a company name. This endpoint searches for the company by name and returns its brand data.
Action
Retrieve personRetrieve a person's profile data.
Action
Retrieve Simplified Brand Data by DomainReturns a simplified version of brand data containing only essential information: domain, title, colors, logos, and backdrops. This endpoint is optimized for faster responses and reduced data transfer.
Action
Run a monitorTrigger a website change monitor to run immediately.
Action
Search company newsSearch for recent news articles about a company or brand.
Action
Update a collectionUpdate a WebDBs data collection's configuration.
Action
Update a monitorUpdate a website change monitor's configuration.
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 Zoho CampaignsZoho Campaigns lets you send email and social media campaigns to your subscribers.
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 is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
More into Brand.dev
HubSpot to Brand.devHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to Brand.devSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to Brand.devSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to Brand.devGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to Brand.devGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Brand.devGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Buttondown and Brand.dev, 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 Brand.dev when something happens in Buttondown?
Any of Brand.dev's 19 actions, including Update a collection, Update a monitor, Add a monitor and Extract Products From a Brand's Website. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Brand.dev to Buttondown?
Brand.dev has no triggers in the catalog today, so automations start in Buttondown. If you need the other direction, ask: your agent reads Brand.dev's API documentation and adds it.
Do I have to build a connector for Buttondown or Brand.dev?
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 Buttondown and Brand.dev 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.