Guide 10 · Developer docs

Building forms with the Forms module: how a form is put together and placed on a page, validating and branching, presenting it, where submissions are stored, and what happens after one arrives, from jobs and records to CRMs and payments.

L1–L2

Unit 06 of 07 4 pages

Acting on a submission

Updated 23/10/2026 01:44

Everything that follows a submission is a job you build, under Customization › Orchestration (jobs were called hooks before the module was renamed). Starting one, creating records, pushing to a CRM and taking payments.

Start with starting a job on a submission and the two messages almost every form needs: a notification to staff and a confirmation to the person who wrote in, each built so that a reply cannot turn it into a spam relay. Creating records from a submission comes next, worked through in full for a person record, then a lead and a custom entity record.

Pushing to a CRM and taking payments both cover work a submission must survive even when another system cannot: an idempotent push that re-sends until the CRM confirms it, and a payment element whose settings do not always do what their names suggest.

In this unit

Read in order

01 Jobs, notifications and confirmations Starting a job when a form submission completes and what the job receives, then the two messages almost every form needs: a notification to staff, routed by an answer if need be, and a confirmation to the person who wrote in that cannot be turned into a spam relay. 02 Creating records from a submission The complete worked example of turning a submission into a person, without duplicates, step by step; then a lead, and a custom entity record created through the site's own API. 03 Pushing to a CRM Sending each submission to a CRM so that the CRM being down never fails or loses one: an idempotent push with retries, an hourly re-send that needs no state, and a daily check for anything still missing. 04 Taking payments Taking a donation, fee or deposit inside a form: where a form ends and a checkout begins, the setup, what a payment creates, and sending a receipt.

Objects ReferenceGenerated from the platform, so it is always current

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

Acting on a submission

In this unit