Workflows overview
Build visual automations that react to changes in every module, test them, and follow every run.
Workflows work on the website picked in the header switcher. Open Dashboard → Workflows, start from a template or a blank canvas, and connect a trigger to logic and action steps.
Triggers
- Events from every module: rankings, click runs, uptime incidents, domain and certificate warnings, audits, backlinks, analytics goals, reports and more.
- A schedule (every few minutes, hourly, daily, weekly or a custom time in UK time).
- An incoming request to a private address, a form submission, or a manual run from the dashboard or an AI assistant.
Logic
- Conditions with if/else branches, switches, filters and a wait or delay.
- Loops over lists, merges, variables, formatting and maths.
- Human approvals that pause the run until a teammate approves or rejects, and tasks for your team.
Actions
- Notify the team by bell, email or team chat, send a request to any address, and post to your webhooks.
- Act in other modules: start a click run, queue an audit, open an uptime incident, add a report note, update your CRM.
- AI steps that summarise, classify or draft text, with a monthly budget per website.
Testing and versions
Every save creates a version you can compare and restore. Test runs use sample data and show each step’s input and output without sending anything. Turn a workflow on only when you’re happy with it.
Trigger options
- AI Overview citation gained or lost (aio.citation.gained, aio.citation.lost): your website starts or stops being cited for a tracked term.
- Local ranking changed (local.rank.changed): choose the minimum number of places moved.
- New audit issues (audit.issue.new): issues that weren’t in the page’s previous audit, with their titles and severity.
- Certificate expiring (ssl.certificate.expiring): choose how many days before expiry; fires once per certificate.
- Traffic spike or drop (analytics.traffic.spike, analytics.traffic.drop): choose the window (last hour, day or week) and the minimum change, from 20%.
- Payment failed (billing.payment.failed): account level. It still starts workflows on websites on billing hold, but those runs can only send notifications, emails, chat messages and HTTP requests.
- The Audit step can also add a new page and audit it: the address must be on the same website and within your plan’s page limit.
Runs, retries and history
Each run lists its steps, timings, inputs, outputs and errors. Failed steps retry with a growing wait, up to the number of attempts you set, and you can re-run a whole run from its page. Run history is kept for 13 months.
Secrets, roles and audit
Store passwords and keys as encrypted secrets and refer to them by name; they’re never shown again after saving. Owners and admins can edit, turn on and approve; members can view and run. Every change is written to the audit log.
Import and export
Export any workflow as a file and import it into another website. Secrets aren’t included, so you add them again after import.
Limits
- Workflows per website: Starter 3, Growth 10, Scale 25, Pro 100, Enterprise 500.
- Runs per website per month: 1,000, 5,000, 25,000, 150,000 and 500,000.
- AI steps per website per month: 50, 200, 1,000, 5,000 and 20,000.
- Runs over the monthly allowance wait until the next month or an upgrade; nothing is charged automatically.
Webhooks
workflow.run.succeeded, workflow.run.failed and workflow.approval.requested (workflow id, run id, status and duration). Add them in Integrations → Webhooks.
Bijgewerkt