Automation

When something happens in a table, do something automatically: triggers, conditions, actions; scheduled tables; and the order to debug them in. A paid capability.

1. What automation isWhen something happens in a table — a row is added, a column changes, a time arrives — run an action: post a request, write into another table, send an email. Rules live on the table and the engine watches them. A paid capability.
2. Triggers: Data Added, Data Updated, Data Arrival TimeWhat each of the three triggers means, which column to point it at, which columns a trigger condition can reference, and how the before-and-after reminders on Data Arrival Time work.
3. Actions: Post to API, Submit to Table, Send EmailWhat 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.
4. Conditional actions: If … Conditions MetDifferent outcomes from one trigger — over 10,000 goes to the manager, otherwise to the rep. A conditional action branches one automation instead of making you build several.
5. Scheduled tables and self-growing datesA daily report with no gaps needs a date table that grows by itself. What datetime's real signature is (two arguments, seconds, minimum 3600), the fact that it does not work in the current desktop build, what to do instead, and where the scheduler stops on the desktop.
6. Debugging an automationNothing fired, it fired but no action ran, the email never arrived, the backfill never landed — a checklist in the order worth working through.