Retrieve Automation
Retrieve a specific automation by its ID
Path parameters
Response
OK
A unique TypeID associated with the object.
The date and time at which the object was first created.
The name of the automation.
An enumeration.
Various types of events that are recorded by Buttondown, both in terms of exogenous systems like Stripe and Memberful, and endogenous ones like email opens and clicks. (In general, if anything important ever happens that could be relevant to your newsletter, we have an event type for it!)
These event types power lots of things within Buttondown. They're used to trigger automations, webhooks, and analytics.
(Note that Buttondown also has a different thing we call "events"; those are EmailEvents and are used for tracking aggregate details about an email. Alas, we shouldn't have used the term "event" for two different things, but it's too late to go back now!)
In general, our event namespacing tries to hew to the following pattern:
<source>.<object>.<action>
When wondering which object we are referring to, default to the more granular object.
For instance, an email being sent to a subscriber is subscriber.delivered, not email.sent.
Additional metadata for the automation.
If true, filters are re-evaluated after the delay has passed.