Event-Driven Automations
Convertly automations apply consistent workflow rules when supported lead events occur.
Trigger -> conditions -> actions -> run logSupported triggers
Section titled “Supported triggers”Current CRM triggers include:
- Lead created or updated
- Lead stage changed
- Lead assigned
- Native form submitted
- Lead source changed
- Lead value changed
- Lead category changed
Automations are event-driven. Time-based reminders, overdue digests, lead digests, trial alerts, and billing alerts are handled elsewhere in the platform.
Supported actions
Section titled “Supported actions”Actions can:
- Assign or clear an owner
- Assign round-robin among selected users or a role
- Add or remove categories
- Change stage
- Create a task
- Schedule a follow-up
- Add a lead note or timeline entry
- Notify selected CRM roles or users
- Update a configured custom field
Automation alerts are for CRM users. Lead-contact email nurture and drip sequences are not part of the automation builder.
Conditions
Section titled “Conditions”Conditions focus on lead data and capture context, such as form, stage, value, owner, category, follow-up state, UTMs, campaign, landing page, and referrer.
Workspace billing, plan limits, trial state, and platform affiliate data are not available as tenant automation conditions.
Permissions
Section titled “Permissions”Admin and Manager can create and change rules. Sales and Staff can view automations but cannot modify them.
Start safely
Section titled “Start safely”Begin with one narrow rule, keep it disabled while building, use the dry-run simulator, then enable it and verify the real run log with a dedicated test lead.