Workflows
Workflows automate CRM tasks by running an action when a trigger fires and your conditions match.
Workflows are in beta. Triggers, conditions, and actions may change before general release. Subscribe to the Informly changelog for updates.
A workflow lets you say "when X happens, do Y." When a deal moves to Won, create a follow-up task in seven days. When a contact's rating drops below three, notify the account owner. Workflows take the small repetitive jobs off your team and run them the moment they're needed.
You build workflows visually — no code, no scripting.
Build a workflow
Go to CRM → Workflows → New workflow to open the builder. A workflow has three parts.
Pick a trigger
The trigger is the event that starts the workflow. Pick one of the trigger types listed below.
Add conditions
Conditions filter when the workflow runs. They're optional — a workflow with no conditions runs on every trigger event. Use them when you only want the workflow to fire on a subset (for example, deals over $10,000).
Add actions
Actions are what the workflow does. You can chain more than one action on a single workflow.
Test, then enable
Use test mode to dry-run the workflow against your historical records, then flip it on when you're confident.
Triggers
| Trigger | Fires when |
|---|---|
| Record created | A new account, deal, task, or contact is created. |
| Record updated | A field on a record changes. |
| Stage changed | A deal moves between pipeline stages. |
| Task overdue | A task passes its due date without being completed. |
| Scheduled | On a recurring schedule (for example, every Monday). |
Actions
| Action | What it does |
|---|---|
| Create record | Create a new task, deal, or note. |
| Update field | Set a field on the triggering record (or a related one). |
| Send notification | Notify a teammate in-app. |
| Assign owner | Set or reassign the owner of the record. |
Test mode
Test mode runs the workflow against your historical records without making any changes. It tells you which records would have matched and what the actions would have done. Use it before you enable a new workflow to make sure your conditions are scoped correctly.
Tips
- Start with the narrowest conditions you can. It's easier to widen a workflow than to undo a flood of unintended actions.
- For high-volume triggers like record updated, always add a condition — otherwise the workflow can run on every keystroke-level edit.
- Use custom fields in conditions so workflows can react to data unique to your business.