Create an Automation

Open the builder

Open Automations and choose New Automation. Creating or changing rules requires Admin or Manager access.

Build the rule

1. Name it clearly. Describe the trigger and result, such as “Assign website form leads”.
2. Keep it disabled. Finish configuration and testing before enabling the rule.
3. Choose a supported event. Select lead creation, update, assignment, stage, source, value, category, or form submission.
4. Add narrow conditions. Use source, form, stage, campaign, value, owner, category, follow-up state, or other supported lead context.
5. Add actions in the intended order. Later actions may see changes made by earlier actions.
6. Review ownership behavior. Assignment actions overwrite the current owner unless an owner condition prevents that.
7. Save the rule.

Example: route one native form

Trigger: Native form submitted
Conditions:
  Form is “Demo request”
Actions:
  Assign round-robin among selected Sales users
  Add category “demo-request”
  Schedule follow-up for the assigned owner
  Add note “Routed by demo request automation”

Example: create a stage handoff

Trigger: Lead stage changed
Conditions:
  Stage is “Qualified”
  Owner is not empty
Actions:
  Create task for assigned owner
  Schedule follow-up
  Notify Manager role

Test without changing data

Use Test Automation and select a representative lead. The dry run evaluates trigger context, conditions, and mock action descriptions without modifying CRM records.

After the dry run passes, enable the rule and perform the event with a dedicated test lead. Review lead history, created work, ownership, and the automation run log.

Avoid broad rules

A generic Lead Updated trigger can run frequently. Add conditions that make the intended change unambiguous and avoid rules that repeatedly update a field which triggers another matching rule.