Actions: Post to API, Submit to Table, Send Email
What happens after a trigger. The fields each of the three actions wants — target URL and headers, content and backfill, target table and mapped values, recipients and the email template. One automation can carry several actions.
Post to API
Sends the triggering row to an endpoint as JSON.
| Field | What goes in |
|---|---|
| Enter Target URL | The receiving address (placeholder Enter URL; URL Required if empty) |
| Set Headers | Authentication and the rest — Add Headers adds them one at a time |
| Set Content | Which of this row's columns go out as fields |
| Add Response Data | Add Backfill Data: which field of the response is written into which column of this row (Select Target Field). Send an order, get a tracking number, write it into the tracking column |
This is the event-shaped form of writing back to an external system.
Submit to Table
Writes the triggering row's content into another table.
| Field | What goes in |
|---|---|
| Target Table | Where it goes (Select Table; Select a Table if empty) |
| Submitted items | Which column of the target (Field Name) takes which value from this row (Field Value), one pair at a time |
For: writing a row into a "to be processed" table when an order arrives; writing into an archive table when a status becomes done. If the target table has a unique index, a matching index updates instead of appending.
Send Email
| Field | What goes in |
|---|---|
| Recipient | Enter Email — Separate emails with semicolons — or Select from Data, taking the address from a column of this row so each row goes to its own owner |
| Subject | Defaulted from the trigger type: Warning: Exception Detected, Data Arrival Notification or Status Change Detected. Editable |
| Message | The available placeholders are New Value Added:, New Time:, Triggered At:, Latest Value:, Original Value:, Exception Time: and Please Address Promptly — replaced with this row's real values when it sends |
Email leaves from wherever the engine is running: the cloud service on the team edition, and your own environment on the desktop app — test it.
Several actions
Add Action hangs more than one action off the same automation, run in order: write into the to-do table, then send the email. Each is saved separately — an unsaved one says Save the Action First.
Where an action's values come from
Everything an action references comes from the row that triggered it: the content fields, the mapped values, the recipient column, the email placeholders — all read from that row at the moment of the trigger. For anything that spans rows (a running monthly total, say) compute it into a column of this row with a formula first, then reference that column.