What it covers
Use previews, run history, permissions and retries to understand what a rule did.
Customisation and integrations
Turn reviewed triggers into repeatable actions.
How it works
Configure supported triggers and actions, preview the rule and inspect its run history. Permissions and retry behaviour help teams understand what ran and what needs another look.
Use previews, run history, permissions and retries to understand what a rule did.
Use previews and run history to review an automation before relying on it.
When to use it
A working path
Choose a supported trigger and action, then preview the proposed rule.
Activate it with the required workspace permission.
Inspect runs, outcomes and retry information when an exception occurs.
Illustrative scenario
A manager previews a rule that creates an internal task for a newly qualified lead, then reviews its run history after enabling it. Previewing the rule helps the manager confirm the trigger and action before activation, while run history provides a practical place to investigate an unexpected or failed outcome.
Before you start
No. It performs configured supported actions; people retain operational oversight.
Yes, run history and retry behaviour are part of the workflow.
Get started
Start with the core CRM for free, then add the tools your team needs.