Automation & Webhooks
Every accepted submission can set more work in motion: the form's own workflows, an inbox card for staff, and webhook calls to other systems. This page covers what is specific to forms; see Automation for the workflow builder itself.
| Mechanism | Set up on | Runs for |
|---|---|---|
| Form workflows | The form's Automation tab | Submissions of that form |
| Inbox card | Always on | Every submission of every form |
| Webhook subscription | Automation > Webhooks | Every submission of every form |
Form Workflows
The Automation tab lists the form's workflows. It is shown to staff with automation access, which forms.forms_access includes. Creating a workflow or opening one shows it in the workflow builder; the back arrow returns to the form.
A form workflow is always started by a submission of the form: its trigger is fixed. Conditions can test the submitter's profile fields or the form's own fields, so a workflow can act only on, for example, submissions that chose a given programme.
Steps
| Step | What it does |
|---|---|
| Wait | Holds the profile for a set time or until a date, then continues. |
| Send email | Sends an email to the profile from a template. |
| Notify staff of the submission | Emails a staff member the answers submitted on the form. Replies go to the submitter. |
| Send SMS | Sends a text message to the profile's phone number. Needs SMS for your institution. |
| Add to product | Adds the profile to specific products, or to those picked on the form. |
| Add to product by name or ID | Adds the profile to the products an answer names, by name or ID. |
| Add tag | Adds one or more tags to the profile. |
Exits
A form workflow stops for a profile when All actions have been completed, or earlier when the exit is set to Profile starts any application or Profile submits any application.
Note: Duplicating a form copies its workflows to the new form.
Inbox Cards
Every submission creates a form card in the staff Inbox, showing the submitter, the form, and the answers. Tasks can be linked to a form submission from the card.
| Who | Gets |
|---|---|
| All active staff and administrators | The card in their inbox. |
| The owners of the profile's journeys, and staff following the profile | A notification as well, unless their data access scope excludes the profile. |
Deleting a person's last submission to a form removes the card. See Submissions.
Webhooks
A webhook sends each submission to another system as it happens. Webhooks are set up under Automation > Webhooks, by staff with automation access.
- Click Create subscription.
- Choose the Event type Form submission.
- Enter the Webhook URL, starting with
http://orhttps://, and click Create.
A subscription cannot point at a cloud metadata or link-local address, and the same URL can only be subscribed to an event type once.
Note: A form submission subscription fires for every form. To act on one form only, filter on
form_idin the receiving system.
Payload
Full Fabric sends an HTTP POST with a JSON body that includes:
| Key | Content |
|---|---|
| One key per form field | The answer, keyed by the field's name, such as first_name or email. |
form_id, submission_id |
The form and the submission. |
profile_id, user_id |
The profile the submission belongs to (both carry the same ID). |
ip |
The IP address the submission came from. |
created_at, updated_at |
When the submission was stored. |
tenant |
Your institution's handle. |
event_type |
automation.forms.submissions. |
Delivery
Each call waits up to 10 seconds for an answer. When the receiving system cannot be reached or answers with a 5xx status, Full Fabric retries twice, after 5 and then 15 seconds. Any other answer, including a 4xx status, ends the delivery. Every attempt, with its request and response, is listed on the Activity tab of Automation > Webhooks.
Related
- Automation for the workflow builder and webhooks across the platform
- Submissions for what a submission writes to the profile