Event-Driven Automations

Convertly automations apply consistent workflow rules when supported lead events occur.

Start with one rule, test the conditions, and verify the resulting action.

Where to go

Automations

What you need

Manage permission to create or change rules, and access to relevant lead records.

1. An event happens

   For example, a new lead arrives or a lead-linked call is missed.

2. Your conditions match

   The rule checks the lead against the conditions you chose.

3. The action runs

   Assign work or create a follow-up, then review the run log.

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
• Lead-linked completed or missed call events

Automations are event-driven. Time-based reminders, overdue digests, lead digests, trial alerts, and billing alerts are handled elsewhere in the platform.

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

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

Automations manage access is required to create or change rules. View access permits the supported read-only surfaces. Record visibility still applies when reviewing related leads and execution history.

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.

See Practical automation recipes for routing, call follow-up, and stage-handover examples. Supported fields, actions, permissions, and execution safeguards still apply.