Automations

An automation is work Sterodata repeats for you: read a list from a connected API, write it into a table, or send a change to the API. You set it up once, and it runs when you press Run, when someone presses its button on a table, or on a schedule.

Each automation has:

• A trigger: what starts it. See Triggers.
• Steps: what it does, in order. A step can use what an earlier step produced. See Create an automation.
• Runs: a record of each time it ran, step by step. See Runs and their history.

Automations work with the APIs you have connected: each step reads from or calls a connected API, reshapes the rows an earlier step read, or writes them into a table. Connect the API first.

Who can make them

Automations live under Settings, in the Automations tab. Only workspace admins see it. Anyone who can edit a table can press an automation's button on that table, once an admin has added one.

What an automation may touch

An automation writes only to the tables it was given when it was saved, and calls only the connections it was given. Saving gives it exactly what its steps use, and only what the person saving may do themselves: if you cannot write to a table, you cannot save an automation that writes to it, and Sterodata names the table. The editor shows the result under the description, as May write to and the tables' names. Because the automation holds this itself, it keeps working after the person who made it leaves the workspace.

In this section

• Create an automationMake an automation under Settings, add its steps in order, choose what happens when a step fails, and save it.
• TriggersWhat starts an automation: the Run button, a button on a table, or a schedule of minutes, hours, days or weeks, or a custom expression.
• Runs and their historyHow to start a run, read how it went step by step, and whose name the changes a run makes carry.