Workflows

A workflow runs automatically when something happens, and moves through a series of steps to get work done — pull the records it needs, decide whether to proceed, run an agent, and take an action like posting to Slack, sending an email, or updating your CRM. It’s how you turn a repeated revenue task into something that happens on its own. Every workflow is a trigger followed by one or more steps, connected in order. The trigger says when it runs; the steps say what it does.

​

Components

• Triggers — what starts a workflow: a meeting starting or ending, a schedule, or a Salesforce record being created or changed.
• Find & filter records — pull the accounts, contacts, deals, and more that a workflow should act on, and gate a run so it only continues when your conditions are met.
• Actions — what a workflow does: send email, write to Salesforce, write to HubSpot, send a Slack message, or run an agent.
• Loops — repeat a step for every record in a set, so one workflow can act on many.
• Human review — pause before an action and wait for a person to approve.
• Folders — organize your workflows as the set grows.

​

Draft, then publish

Every workflow has a live version and, while you’re editing, a draft. Changes you make go to the draft — the live version keeps running untouched until you publish. Nothing runs until you publish. Publishing installs the trigger and makes the workflow live; unpublishing removes the trigger to pause the workflow without deleting it.

​

Test before you publish

You can test a draft against real data to see what each step would do. A test run is always a dry run: it never sends a Slack message or email, and never writes to your CRM — a write step reports the value it would have set instead of setting it. Test freely, then publish when it looks right.

​

Use data from earlier steps

Steps can reference data the workflow already has — the record that triggered it, or the output of an earlier step — using variables written as {{...}}. For example, an email step can put the account name in the subject, or a Slack message can include a summary an agent produced. Variables are filled in with live values each time the workflow runs.

​

Next steps

1. Sign in to Clearskies and open the workflow builder
2. Choose a trigger for when your workflow should run
3. Add the steps that find data and take action

Questions? We’re here to help at support@clearskies.cc