Insites AI · Automations
Create your first automation Beta
Last updated 18 November 2026
Build, test and switch on an automation that reacts to a form submission.
What you build
Insites AI is pre-release. This page was written against the build of 2 November 2026 and will be revised at release.
In this guide you build an automation that emails the people with the Owner role whenever someone submits one of your forms. It uses a trigger, one action and a test run, and nothing is sent until you switch it on. You need the Editor or Owner AI role, and a form on your site.
An automation acts as the administrator who creates it. Its actions run with that person's access, and any credits it uses are charged to them. For the full list of triggers and actions, see How automations work.
Step 1: Open the editor
- Click Automations in the main menu.
- Click the button that creates a new automation. The editor opens.
You can also ask the assistant in the chat, for example When a form is submitted, email the owners. It drafts the automation on a card. Approve the card, then open the automation and check each part.
Step 2: Name it and set the limit
- Under Automation, type a Name, such as Tell owners about new enquiries. A clear name makes the run log and History easier to read.
- Set Status to Paused while you build. Paused saves the automation without running it.
- Leave Run limit per hour at its default of 100. If the automation runs more often than that in one hour, it pauses itself and sends one email.
Step 3: Choose the trigger
Under When, set Trigger to A form is submitted, then choose your form. Form triggers are checked every five minutes, so the first run can take up to five minutes to appear.
Step 4: Add the action
- Under Then, click Add an action and choose Notify administrators.
- Choose the role to notify, and write the message. You can use placeholders for the record, such as
{{ record.email }}.
Leave the Only if list empty to run on every submission. To run only for some, add a condition: choose a field, a comparison and a value. Every condition must hold for the automation to run. Actions run in order, and the first one that fails stops the run.
Step 5: Save and test
- Click Save.
- Click Test Run. It runs the saved automation once against the most recent matching record, and shows each step as Would run, Skipped or Would fail.
- Fix any step that would fail, save again and test again.
A test run writes and sends nothing. It always tests the saved version, so save before you test.
Step 6: Switch it on and watch it
- Set Status to Live and click Save.
- Submit your form once.
- Wait up to five minutes, then open Automations and click Run log under your automation.
Each run shows what started it, each step and its outcome, and its status: OK, Failed or Skipped. To undo something an automation wrote, open AI > History and click Revert on that change.
Note
An automation never starts another automation, or itself, so one write cannot cause a loop. To stop every automation at once, use Pause Everything under Automations > Configuration.