Site · Insites AI
AI automations in the site admin
Last updated 18 November 2026
Triggers, conditions, actions and the safety rules for automations.
What an automation is
Insites AI is pre-release. This page was written against the build of 31 October 2026 and will be revised at release.
An automation is a rule that runs on its own. It watches for something (a record, a form, a schedule or a webhook), checks an optional condition, then runs its actions in order. For example: When a contact is tagged VIP, create a task for the account manager.
Automations have their own item in the main menu, Automations (#/automations). You can build one in the editor, or ask the assistant to draft one and approve it on a card. To build one step by step, see Create an Automation.
The three parts
When: the trigger
| Trigger | You choose |
|---|---|
| A record is created | The table |
| A record is updated | The table |
| A record is deleted | The table |
| A field changes | The table, the field, and optionally the value it changes to |
| A tag is added | The table, the tag, and the field that holds the tags |
| A form is submitted | The form name |
| On a schedule | Every hour, every day or every week, the hour (in your time zone) and the day. Optionally a table: the actions then run once for each matching record |
| A webhook call arrives | Nothing. After you save, the editor shows an address and a signing secret |
Record and form triggers are checked every five minutes, so an automation reacts within five minutes, not at once. A change confirmed in the assistant starts matching automations straight away.
Only if: conditions
Each condition compares a field with a value: is, is not, contains, starts with, is more than, is at least, is less than, is at most, is one of or is filled in. Every condition must hold. Leave the list empty to run every time.
Then: actions
| Action | What it does |
|---|---|
| Create a record | Adds a record to a table |
| Update the record | Changes fields on the record that started the run |
| Add a tag / Remove a tag | Changes the tags on the record |
| Create a task | Creates a CRM task, assigned to an administrator, due in a number of days |
| Send an email | To an address, to the email on the record, or to everyone with a given AI role (owner, editor or viewer) |
| Notify administrators | Sends a notice to administrators with a role you choose |
| Call a webhook | Sends a POST to an https address, by default with the record as the body. A failed call is tried again three times, after 1, 2 and 4 seconds |
| Post to Slack | Posts a message to a channel in the Slack workspace connected under Integrations > Slack |
| Ask the AI | Asks the assistant a question about the record. Later actions can use the answer, or it can be written to a field. Costs 1 credit for each run |
An automation can have up to ten actions. They run in order, and the first one that fails stops the run. Each action can have its own Only run this action if condition. Insert values from the record with placeholders such as {{ record.email }}.
Safety
- Everything an automation writes appears in History, marked with the automation, and can be reverted. See History, Previews and Revert.
- An automation never reacts to its own writes, so it cannot start itself in a loop.
- A run limit per hour (default 100) stops a runaway. If an automation runs more often than its limit in any hour, it pauses itself and the owners get an email.
- A test run writes nothing. It runs the saved automation once against the most recent matching record and shows what each step would do.
- A webhook trigger accepts a request only when it is signed with the automation's secret.
- Only the administrator an automation runs as, or an owner, can change it. Everyone else can read it.
The Automations page
The list shows each automation with its trigger, last run, runs today, status (Live, Paused or Failing) and a switch to pause or resume it. An automation drafted by the assistant shows the question it was built from. The Pause all button at the top pauses every automation at once; when all are paused it reads Resume all.
Click Run log under an automation to see every run, newest first: the time, what started it, each step and its outcome, the credits used, and the status (OK, Failed or Skipped). A failed run shows the step that stopped it.
Cost
Running an automation is free. Only an Ask the AI step costs credits: 1 credit for each run. See Credits.