Guide 09 · Developer docs

Automation, jobs and integration

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 03 of 08 6 pages

What a job does

Updated 23/10/2026 01:49

The actions: records, HTTP, rendered output and email, files and PDFs, stopping, and AI agents. A working configuration for each, what it leaves for later actions, and how it fails. For anyone building a job's action list.

Read Record actions first: finding, creating, updating and deleting records is the core of most jobs, and it explains the API models every other action works with. HTTP request and response is what makes integration possible, with the default that stops most first attempts. Render template and send email covers the action that unlocks the most, producing CSV, JSON or HTML from the theme repository, and the Send Email action; the email work itself is the unit after next.

Files, PDFs and certificates saves and combines what a job produced. Stopping a job early says exactly what a stop leaves behind, and AI agent actions what an agent is for and what it costs.

In this unit

Read in order

01 Record actions Retrieve Records, Create Record, Update Record and Delete Record: a working configuration for each, how fields are mapped from the event and earlier actions, which entities each can reach, and the failures that surprise people. 02 HTTP request and response The HTTP Request action calls another system: method, URL, headers, body, timeout, retries and the status codes it accepts, and what it leaves for later actions. The HTTP Response action answers a synchronous web event, with a success or a structured error. 03 Render template and send email Render Template turns a template from the theme repository into text a later action uses: a CSV export, a JSON payload, an email body, a certificate's markup. Send Email queues a message from a template. How each is configured, what it leaves, and where it fails. 04 Files, PDFs and certificates Create File saves output into the file manager, Merge Files joins files end to end, and Merge PDFs joins PDFs into one. Where the files go, how long they last, what each action can take as input, and a certificate built from all three. 05 Stopping a job early The Stop execution action ends a run, or one loop iteration, with the status you choose. When it takes effect, which actions still run after it, what it leaves behind, and what a web caller receives. With Trigger job, the action that starts another job. 06 AI agent actions The AI Agent action hands a task to an installed agent, with the run's data as its input. What it is for, what it leaves, where it cannot be used, and the cost model a site builder needs before putting one on a busy event.