Skip to content

Insites AI · Automations

Automations in depth Beta

Last updated 18 November 2026

Triggers, conditions, actions and guard rails for automations that run on their own.

What an automation is

Insites AI is pre-release. This page was written against the build of 1 November 2026 and will be revised at release.

An automation is a rule that runs on its own. It has three parts:

  • When: the trigger that starts it, such as a new record or a form submission.
  • Only If: optional conditions that must all hold.
  • Then: one to ten actions that run in order.

You can build an automation yourself under Automations in the main menu, or ask Insites AI to propose one in the chat. Everything an automation writes appears in AI > History, where it can be reverted.

When to use one

Use an automation for work that should happen every time, without anyone asking. For example, create a follow-up task when a contact is tagged VIP. Email the sales team when an enquiry form is submitted. Or score each new enquiry with an Ask the AI step.

For a question you want answered on a schedule, use a saved question instead. See AI reports in depth.

Triggers

TriggerWhat you choose
A record is created, A record is updated, A record is deletedThe table
A field changesThe table, the field, and optionally the value it changes to
A tag is addedThe table, the tag, and the field that holds the tags
A form is submittedThe form
On a scheduleEvery hour, every day or every week, at a time of day in your time zone. Optionally, a table to run once for each of its records
A webhook call arrivesNothing. Another system calls the automation's own address, signed with its secret

Record and form triggers are checked every five minutes, so an automation reacts within about five minutes. An hourly schedule runs when at least 58 minutes have passed since its last run.

Actions

ActionWhat it does
Create a recordAdds a record to a table you choose
Update the recordSets fields on the record that started the run
Add a tag, Remove a tagChanges the tags on the record
Create a taskCreates a task with a title, an assignee and a due date
Create an opportunity, Move an opportunityAdds an opportunity to a pipeline stage, or moves one to another stage or status
Send an emailEmails an address, everyone with an AI role, or the email on the record
Notify administratorsEmails everyone with the role you choose
Call a webhookSends the record, or a body you write, to a public https address
Post to SlackPosts a message to a Slack channel
Ask the AIAsks a question about the record and keeps the answer for the next actions

Text in an action can hold placeholders for the record's values, such as {{ record.email }} or {{ record.name }}. An action can also carry its own condition, so it runs only when that condition holds.

Worked example: score every new enquiry

You want each new enquiry scored from 1 to 5, and an email to sales for every enquiry that scores 4 or more.

  1. Go to Automations and click Create Automation.
  2. Under Automation, type a Name, for example Score new enquiries.
  3. Under When, set Trigger to A record is created and choose your enquiries table in Table.
  4. Under Then, click Add Action and set Action to Ask the AI. In What to Ask, type Score this enquiry from 1 to 5. Message: {{ record.message }}.
  5. Set What to Do With the Answer to Read named values (for example score and reason), and type score, reason in Value Names, Separated by Commas.
  6. Click Add Action again and choose Send an email. Set Send To, a Subject and a Message that uses {{ ai.reason }}.
  7. Give the email action a condition: value ai.score, condition is at least, value 4.
  8. Click Save.
  9. Click Test Run. It runs the saved automation once against the most recent matching record and shows what each step would do. Nothing is written or sent.

The automation is live as soon as it is saved with Status set to Live. Click View Run Log to see each run, step by step.

Note

An Ask the AI step answers from the prompt you write and the record values you put in it. It does not look anything else up. A test run calls the AI, so it costs 1 credit, like a real run.

Asking the assistant to build one

You can describe the rule in the chat instead, for example When a contact is tagged VIP, create a task for Erin due tomorrow. The assistant shows a card with When, Only if and Then. Click Apply to create it live, or Discard. The automation shows Built by AI from: and your question when you open it.

A proposed automation cannot carry a webhook secret. Add the secret in the editor after you apply it.

Who an automation acts as

An automation acts as the administrator who created it. The records it writes are recorded under that person, and so are the credits its Ask the AI steps use. Only that person or an owner can change or delete it. Everyone else sees:

You can read this automation but not change it. Only the person it runs as, or an owner, can.

Guard rails

  • Run Limit per Hour. Each automation has a limit, 100 by default and at most 1,000. When it is reached, the automation pauses itself and one email is sent. Set the default for new automations, and who gets the email, under Automations > Configuration.
  • The first failed action stops the run. The run is marked Failed and the automation shows Failing. The next successful run sets it back to Live.
  • No loops. A write made by an automation never starts another automation, or the same one again.
  • Pause Everything under Automations > Configuration pauses or resumes every automation at once. The Automations switch on the same page stops every automation from running.
  • Webhook calls go only to public https addresses.

Limits

  • An automation has one trigger and at most ten actions.
  • An Ask the AI prompt can be up to 8,000 characters.
  • A Post to Slack action needs a Slack channel id, such as C0123ABCD, and a connected Slack workspace.
  • Deleting an automation also deletes its run log. Changes it already made stay in History.

Troubleshooting

What you seeWhyWhat to do
The automation shows Paused and you did not pause itIt reached its Run Limit per HourCheck the run log for the cause, raise the limit if the volume is real, then switch it back on
The automation shows FailingAn action failed on the last runOpen View Run Log, open the failed run, and see which step stopped it
Nothing happened a minute after a new recordTriggers are checked every five minutesWait five minutes, then check the run log
A record changed but no run appearsThe record did not match Only If, so no run was recordedCheck the conditions under Only If
A run shows SkippedThe automation was over its Run Limit per HourRead What Started It on that run for the reason
You cannot edit the automationSomeone else created itAsk that person or an owner
An Ask the AI step failedCredits ran out, or the daily limit was reachedSee Credits, limits and pricing

Related