Automations with AI
Aglyn AI is in beta. It is available today on every plan that includes it, and it is still changing as we improve it. Beta means you can use it now, while what it builds and the steps on this page may still change.
On the Automation page, Aglyn AI can draft an automation from a description, change or fix one you already have, explain what one does, and tell you why one of its runs failed. None of them runs an automation, switches one on, or changes one you have saved: what it drafts arrives as a new automation, switched off.
Draft an automation from a description
Choose Create with AI beside Add action and Recipes on Automation → Actions, or at the top of Automation → Workflows (in its empty state while it has none). Describe what should happen, and when — "when someone submits the newsletter form, add them to the newsletter list, make them a lead and send them a welcome email".
The automation is drafted switched off, using only the triggers and steps your plan includes. A list, campaign or other record your site does not have — or that the words could mean more than one of — is left as a placeholder for you to pick. When it is ready, Review it opens it in the Actions editor; from Workflows, that takes you to Actions, where it is listed.
Draft an org automation
An org automation is written once for your workspace and runs on the sites you choose. On your workspace's Automation → Org automations, choose Create with AI in the card's header and describe what should happen, and when — "when someone books on any of our sites, make them a contact, tag them booked and send them a welcome email".
The automation is drafted from what an org automation can do: it starts only on something the server sees — a form, a lead, a booking, a member or a CRM event — and uses only the steps every site runs the same way, so nothing that belongs to one site's pages, workflows or webhooks. It opens placed on every site, so a campaign or dataset is filled in only when it is shared with every site. A list, campaign or dataset your workspace does not have, that is shared with only some sites, or that the words could mean more than one of, is left as a placeholder for you to pick once you have chosen the sites.
Nothing is saved for you. Open in the editor opens it in the org automation editor as a new automation, switched off. Choose the sites it runs on, check its steps, and save it with the editor's own Save — or close the editor, and nothing changes. When it is right, switch it on from the list.
Change or fix an automation
Open a saved action and use the box under Explain it:
- Change with AI — describe the change: "also tag them newsletter, and wait a day before the email".
- Fix with AI — asks Aglyn AI to fix whatever would stop the automation working as intended, such as a list your site no longer has, and to change nothing else.
Either way you get a changed copy, switched off, beside the action you started from, which is left exactly as it is. The copy says what changed from the original — steps added, removed or changed, and whether its trigger or conditions changed — worked out by comparing the two, not taken from the AI's account of itself. Review the copy opens it in the editor. When it is right, switch the copy on and the original off.
It reads the action as it is saved, so save your edits first. An action that does something Aglyn AI does not write — starts on something a visitor does on a page, has a step that runs on the page, or only runs when an expression is true — cannot be changed this way, so that nothing you did not ask to lose goes missing; edit it in the editor instead. Workflows (lists of function calls) can be explained, not changed.
Explain an automation
Open a saved action or workflow and choose Explain it at the top of the editor. In a few minutes you get a plain-words account of what it does, step by step, and anything worth checking, such as a list your site no longer has or a placeholder nobody has filled in. It reads the automation as it is saved, so save your changes first.
Find out why a run failed
In an automation's Runs log, a failed run has Why did this fail?. It reads what the run history recorded about that run, together with the automation's settings, and answers with the most likely cause and how to fix it. Opening it again shows the same answer.
What Aglyn AI is sent
- To draft an automation: your description, what your plan lets automations use, and the names of your site's forms (with their field names) and datasets. The names of your lists, campaigns, workflows, webhooks and pipeline stages are not sent; the words of the answer are matched to them on Aglyn's side.
- To draft an org automation: your description, what your plan lets automations use, what an org automation can start on and do, and the names of your workspace's datasets. No site's forms are sent; the names of your lists, campaigns and pipeline stages are matched on Aglyn's side, as for a site's automation.
- To change or fix one: the same, plus how the action is set up, as for an explanation below.
- To explain an automation: how it is set up, including the text of its emails and messages and the names of the records it uses. Email addresses are removed first, a teammate is described only as a teammate, and on-page code is left out.
- To explain a failed run: also when the run happened, what it did and the errors it recorded, with email addresses removed. What a visitor submitted, such as what they entered in a form, is never read.
No contact, lead, deal, form submission or list member is read for any of them.
Who can use it
These jobs need the Generate with AI permission, on a site whose Automation plugin is on. Drafting an org automation needs the same permission in the workspace, Automation switched on for it, and a plan with org automations; only members who can edit org automations see Create with AI there. See who can use Aglyn AI. A site that has switched AI off shows none of these controls. Each job spends AI credits; an automation's own runs count against your workspace's action runs, never your AI credits.