Global Automations

Create automations at site level and control which forms they run for.

PRO Last reviewed

A Global Automation is created once at site level and can run for any form on the site. Use one when several forms need the same behavior, such as sending every lead to the same CRM endpoint or notifying the same internal address.

Automations are available in Elzo Forms PRO.

Create a Global Automation

  1. Go to Forms → Settings → Automations.
  2. Click Create Automation.
  3. Give it a Title that says what it does, such as Send leads to CRM.
  4. Add conditions if the automation should only run for some forms or some submissions. Leave the conditions empty to run it for every form.
  5. Click Add action and configure the actions it should perform.
  6. Click Check workflow to validate the configuration.
  7. Click Save Automations.

A Global Automation with no conditions runs for every form on the site as soon as it is saved. Add at least one condition if that is not what you want.

Limiting where a Global Automation runs

There are two ways to narrow the scope, and they work differently.

Conditions are evaluated for each submission at runtime. They are the right tool for rules about the submission itself — the form it came from, the values submitted, whether the visitor was logged in, which page the form was on.

To restrict an automation to specific forms, add a condition, set its data source to Data reference, and enter the path form.id or form.key. A condition on a submitted field restricts it to specific answers instead.

Per-form toggles are set by whoever edits an individual form and take effect before conditions are evaluated. They are the right tool when a form should opt out entirely.

Control Global Automations from a form

Every form’s automations screen lists the site’s Global Automations under Global automations. They are shown read-only there — the settings themselves can only be changed at site level — but each one can be switched off for that form.

  • Clear Enable for this form on a single Global Automation to skip just that one.
  • Select Disable all global automations for this form to skip every one of them.

Save the form to apply either change.

Note: a newly created Global Automation is active on existing forms unless someone disables it there. Adding a Global Automation changes what already-published forms do.

Execution order

When a form is submitted, Global Automations run first, in the order they appear on the settings screen. The form’s own automations run afterwards, in their own order.

This matters in two situations:

  • A Global Automation with Stop other automations if this automation matches selected will prevent the form’s own automations from running once it matches.
  • A Global Automation cannot read the outputs of a form-level automation, because it has already finished by then. Workflow data references only reach backwards.

An action’s On error setting can also cross this boundary: Stop all automations in a Global Automation stops the form’s automations too.

Example

A site has a contact form, a quote form, and a support form. Every lead should reach the same CRM, but support requests should not.

  1. Create a Global Automation named Send leads to CRM.
  2. Add a Webhook action pointing at the CRM endpoint.
  3. Open the support form and clear Enable for this form for that automation.

The contact and quote forms now post to the CRM with no per-form setup, and adding a fourth lead form later requires no change to the automation.

Limitations

  • Global Automations cannot be edited from inside a form. Changes are made on the settings screen only.
  • They are stored in site settings rather than with a form, so they are not included when a form is exported or imported.
  • Runtime limits are counted per submission across all automations. A Global Automation that sends a webhook consumes part of the same 10-request budget available to the form’s own automations.

Next steps

 
Contact us