Overview
Most website work isn't a one-off. It's the Monday report, the monthly speed check, the link sweep nobody remembers until something breaks, and the launch page that has to go live at exactly 7pm. Automations hand all of that to your assistant.
You describe the job in plain English. The assistant asks for anything it needs, plays the plan back to you, and saves nothing until you say yes. From then on it does the work on its own, reports back in a chat thread, and emails the results, PDFs included, to the people you chose.
Three ways to start an automation
At a set time
One-off jobs that have to happen at a particular moment, whether or not anyone's at a keyboard. Give it a date and a time and it runs once, then marks itself done.
- “Publish the new product page at 9am on Monday.”
- “At 00:01 on 27 November, publish our Black Friday page, then email the sales team to say it's live.”
- “Tonight at 7pm, publish the event recap post we drafted.”
- “Next Friday at 3pm, check the launch page for broken links and email me a report.”
On a schedule
Recurring work that runs daily, weekly on the day you choose, or monthly on a chosen date, at local time in your timezone. Clock changes are handled for you.
- “Every Monday at 8am, email a top-level SEO report as a PDF to Anna, Ben and Cara.”
- “Every morning, check for ranking or traffic drops and tell me what slipped and what you'd do about it.”
- “On the 1st of each month, run a page speed check on our key pages and summarise what to fix.”
- “Every Friday afternoon, sweep the site for broken links and missing images, and draft the fixes.”
- “Each month, review the site for anything out of date, like old years, stale prices or expired offers, and draft updates for me to approve.”
- “At the start of each month, suggest the blog posts we should write next, based on what our audience is searching for.”
When something happens (coming soon)
Event triggers are on the way. You'll be able to start an automation from something that happens on your site. Because the assistant already works on your site's code, it will add whatever's needed to send the event, whichever platform you're on, through the usual review-and-approve process.
- When someone submits a form, pull together everything they've sent before into one thread.
- When a blog post goes live, submit it for indexing and draft the social posts.
- When a new enquiry comes in, draft a reply for your team to review.
Until event triggers launch, the assistant offers the closest scheduled version, such as a daily digest of new form submissions.
What an automation can do
An automation can do the same work your assistant does in a normal chat, and then deliver the result.
- Report: build a summary or a full PDF report from your site and its data.
- Check: look for broken links, slow pages, out-of-date content, or slips in rankings and traffic.
- Draft: prepare content updates, fixes and new posts as drafts, ready for someone to approve.
- Publish: put live the exact pages you approved when you set the automation up, at the time you chose.
- Deliver: post every run to a chat thread, and email results, with up to 5 attachments, to the people you agreed.
Combine any trigger with any of these. Publish at 9am and email the team. Check every Friday and draft the fixes. Report monthly as a PDF to the board.
How it works
- Describe it, or pick an idea. Open Automations and type what you want, or start from one of the suggested ideas.
- The assistant fills the gaps. It asks only for what's missing: what should happen, when, what the output looks like, and who receives it.
- It plays the plan back. You get a short plain-English summary of exactly what will happen, when, and who gets anything. Nothing is saved until you confirm.
- It runs on its own. At the right time the assistant does the work, posts the results to a chat thread and emails the people you agreed.
- You stay in control. See every automation with its next run and its history (done, failed or skipped, each linked to its thread). You can run it now, or pause, resume, change or delete it.
Nothing goes live by surprise
By default, an automation can't publish, edit live content or delete anything. Its changes are left as drafts for a person to approve. The only exception is pages you specifically approve at setup: say “publish this page at 7pm” and the assistant finds the exact page and names it back to you. Only that page can go live. The platform enforces this; it doesn't rely on the AI following instructions.
Each run acts as the person who set the automation up and is limited by their permissions. Email goes only to the addresses confirmed at setup, up to 20, and never to anyone else.
Availability
Automations are included on Scale and Enterprise. Team admins create, change, pause and delete them from the Automations menu. Each run uses credits in the same way as a normal chat.
Frequently asked questions
Do automations cost extra?
They're included on Scale and Enterprise plans. Each run uses credits like a normal chat, so a weekly report costs roughly what asking for it by hand would.
What schedules are available?
Once at a set date and time, daily, weekly on a chosen weekday, or monthly on a chosen day between the 1st and 28th. Schedules run at local time in your timezone and handle clock changes correctly.
Can it publish to my live site?
Only pages you approved for publishing when you set it up, and the assistant names each one back to you first. Everything else a run produces is left as a draft for a person to review. The platform itself enforces that limit.
Can it take a page down or change live content at a set time?
Not yet. Timed automations can publish the pages you approved. Other changes are prepared as drafts, so someone on your team can approve them in a click.
Can an automation email anyone?
No, only the addresses confirmed when it was set up, up to 20 of them. Each email can carry up to 5 attachments (10 MB in total), such as a PDF report.
Can it react to things happening on my site, like a form submission?
Event triggers are coming soon. Until they launch, the assistant offers the closest scheduled version, such as a daily digest of new submissions.
