Play steps reference

Each record that enters a play runs through its steps in order. Clu adds and configures steps when it builds a play, and you can add or change them yourself with Add step on the canvas. Each step card shows its cost per record or per company.

All steps at a glance

Get company, Approve, Wait, Code, Webhook and Hand off work only in a play that belongs to an agent, not in a library play.

Source steps

Find People

Finds people matching your filters at each company the play is working on. People per company: 1 to 25 (default 10). Free.

Get company

Turns people into one record per company, so later steps (for example a Research skill on the company) run once per company instead of once per person. Company source: Employer or CRM account. Free.

Enrich steps

Enrich

Nothing is charged for an email, phone or profile that isn’t found. See Waterfall enrichment.

Validate

Verify email and Verify phone, 0.5 credits each per record.

Find meetings and call notes

Find meetings adds the next and last Google Calendar meeting with each record. Get Fathom call notes, Get Gong call notes and Get Fireflies call notes add the latest call with each person (matched by email) or company (matched by domain) from the notes synced into Knowledge: summary (up to 2,000 characters), action items, attendees and a link. Recency is the latest call, or the latest within a number of days (1 to 365). After a call-recorded trigger, the step reads the call that started the play. Get Fireflies call notes can also read the call’s transcript from Fireflies (first 8,000 characters). All are free, work on agent plays and need the app connected. See Google, Airtable, Notion and Fathom and Integrations.

AI: the Agents step

The Agents step runs one or more skills on each record:

• The play’s projected cost (on the step card and in the Try it quote) assumes the longest allowed prompt, so it can be higher than what a run actually charges. Runs charge the skill’s real estimate.
• Agent instructions can read your Knowledge sources at no extra cost.
• For Employment check, the Invalid email counts as left policy can be set by asking Clu.
• Skill outputs (for example {{play.first_line}} from Write) can feed later steps such as Add to sequence. More on each skill in Skills.

Logic steps

Branch

Routes records down 2 to 6 paths: If, Else if and Else. Each path has its own conditions on record fields, skill outputs or CRM data. A record goes down the first path it matches; the rest fall to Else, and leave the play if no step follows Else. Free.

Approve

Holds each record until a person approves or rejects it. Free. Full details in Approvals below.

Wait

Waiting records show under Waiting records on the Runs tab. Free.

Code

Runs JavaScript to compute typed outputs from record fields you declare as inputs. Limits: up to 20,000 characters of code, 1 to 30 inputs, 1 to 12 typed outputs, 3 seconds per batch of records. Code has no network access, cannot import packages and cannot read secrets. Free.

Hand off

Sends records to another play of the same agent (Hand records to), which receives them with the Another play sends records trigger. New play creates the receiving play. Free.

CRM steps

CRM Action

Reads from or writes to Salesforce, HubSpot or Attio. Free (it uses your CRM’s API calls, not credits).

Create a new record and Create only are for people on an agent’s play. Create only skips anyone the Sync matches (by Cleanlist ID, email, LinkedIn URL or name in the Account) and writes nothing to them. Skipped people count as not synced, so a Branch on whether the person synced keeps them out of later CRM steps.

On Attio: Sync (people or companies), Look up, Update fields, Create task, Log note and Add to list (a list of people) work. Set owner and Add contact role aren’t available, Attio has no Leads (use Contact), and only deals have an owner. Every Attio deal counts as open, so Update fields and a company Sync skip a record that has a deal. Create task and Log note need CluGTM to have task or note access in your Attio workspace.

Owner assignment options: Keep current owner (your CRM defaults), Assign one specific owner, Round-robin across all owners, Round-robin across chosen owners, Account owner, Owner from a field, or Rules, each with an Otherwise fallback.

Write safety: Inherit CRM protections (the default, follows your CRM settings, for example leaving records a rep owns alone) or Allow updates to owned records.

Review duplicates and Merge duplicates

Used only by CRM cleanup plays with the CRM duplicates trigger. See CRM duplicate cleanup.

Output steps

Add to sequence

Send to: a CluGTM sequence, or (on an agent’s play) lemlist, Outreach, Salesloft or Instantly. Free: sending costs no credits.

CluGTM sequence

• Pick a Sequence, or create a new one.
• Values stores per-person text from earlier steps (for example a Write first line) that your sequence emails use as {{play.first_line}} or {{play.<value name>}}. A person missing a value a step needs is stopped with the reason, for example “Stopped: no first line written”.
• People who replied or were stopped in another sequence are skipped. People added to a draft sequence wait there and start when you launch it.
• Needs access to Sequences.

lemlist, Outreach, Salesloft or Instantly

• Connect the tool on the Integrations page: lemlist under CRM integrations, Outreach, Salesloft and Instantly under Sales engagement, where only an organization admin can connect them. Until then the step shows Connect, which opens the tool’s card. See Integrations.
• Pick the Sequence (a campaign in lemlist and Instantly, a cadence in Salesloft) and Status. Sender: Sequence default, Record owner or One user (lemlist and Instantly use the sequence default), with a fallback user (Outreach requires one).
• Instantly can also fill the campaign’s own custom variables from record fields.
• If active in another sequence: Skip (default) or Add anyway.
• People are skipped when they have no email, unsubscribed from CluGTM sequences, have a risky or invalid email, are already in that sequence, opted out or bounced there, are active elsewhere (unless Add anyway), or have no mapped sender. Existing people in the sequencer are never updated.

Notify

Slack channels must be internal to your Slack workspace. A Teams channel connected with a Workflows webhook gets plain posts only: no owner routing or approve buttons; those need Clu in Teams. Free.

With Once a day, one Slack message at the hour you pick (in your browser’s time zone) covers every scheduled run since the last one. Days with nothing new send nothing, and Run now and failures still send right away. For one daily message across all of an agent’s plays without a Notify step, use Daily summary in the agent’s Delivery settings (see Agents: Slack).

Webhook

Sends records to your own https endpoint. Free.

Use Send test to check the endpoint once the play is saved. Secrets come from Settings → Connections → Secrets; see Secrets.

Export to Google Sheets

Adds a row per record, or updates the matching row, in the Google Sheet and Tab you pick, with the columns you choose. Free.

Create a Google Doc and Notion steps

Create a Google Doc creates one doc per record. Add a page to a Notion database adds one page per record, and Update a Notion page updates the matching page. Free; the apps must be connected.

Brief

Scheduled briefs (an agent with a Schedule trigger and no record play) have a Brief step: one unattended Clu turn that writes the brief, then a Notify step that sends it. It is charged like a Clu message, up to the agent’s Brief credits per run (default 100, at most 1,000). See Agents: Scheduled briefs.

Triggers from integrations

What starts a play is set on its trigger; see Plays and triggers. These triggers come from integrations and work on an agent’s play:

All four are free. Teammates’ calls are skipped: participants with a member’s email or your company’s domains don’t start the play. Add Enrich after a call trigger to get names and titles, and a call-notes step for the summary.

Failures and retries

On an agent’s play, open a step’s On failure settings:

New Enrich and CRM Action steps on an agent’s play retry 3 times by default. A retry restarts at the step that failed and never charges earlier steps again. Records waiting for a retry show under Waiting records on the Runs tab.

Play size limits

A play can have up to 50 steps, branches nested up to 10 deep, and is limited to 200 KB in size. Records parked by Wait, Approve, retries and Hand off are capped at 50,000 per play.

Approvals

The Approve step pauses records until a person decides. Approvals appear on the agent’s Approvals tab, in the Approvals inbox and, if you choose, in Slack.

Approve step settings

Approvers get one reminder after 24 hours. Approved records continue on the Approved path. Rejected records take the Rejected path, or leave the play if it has none.

Where to decide

• Approvals inbox: on the Agents tab, click Approvals. Tabs Pending and Decided, with Refresh and Download CSV. Each row shows the agent, play, step, how long it has waited, and when it expires (or “No deadline”). Select rows and click Approve selected (N) or Reject selected, or open one with Review and approve / Review and reject.
• The agent’s Approvals tab: the same records for one agent, plus Approve all at this step (N). The tab appears only when a play has an Approve step or approvals are pending.
• Slack: approvers linked to Slack get Approve and Reject buttons (with reasons Not a fit, Wrong timing, Already in touch, Wrong person), and Approve all.

When you confirm, CluGTM explains what happens next (“Records continue on the saved Approved path.” or “Records take the Rejected path. With no Rejected path, they leave the play.”) and lets you add a Reason, optional. When you approve a single record, you can edit the fields shown before it continues, except emails, phones, LinkedIn URLs and IDs.

Who can decide

An approver listed on the step, or an organization admin. In Slack, only the linked approver can use the buttons. The agent must be on: inside a paused agent the Approvals tab shows “Turn the agent on to decide.” With nothing pending, the inbox shows “No approvals waiting”.

Secrets

Secrets hold tokens and keys for Webhook step authentication, so they never appear in a play or in chat.

• Where: Settings → Connections → Secrets. Visible to organization admins in workspaces that have Agents.
• Add secret: a Name (up to 80 characters) and a Value (up to 8,192 characters), then Save secret. “The value will be hidden after saving.”
• Saved secrets lists each secret with a short hint (•••• and the last characters) and when it was last used.
• Archive removes a secret from use (“It will no longer be available for Webhook steps.”). A secret that a Webhook step still uses cannot be archived.
• Values are encrypted at rest. Only Webhook steps can use secrets; Code steps cannot.

Related

• Plays and triggers: what starts a play, schedules, runs and auto-pause
• Agents: build, test and turn on agents
• Skills: Research, Qualification, Custom and Employment check
• Sequences: the CluGTM sequences Add to sequence uses
• CRM duplicate cleanup
• Integrations: HubSpot, Salesforce, Attio, Slack, Teams, Gong, 6sense and more
• Credits and pricing