Buttondown MCP integration for AI agents.
Connect AI agents to Buttondown through 12 structured actions, including get account, create subscriber, and delete subscriber. Review authentication, inputs…
- ACTION CONTRACTS
- 12
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Buttondown integration exposes
The Buttondown Agent App exposes 12 provider-backed actions for marketing and communication work. Its current contract lets an authorized agent get the account associated with the buttondown api key, create a buttondown subscriber, and delete a buttondown subscriber by id or email address. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Buttondown account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Buttondown capabilities.
Showing 12 of 12 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_accountREADGet the account associated with the Buttondown API key.
create_subscriberWRITECreate a Buttondown subscriber.
INPUTS: email_address / notes / metadata / tags / referrer_url
delete_subscriberHIGH IMPACTDelete a Buttondown subscriber by ID or email address.
INPUTS: id_or_email
create_tagWRITECreate a Buttondown tag.
INPUTS: name / color / description / public_description / subscriber_editable
delete_tagHIGH IMPACTDelete a Buttondown tag by ID.
INPUTS: id
get_subscriberREADRetrieve one Buttondown subscriber by ID or email address.
INPUTS: id_or_email
get_tagREADRetrieve one Buttondown tag by ID.
INPUTS: id
list_newslettersREADList newsletters available to the Buttondown API key.
INPUTS: page / page_size
list_subscribersREADList Buttondown subscribers with common filters.
INPUTS: page / email_address / type / tag / date__start
list_tagsREADList Buttondown tags.
INPUTS: page / page_size
update_subscriberWRITEUpdate a Buttondown subscriber by ID or email address.
INPUTS: id_or_email / commenting_disabled / email_address / notes / metadata
update_tagWRITEUpdate a Buttondown tag by ID.
INPUTS: id / name / color / description / public_description
INPUT CONTRACTS
Know what the action needs before it runs.
create_subscriber
email_addressREQUIRED- The email address of the subscriber.
notesOPTIONAL- Any private notes to attach to the subscriber.
metadataOPTIONAL- A structured key-value blob stored on the Buttondown object.
tagsOPTIONAL- Tag names to apply to the subscriber. Tags that do not already exist will be created.
referrer_urlOPTIONAL- The URL the subscriber was referred from.
delete_subscriber
id_or_emailREQUIRED- The Buttondown subscriber ID or email address.
create_tag
nameREQUIRED- The name of the tag.
colorREQUIRED- The hex color code associated with the tag.
descriptionOPTIONALpublic_descriptionOPTIONALsubscriber_editableOPTIONAL- Whether subscribers can add or remove this tag from their own profile.
delete_tag
idREQUIRED- The Buttondown tag ID.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Account
Get the account associated with the Buttondown API key. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_accountControl Create Subscriber
Create a Buttondown subscriber. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_subscriberVerify with Get Subscriber
Retrieve one Buttondown subscriber by ID or email address. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_subscriberSAFETY BOUNDARY
Operate Buttondown with explicit limits
- Authorize Buttondown with API key and grant only the provider access required by the selected actions.
- 6 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_subscriber` and `delete_tag` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Buttondown rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Buttondown task completed successfully.
CONNECTION MODEL
API key
Buttondown API key passed as Authorization: Token <api_key>. Find it on the Buttondown API requests page: https://buttondown.com/requests.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 6
- WRITE SIGNALS
- 4
- HIGH IMPACT
- 2
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Buttondown.