What starts a job

01 Entity events An entity event starts a job when a record is created, updated or deleted, or when one of a few entities reports something of its own. When each one fires, what the run receives, what an update can see of the previous values, and the records whose changes start nothing.

02 Web events and schedules The two triggers that are not about a record: a web event gives a job a URL for another system to call, and a schedule runs it on the clock. What each run receives, how schedules are set and in which timezone, and what happens when a run is still going as the next one comes due.

03 Chaining one job to another A Trigger job action starts a second job and hands it data. How the second job runs depends on its own synchronous setting, what it receives, how a failure travels back or does not, and when two jobs are better than one.

04 Guarding against recursion A job that updates a record on that record's update event can start itself again. Which writes raise events on this platform and which do not, the four ways a loop actually forms, and the guard that stops it: a condition on the field that changed.

05 Choosing a trigger A decision table from the moment you have in mind to the trigger that serves it, including the cases where no event fires and the answer is a scheduled job.

Objects ReferenceGenerated from the platform, so it is always current

API ReferenceEvery REST endpoint, in cURL, PHP, Python and JavaScript

In this unit