Automations and workflows
Trigger-action rules for when leads or quotes change state.
Updated 2 July 2026
Workflows are the "when this happens, do that" layer of Jeanus. They fire in the background when a record changes state and can send emails, create tasks, notify Slack, or POST to your own webhooks.
Anatomy of a workflow
- Trigger. What event kicks it off. Examples: lead created, quote sent, customer promoted from lead, task overdue.
- Filter. Optional conditions. Only run if the amount is over £5,000, or only for a specific vertical, or only if a custom field is set.
- Actions. One or more things to do. Send an email, create a task assigned to a specific rep, notify a Slack channel, POST to a webhook.
Where to build them
Settings > Workflows. Click New workflow, pick a trigger, add filters, chain actions. You can save it in draft mode to test before letting it fire on live records.
Common workflows to seed
- Send a Slack ping to your #sales channel when a quote over a certain value is accepted.
- Auto-create a "Send welcome pack" task when a lead is promoted to a customer.
- Auto-create a "Check-in call" task 30 days after a customer's first order.
- Send an internal note when a customer visits the portal three times in a week without ordering.
Test before you launch.The Test button on the workflow builder fires the workflow against a picked record without any side effects. Use it before going live so you know the email copy and Slack format read well.
What Jeanus already does without a workflow
Overdue tasks, quote follow-up nudges, sign-off requests and portal chat notifications are all built in and do not need a workflow. Workflows are for the extra layer of automation specific to your team.