Guide 09 · Developer docs

A job is a trigger, conditions and an ordered list of actions, set up under Customization › Orchestration in the admin; jobs were called hooks before the module was renamed, and the API's routes keep that name. What starts a job, what it can do, branches and loops, email, scheduled work, integrations with other systems, and every event and action.

L2–L3

Unit 07 of 08 4 pages

Jobs and other systems

Updated 23/10/2026 01:50

The patterns an integration engineer needs to connect a site to a CRM, an ERP, a warehouse or another system with jobs, ending with a complete integration to copy.

Begin with the catalogue: find your kind of system, its usual direction and cadence, and where its credentials live. The next two pages are the rules every integration follows: a retry policy that survives the other system being down, with dead letters that someone is told about, and field ownership, which keeps a two-way sync from looping. The last page puts all of it together: an order pushed to a fulfilment warehouse when it is paid and its status pulled back on a schedule, with idempotency, retries and a daily reconciliation.

The pages build on scheduled jobs, the previous unit, and on the HTTP Request action (HTTP request and response).

In this unit

Read in order

01 The integration pattern catalogue Find your case: the usual direction, cadence and pitfalls of a CRM, ERP, fulfilment, marketing automation, analytics or chat integration built from jobs, and where an integration's credentials live. 02 Retry, backoff and dead letters What a job retries by itself and what it does not, a retry policy with concrete intervals for when the other system is down, what happens to a request that exhausts them, and who is told. 03 Field ownership and two-way sync Decide per field which system is authoritative, record it, and enforce it in the jobs, so a two-way sync cannot fall into the update loop where two systems echo and overwrite each other's changes. 04 Worked integration: order fulfilment One complete integration built from five jobs: a paid order pushed to a warehouse with an idempotency key, a retry every 15 minutes, shipping status pulled back hourly with a watermark, and a daily report of dead letters and reconciled counts.

Objects ReferenceGenerated from the platform, so it is always current

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

Jobs and other systems

In this unit