Automations for RevOps

Last updated: July 29, 2026

Keep your CRM clean and identify deal risks before the pipeline goes quiet. These templates help enforce data quality and detect stalled deals without manual spot-checks.

Browse them under Automations → Templates → For RevOps. For a detailed guide on writing Triggers, Conditions, and Actions, see Writing effective automations.

How to start from a template

  1. Go to Automations → Templates.

  2. Filter For RevOps.

  3. Click Use Template.

  4. Name it, set Who is this Automation for? (Everyone in the Workspace or Selected Team), then Next.

  5. Configure the builder, Run Test, and Publish.

CRM Auto-fill

Needs: An active CRM connection. If the CRM is disconnected, reconnect before you start.

Update CRM fields after every call using AI-generated summaries and extracted data points, so reps don’t have to retype notes into HubSpot or Salesforce.

Trigger

After every call

Condition (optional)

Not included in this starter. You control what gets written with field mappings and optional approval.

Action

Update CRM — map CRM fields to Hyperbound/custom fields and extraction prompts. Optionally require approval before values are written to the CRM.

Tips: Start with a small set of fields. Write clear extraction prompts for each field (e.g., “next meeting date as YYYY-MM-DD,” “competitor names only if explicitly mentioned”). Use approval while building trust, then relax it once accuracy is confirmed.

Deal Risk Notification

Receive a Slack alert when a deal goes quiet and Kota detects meaningful risk such as stalled momentum, missing next steps, weak engagement, or unresolved objections.

Trigger

Deal with no activity — default 7 days

Condition (optional)

Does this deal show meaningful risk, such as stalled momentum, missing next steps, weak buyer engagement, or unresolved objections?

Customize this in your team’s risk language (e.g., commit deals only, missing next-step date, no multi-threading).

Action

Medium: Slack

Message: Send a concise deal risk notification explaining the risk signal, likely impact, and one recommended next step for the owner.

Audience: yourself

Tips: Use shorter inactivity windows for high-velocity deals and longer for enterprise deals. Request “owner + deal + one next step” every time. Route notifications to owners, managers, or a RevOps channel depending on who should act.