Integration
Connect Buttondown to Amplitude
When something happens in Buttondown, your agent does the next thing in Amplitude. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Buttondown and Amplitude to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with Buttondown and Amplitude
Triggers and actions 4 triggers ยท 41 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
Batch upload eventsSends a batch of events to Amplitude in one call. Use this when you have many events to record at once rather than one at a time.
Action
Export event dataExports every event Amplitude recorded in a time window, as a zip archive of event data.
Action
Get cohortReturns one behavioral cohort's details, including its name, size and when it was last recalculated.
Action
Get event segmentationCounts how often an event happened over a date range, optionally split by a property or filtered to a segment of users.
Action
Get funnel analysisRuns a funnel over a series of events and returns how many users reached each step and how many dropped off.
Action
Get retention analysisShows how many users came back and did something again after a starting event, over a date range.
Action
Get user propertiesLooks a user up in Amplitude and returns what Amplitude knows about them, including their Amplitude ID.
Action
Group identifySets properties on a group in Amplitude, such as a company or team, so you can analyse behaviour by group.
Action
Identify userSets properties on a user in Amplitude without recording an event, so later events are attributed with the new details.
Action
List cohortsLists every behavioral cohort in the Amplitude project, with each cohort's name, size and owner.
Action
Send eventRecords a single event in Amplitude for a user, with optional event and user properties.
Action
Upload cohortCreates a cohort in Amplitude from a list of users you supply.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.