Skip to main content

Admin Automations : configure triggers and actions

Written by Guillaume Rieu
Updated over a week ago

This feature is only available to users with Admin permissions and an active Business licence. If you don’t see automation settings, check your role or contact your workspace administrator.

Learning Objective

By the end of this guide, you'll know how to configure meeting automations using triggers and actions to reduce manual work and improve visibility across your organization.

Prerequisites

Before getting started, make sure you have:

  • Admin permissions

  • A clear folder structure (recommended)

  • Insights templates configured

  • Defined use cases (Sales, Onboarding, Churn, Enterprise)

How Automations Work

Every automation follows a simple rule:

πŸ‘‰ WHEN a condition is met (trigger)

πŸ‘‰ THEN an action runs automatically

Example:

WHEN a demo call is recorded β†’ THEN generate insights and share them with the Sales folder.

Think of automations as guardrails that ensure important conversations never get lost.

Step 1 β€” Choose Your Trigger

Triggers define when the automation runs. Selecting the right ones prevents noise and keeps data useful.

Any Meeting

Runs the automation for every meeting.

Common uses:

  • Send recaps

  • Notify Slack channels

  • Create CRM tasks

Add Filters (Recommended)

Filters let you build highly targeted workflows by combining conditions.

Meeting Type

Trigger based on internal vs external meetings.

πŸ‘‰ Helps separate customer conversations from team syncs.

Recorder’s Team

Filter by the team that recorded the meeting.

πŸ‘‰ Example: Trigger automation only for CS calls.

Meeting Host

Ideal for persona-based workflows.

Examples:

  • Record calls hosted by new hires

  • Notify managers when strategic reps run meetings

Folder

Automate based on how meetings are organized.

Example folders:

  • Sales

  • Enterprise

  • Customer Success

  • Partnerships

πŸ‘‰ Great for pipeline-based automation.

Title Keywords

Trigger workflows when specific words appear in the meeting title.

Combine Filters with AND / OR

Refine automation behavior using logical operators:

  • AND β†’ higher precision

  • OR β†’ broader coverage

Example:

Meeting type = External AND Folder = Sales

Only customer-facing sales calls trigger the automation.

Step 2 β€” Configure Actions

Actions define what happens automatically once the trigger is met.

Choose carefully β€” strong automations create leverage, while too many create noise.

Auto-record Meeting

Automatically joins and records the meeting.

Why enable it:

  • Prevents forgotten recordings

  • Builds a searchable call library

  • Supports coaching and QA

  • Helps identify objections and churn signals

πŸ‘‰ Recommended for demos, onboarding calls, and enterprise conversations.

Only Record if a Team Member Is the Host

Records meetings only when someone from your company organizes them.

βœ… Reduces legal risk

βœ… Protects customer trust

βœ… Avoids recording meetings where you're just invited

πŸ‘‰ Highly recommended as a default setting.

Auto-share

Automatically sends recordings or notes to selected people or channels.

Typical uses:

  • Share calls with managers for coaching

  • Notify leadership about strategic deals

  • Send sales calls to Customer Success for smoother handoffs

Auto-add to Folder

Automatically organizes meetings into the correct folder.

Why it matters:

  • Faster search

  • Cleaner reporting

  • Easier coaching workflows

πŸ‘‰ A strong folder structure is key to scaling.

Auto-personalize summary

This option allows you to personalize the overview of each call based on your selected criteria.

Note: This feature is insight-based, not template-based.
This means you will need to add each insight individually.

Analyzes meetings and extracts key information such as:

  • Summaries

  • Objections

  • Next steps

  • Risks

  • Key topics

πŸ‘‰ Turns conversations into data your team can act on.

Tip: Start with high-value calls before expanding.

Enforce Automation

When this option is enabled, it prevents members from modifying or overriding the automation with their own personal settings. In other words, the automation becomes mandatory and applies consistently across all users. This ensures standardized behavior, avoids configuration conflicts, and guarantees that the defined process runs exactly as intended without individual custom adjustments interfering with it.

Did this answer your question?