Start free

Automations overview

What automations are, when to use them, and how they relate to the task inbox.

An automation pairs a trigger with a step, so the agent can act on a pipeline event without you having to notice it first and decide what to do. When the trigger's event occurs, the agent runs the automation's step — either immediately (auto-execute) or after you approve it (draft-only / approve-each-step).

Why use automations?

Without automations, every pipeline action requires you to notice something has changed and manually decide what to do next. Automations move that burden to the agent: you define the trigger and step once, and the agent applies it continuously.

Examples of what you can automate:

  • When a client research completes and the propensity score crosses 75, automatically draft an outreach sequence.
  • When a deal has sat in a stage for more than 14 days with no activity, notify the deal owner.
  • When a company news signal arrives for a tracked client, re-research them to capture the new context.
  • Run a one-off, manually-triggered automation ("Run now") that drafts a welcome sequence for a specific client or deal.

How automations work

  1. An event occurs in the system (a research run completes, a score changes, a signal arrives, etc.) — or an operator clicks Run now on a manual-trigger automation.
  2. Client Path evaluates every enabled automation whose trigger matches the event.
  3. For each match, the automation's step runs, gated by the automation's autonomy tier.
  4. draft_only and approve_each_step create an AgentTask in the task inbox and wait for your approval. auto_execute_safe_steps runs immediately for side-effect-free steps (like drafting a sequence) — nothing that sends externally ever runs unattended.

The automations list showing several automations with trigger labels, step labels, autonomy, and enable/pause toggles

Where to configure automations

Go to Settings > Automations. Editor role or above is required to create/edit; admin or owner is required to delete.

Key concepts

  • Triggers: manual, plus the five event kinds that can fire an automation.
  • Conditions: the per-trigger parameters that scope when an automation fires.
  • Steps: the actions an automation can run when its trigger matches.
  • Autonomy: how much of a run happens without your approval.
  • Audit: review what automations have done.