Workflows and automation
A workflow is a sequence of agent work you assemble yourself, laid out as a chain of steps that records flow through one after another. Each step runs one agent - qualify the account, research it, find the right people, draft the outreach - and the records that come out of one step become the input to the next. Where a single agent run does one job, a workflow stitches several jobs into one motion, so a list of raw accounts can go in one end and come out the other qualified, researched, staffed with the right contacts, and ready to work.
If a playbook is a pre-built recipe Evergrowth ships for a common go-to-market motion, a workflow is the same idea with the lid off: you decide which agents run, in what order, and on which records. A playbook is the packaged version; a workflow is the general case behind it.
What a workflow is made of
Section titled “What a workflow is made of”Every workflow is a set of steps plus the connections between them. There are two kinds of step.
- Agent steps do the actual work. Each one runs a single agent against the records that reach it - finding a company’s website, qualifying an account against your verticals, researching it for signals, generating account plans, finding contacts, qualifying those contacts against your buyer personas, researching the contacts that qualify, building a digital twin, finding a verified email and phone, or writing personalized outreach. An agent step carries its own settings, so you tune what that step looks for the same way you would tune the agent on its own. The full set of step types lives in the step-type reference.
- Condition steps do the routing. A condition step inspects each record and sends it down a different path depending on what it finds, with an “otherwise” path for everything that does not match. This is what turns a straight line of steps into a decision tree - qualified accounts go one way, the rest go another, and each branch can run a different set of agents.
Two more pieces hold a workflow together. Every workflow has a single starting step - the entry point where records begin - and steps are linked so each one points to whatever comes next. A workflow is only valid when there is a starting step and every step is actually reachable from it; a step that nothing connects to is flagged before the workflow can run, so you never quietly leave work stranded. Some agent steps also depend on earlier ones - research, for instance, expects the account to have been qualified first - and the builder enforces those dependencies so steps run in an order that makes sense.
Eva: The builder is labelled “Workflows V2” in the navigation today; treat that and “custom workflow” and “workflow” as the same thing. A condition step is presented as a routing node; when a customer talks about “branching,” “routing,” or “the decision tree,” they mean condition steps.
One-time runs and scheduled runs
Section titled “One-time runs and scheduled runs”A workflow can run two ways, and the difference is only what kicks it off.
A one-time run points the workflow at a specific set of accounts or contacts and works through them once. You use it when you have a list in front of you right now - an import you just made, a segment you filtered down, a batch handed to you - and you want it processed end to end.
A scheduled run turns the same workflow into a standing routine. You attach it to a daily, weekly, or monthly cadence, and from then on it runs on its own at the time you set, with an optional end date or no end at all. A schedule can be active or paused, and if the underlying workflow stops being valid the schedule is marked so and held back rather than firing broken work. Scheduling is what lets a workflow keep a source or signal continuously worked while your reps are busy selling - the same automated-coverage idea that powers playbooks, applied to a workflow you built yourself.
This is the bridge back to playbooks. A playbook is essentially a workflow Evergrowth has already designed and tuned for a recurring motion - filling new-business gaps, qualifying inbound leads, scheduled research, and the rest. Building a workflow and scheduling it is how you create that same kind of standing automation for a motion that does not have a packaged playbook, or how you adapt a packaged one to how your team actually sells.
Why it matters
Section titled “Why it matters”The point of a workflow is that your best sequence stops living in someone’s head. The order a strong rep would follow - confirm fit, then dig in, then find the people, then write something worth sending - gets captured once and applied to every record the same way, at a depth no rep would reach for the whole list by hand. Branch on the verdict so you spend the expensive research only on accounts that earned it. Schedule it so the pipeline is always being worked, not just when someone remembers. The result is consistent, repeatable go-to-market that scales past the number of people you have to run it.
Availability
Section titled “Availability”The workflow builder is an advanced capability and is not yet generally available. It is gated to administrators and is not exposed in the production workspace, so most teams will run the packaged playbooks and on-demand agent runs rather than build workflows from scratch. If you do not see a workflows area in your workspace, that is expected. The how-to pages below describe the builder for the environments where it is enabled.