Integration · Email
AI agents for Buttondown
Run a Buttondown newsletter: find, add, update, unsubscribe and delete subscribers with tags and notes, list emails, draft, schedule or send a new issue, and read an email's opens, clicks and deliveries.
- Actions
- 8
- Read
- 4
- Write
- 4
Actions
What your agents can do in Buttondown
8 actions. Each one is a tool your agents can call and a step your workflows can run.
Read 4
Look things up. Nothing changes.
List subscribers
Lists subscribers, newest first, 100 a page, at results[].
Get a subscriber
Reads one subscriber by ID or email address: type, tags, notes, metadata, signup source and UTM fields, open_rate, click_rate, last_open_date, last_click_date and unsubscription details.
List emails
Lists the newsletter's emails, newest first, at results[]: each with id, subject, status (draft, scheduled, sent …), publish_date, absolute_url (the archive page), email_type and slug.
Get email analytics
Reads how an email did: recipients, deliveries, opens, clicks, unsubscriptions, complaints, replies, comments, temporary_failures and permanent_failures.
Write 4
Create, change or send.
Add a subscriber
Adds a subscriber by email address, with tags (created when missing), private notes and metadata.
Update a subscriber
Changes a subscriber found by ID or email address: replaces its tags, notes or metadata, changes its email address, or sets its type.
Delete a subscriberDeletes data
Permanently deletes a subscriber by ID or email address, with their history.
Draft, schedule or send an email
Creates a newsletter email with a subject and a Markdown or HTML body.
A person can approve first
Any write action can be set to wait for a person's approval before it runs, so an agent asks before it changes anything. Actions that delete data ask first by default.
Connection
How it connects
Connect it once in the console, then give it to the agents and workflows that need it.
Paste an API key from your Buttondown account.
What you enter
- API key
Kept safe
- Credentials are stored encrypted with your organization's own keys.
- They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
- Calls go only to the tool's own servers.
Ideas
Ideas to start with
Starting points made only from the actions above. Mix them with any other tool your agents can use.
- 01
Ask about your Buttondown data
Ask a question in plain words. The agent can list subscribers, get a subscriber or list emails in Buttondown, then answers with what it found.
- 02
Let an agent update Buttondown
Have the agent add a subscriber or update a subscriber in Buttondown as part of a larger task. Turn on approval and a person signs off on each change first.
- 03
Work from your CRM
Give one agent HubSpot and Buttondown: it can search contacts in HubSpot and add a subscriber in Buttondown in the same run.
FAQ
Buttondown and MyDeepAgents
Can MyDeepAgents connect to Buttondown?
Yes. The Buttondown connector has 8 actions: 4 read and 4 make changes. Your agents can call them as tools, and your workflows can run them as steps.
How do I connect Buttondown?
Paste an API key from your Buttondown account. You'll need: API key. Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.
Can an agent change data in Buttondown without asking?
Only if you let it. Each of the 4 actions that change data can be set to wait for a person's approval before it runs, and the one that deletes data asks first by default.
Can I use Buttondown in workflows as well as agents?
Yes. Every Buttondown action also works as a step in a workflow, and the same connection serves your agents and your workflows.
Early access
Put Buttondown to work
Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.