Automations
Who this is for
Section titled “Who this is for”Users with automations: read to inspect automation rules and automations manage permission to create, edit, enable, disable, or delete them.
Before you start
Section titled “Before you start”Confirm the intended trigger, action, record owner, and failure handling. An automation should make a bounded change; it is not a substitute for reviewing business-critical work.
Rule vocabulary
Section titled “Rule vocabulary”Rules can trigger from lead, deal, contact, organization, vendor, or task events: created, updated, field_changed, stage_entered, or status_changed.
Supported actions are create_task, update_field, send_notification, assign_owner, add_to_sequence, and log_activity. Action configuration must be a JSON object; invalid JSON is blocked before save.
- Open Settings → Automations and review existing rule state, trigger, action, and recent execution context.
- Create or edit a rule with the smallest possible trigger/action scope.
- Enable or disable it only after a review of its operational effect.
- Delete a rule only after the confirmation prompt; deletion stops future rule execution and cannot restore the definition.
What happens next
Section titled “What happens next”An active rule is eligible for executor processing. It does not guarantee a downstream provider action, outbound delivery, or business outcome; check the resulting record and relevant integration state.