Integration
Connect Buttondown to Wachete
When something happens in Buttondown, your agent does the next thing in Wachete. 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 Wachete 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 Wachete
Triggers and actions 6 triggers · 36 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.
Trigger
Any new notificationFires when there is a new change notification from any monitor in your Wachete account.
Trigger
New notification for monitorFires when there is a new change notification from the specified Wachete monitor (taskId).
Action
Create monitorCreate a new Wachete monitor (wachet) that watches a web page or part of a page for changes.
Action
Delete monitorDelete a Wachete monitor by its ID.
Action
Get monitorGet information about a specific Wachete monitor by its ID.
Action
Get monitor dataGet the captured data/history for a Wachete monitor, optionally as a diff and within a date range.
Action
List foldersList folder contents, optionally under a parent folder.
Action
List notificationsList change notifications, optionally filtered by monitor (taskId) and date range.
Action
Update monitorChange the settings of an existing Wachete monitor — name, URL, watched/excluded XPath, regex, note, job type, check frequency and location, crawl options, folder, alerts, notification endpoints, headers and proxies. A partial update: the op first reads the monitor's current record, overlays only the fields you filled in, then writes the merged record back, so anything you leave blank keeps its current value — including settings this op does not expose. Identify the monitor by its id. Check frequency is in seconds (86400 = daily) and is ignored if not positive; the true/false options take the words true or false; alerts, notification endpoints, headers and proxies take JSON. Returns the monitor id, name and URL after the update plus the full monitor record.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.