Skip to main content
A Workflow is: when something changes on a saved view, do these actions. That’s the whole model. There’s no separate trigger language to learn — the view you already built with the filter bar is the trigger.

​
View + When + Actions

Every Workflow has three parts:
  • View. The saved view it watches. Any view over Accounts or People works.
  • When. One of:
    • Enters — fires the first time a record starts matching the view.
    • Leaves — fires when a record that matched stops matching.
    • Schedule — fires on a cron you set, over everyone in the view at that moment, as one digest.
  • Actions. One or more things to do to each record that fired.

​
Actions

  • Slack — post to a channel
  • DM owner — Slack DM to the record’s owner
  • Email
  • Webhook
  • Set tier
  • Set owner
  • Add tag — what used to be Set status. Add a tag from any group; a single-choice group swaps out the tag already there
  • Add to list
  • Dismiss
  • CRM note — log a note on the matched CRM record
  • CRM task — create a task for the owner in your CRM
  • Push to CRM — create the company or contact if it isn’t there yet, skip if it already is
A Workflow can chain several actions. They all run for every record that fired.

​
The fire guarantee

Clustr fires within 15 minutes of learning a fact, within two minutes for anything done in Clustr or your CRM. A LinkedIn signal landing is the slower path; a tag you set, a deal you moved, an intro you requested, or a stage change in your connected CRM is the fast one.
The first pass after creating or turning on a Workflow fires nothing. It records who’s already a member so only real transitions — entering or leaving after that point — trigger an action. Turning a Workflow on over an existing view with 500 Burning accounts in it does not send 500 Slack messages.
A single pass caps at 200 fires. If more than 200 records transition at once, the rest are picked up on the next pass rather than dropped.

​
Building one

Open Workflows, pick New workflow, and either start from a template or build from scratch:
  1. Pick the view, or create one from the picker.
  2. Choose Enters, Leaves, or Schedule.
  3. Add actions from the menu, one at a time.
  4. Save. If the view already has matching records, they’re seeded silently — nothing fires until the next real change.
Every Workflow has a Runs tab: one row per pass, what fired, and where each action delivered or failed.

​
Templates

Three Workflows are one click away for a new workspace:
  • Hot accounts — Score A+ or A, Burning → Slack channel
  • New deal at an account we can reach — open deal, path at 75%+ → DM the CRM owner
  • Competitor is here — a competitor present on the account → Slack channel
Picking a template opens the editor prefilled; nothing is created until you save.

​
Every action leaves a trace

Whether a Workflow does it or you do it by hand, the same activity entry lands on the record. A Workflow that fired but delivered nowhere is visible on both the run and the record, not silently swallowed.