Automations
Automations that do the busy work.
When a deal is won, a lead goes quiet or an invoice is paid, Spodus does the next step for you. No code.
From a busy job to one that runs itself.
Pick what starts it, add the steps, and turn it on. No code.
Pick a trigger
A record changes, a date comes round, a schedule ticks or a webhook calls.
Add the steps
Create tasks, update records, send emails, notify people, wait, and branch.
Turn it on
Publish it and every run is logged, with the record it acted on.
Automations that read like a sentence.
When this happens, only if that's true, then do these things. Anyone can follow it.
Start on anything
A record created, changed or deleted, a date, a schedule, a webhook or a button.
Thirteen kinds of step
Create and update records, find and loop over them, branch, email, notify and assign.
Wait, then check
Pause for days, then carry on only if the record still needs it.
Every automation in one list
See which are live, when each last ran and how often. Star the ones you check.
Every run, logged
See each run's status, the version it used and the record it acted on.
Branch it on the canvas.
Switch to the canvas to see every path at once, with if / otherwise branches side by side.
Automations work across every product.
Start on a deal, an invoice, a ticket or a person, and act on any of them.
Two ways
to start
Start fresh today, or bring the clients, deals and history you already have.
Start fresh
Free for up to three people.
You get every product: CRM, invoicing, support, team, chat and Spodus AI, which asks before it changes anything. Upgrade when your team grows.
Start for freeBring your data
Bring your data from the tool you use now.
Your deals arrive with their stages, owners and dates. Connect your work email, and each client's emails land on their record. On a paid plan, we'll move it all for you, free.


The busy work, running on its own.
Start free with your team, or book a demo and see Spodus on your own data.
Questions, answered
A record being created, updated or deleted, a date on a record coming round, a schedule, a webhook call, or someone pressing Run.
Yes. They run on the server, so a change made by anyone, on any device, starts its automation even with every tab closed. Schedules, date triggers and webhooks run on the server too.
Workspace admins create and edit automations, because they act on every object in the workspace. Everyone else can see the list and what runs.
No. They come with every seat. Webhook triggers and webhook steps are on Starter and up.