Skip to content

Build a workflow in the workflow builder

A workflow chains agents together so a set of accounts or contacts moves through your full go-to-market sequence in one pass: qualify, research, find people, find their email and phone, write plays, and so on. You build it once on a visual canvas, then run it on the records you choose. For background on what a workflow is and how it executes, see Workflows.

Workflows in the left navigation opens a hub of cards. Workflow Builder (badge New) is the one this page covers, and its count is the number of workflows built there. If your workspace still has workflows from the older builder, a second card badged Legacy holds them until that builder is sunset at the end of 2026; a workspace with none never sees that card (see Workflows). Workflow Scheduler holds your scheduled runs. The Workflows nav item itself needs only general automations access; opening either card to build or edit needs the Create workflows permission specifically. If you do not see what you expect, check Teams, roles, and permissions or ask an admin to adjust your team.

  • Decide the order your agents should run in. Some agents can only complete when an earlier agent has already produced results on the record. For example, Account Research, Contact Finder, and Contact Qualification all require Account Qualification to have run first, and Play Agent requires Account Qualification, Account Research, and Contact Qualification. The builder shows these prerequisites on each step, but planning the order first saves rework.
  • Have your verticals, research criteria, personas, plans, and plays set up in the Agent Training Center so the relevant steps have something to reference.
  1. Open Workflows from the navigation, choose the Workflow Builder card, then select Add new in the top right. It offers three ways to begin: Start from scratch, which opens the builder on a blank canvas and is what the rest of these steps assume; Use template, which opens a gallery of ready-made sequences - see Start from a template; and Build with Eva, which hands the job to Eva instead - see Have Eva build it for you. All three need the Create workflows permission.
  2. Name the workflow. The name field sits at the top left of the builder header; click it and type. You can also set the name and tags on the Settings tab (see step 10).
  3. Stay on the Workflow setup tab. The builder has three tabs: Workflow setup (the canvas where you assemble and connect steps), Settings (name and tags), and Target (an optional point at which a run stops). The setup tab is open by default.
  4. Add a step from the left sidebar. The sidebar is titled Possible steps with the hint “Drag onto the canvas, or click to add”. It has three groups:
  • Agents: each agent you can add as a step. The available agents are Website Finder Agent, Account Qualification Agent, Account Research Agent, Account Plans Agent, Contact Finder, Contact Qualification Agent, Contact Research Agent, Email/Phone Finder, and Play Agent. Each shows a one-line description of what it does. There is no separate Digital Twin step to add - a contact’s Digital twin is generated automatically once Contact Qualification Agent qualifies it, so it does not need its own place in the chain.

  • Actions: Add tags (“Adds tags to the account or contact”) and Set attribute (“Writes a value to a custom field on the account or contact”). They do no research and cost no credits; they label the records that reach them so you can find those records again later.

  • Routing: a single Condition step that “Routes records down different paths based on rules”. Use it to split records onto different paths based on filters.

    Hover any item for a card that spells out what the step is for before you commit to it: When to use, Needs results from (each prerequisite agent ticked green when it is already in this workflow, or flagged as “not in this workflow yet”), and Produces. A step that needs nothing says so.

    There are two ways to place a step. Drag an item from the sidebar onto the canvas and drop it where you want it; a dashed outline follows the cursor so you can see where it will land. Or click it, and the step is placed just below the open end of the flow, with the canvas panning to it if that spot was off-screen.

    Either way, if the flow has exactly one loose end, the new step is wired to it automatically and a confirmation reads “Connected after [step name]” so you know what it joined. Where the target would be ambiguous - several loose ends, or none - the step is placed unconnected and you wire it yourself in step 6. The first step you add automatically becomes the starting step.

  1. Configure the step in the right sidebar. Clicking a card on the canvas opens the Edit step panel on the right. The panel header shows the step’s name and description. If the step needs results from earlier agents, a note reads “For this step to complete, the record must have results from:” followed by the required agents in bold. Below that are the step’s own settings (for example, which verticals an Account Qualification step checks against, or which plays a Play Agent writes). Settings differ per agent; see the individual agent how-to pages for detail.

    For an action step, first choose the Entity type, Account or Contact. On Add tags, pick tags in Tags or type a new one and press Enter; every record that reaches the step gets all of them. On Set attribute, choose the Custom field to write to (or Create new, if you can manage settings) and type the Value. One step sets one field, so add a step per field. The card on the canvas then shows the tags, or “[field] set to [value]”, and reads missing configuration until the step is filled in. For how these steps behave in a run, see Action steps.

  2. Connect steps with the then dropdown. In each agent step’s edit panel, a then label sits next to a dropdown that reads “Select step”. Pick the step that should run next. On the canvas, the card shows the chosen step under a next label; leave it blank and the card reads “end of flow”, meaning the path ends there.

  3. For the Contact Qualification Agent, you can decide what happens to contacts who have left their company. Two switches cover the two halves of that, and you can turn on either or both:

    • Follow contacts who changed jobs marks a contact who has left their company as not a fit on the original account, creates a new account for them at their current company, and then routes them to whichever step you pick in the then dropdown that appears (shown as the else path on the card).
    • Find a replacement for contacts who left searches the contact’s original account for someone with the same persona to take their place. If the contact who left had no persona, the search looks for their job title instead. It looks for one person, and the replacement it finds has already been qualified, so a replacement who fits carries on to the step this Contact Qualification step leads to with then, just like any other contact that came back a fit. The replacement must meet the same email and phone requirements as the workflow’s Contact Finder step; in a workflow without one, it needs a valid email, unless the workflow’s Email/Phone Finder step only looks for phone numbers. If nobody suitable turns up after a few searches, the contact’s record in the run says no replacement was found. Each search is charged as a Contact Finder search.

    With both switches on, a contact who left is followed to their new company and their old seat is refilled. Only one Contact Finder search runs on an account at a time, so if a replacement search and a Contact Finder step reach the same account together, one waits for the other to finish.

  4. For a Condition step, set its branches in the edit panel:

  • Choose the Entity type: Account or Contact. This decides which fields the branch filters can use.
  • Under Branches, select Add to create a branch. For each branch you can Add filters (or Prefill with views from a saved view) to restrict when it runs, then pick the step to run with the then dropdown. A branch with no filters always runs and is labeled next. When a branch has filters, an else dropdown lets you route records that do not match the filters to a different step. A branch with no filters is a dead end until you connect it.
  1. Set the starting step. Every workflow needs one step marked as the start. In any step’s edit panel, turn on Make this step as starting point for this workflow. The starting step shows a Start chip on its card. The first step you added is set as the start automatically; switch it to another step if needed.

  2. Optionally open the Settings tab to set the workflow name and tags. Tags are free text you create as you type; they group and label workflows in the list. The name also appears in the header field.

  3. Optionally open the Target tab to set where a run stops. By default a workflow runs every record you launch it on through every step. The tab, headed Workflow target, holds one Stop early at a target card: switch it on and it reads Stop at [number] [unit]. Type the number and pick what counts from the dropdown - one result for each agent step the workflow contains (for example qualified accounts, contacts found, contacts with an email, or contacts with plays), plus records matching custom conditions, where you choose Count records of type (Account or Contact) and build the filter conditions a record has to meet. Runs then end once they have enough, and records they did not reach stay untouched and cost nothing.

    A target set here is saved with the workflow and is where every launch starts: whoever launches it can change the number or switch it off for that run, without editing the workflow. See Stop a run early at a target.

  4. Arrange and view the canvas:

    • Drag a card by its body to reposition it.
    • Pan the canvas by dragging an empty area of the background, or by holding the middle mouse button and dragging.
    • Zoom with the controls in the bottom right corner: the minus and plus buttons step the zoom, and clicking the percentage resets it to 100%. You can also double-click an empty area of the background to zoom in on that spot, and hold Cmd (Ctrl on Windows) while double-clicking to zoom back out.
    • When you reopen a workflow you have already built, the canvas opens zoomed to fit the whole thing on screen and centred on it, rather than at 100% on the top-left corner. On a long chain that means you see the shape of the workflow first and zoom in on the part you came for, instead of hunting for it.
  5. Work on several steps at once. On a workflow of any size it is faster to move or reuse a block of steps than to place each one:

    • Select several steps. Hold Cmd (Ctrl on Windows) and drag across an empty area of the background to draw a selection box around the cards it touches, or hold Cmd and click cards one at a time. Cmd+A selects every step, and Esc clears the selection. A bar at the bottom of the canvas shows how many steps are selected, along with the shortcuts below.
    • Move them together. Dragging any card in a selection moves the whole group, keeping the layout you already arranged.
    • Copy, cut, and paste. Cmd+C copies the selected steps, Cmd+X cuts them, and Cmd+V pastes. Paste lands the copies where your cursor is on the canvas. Every pasted step is a new step with its own identity, and the connections between the steps you copied are kept - so lifting a qualify-research-plays block out of one workflow and pasting it into another rebuilds that stretch in one action. Connections to steps you did not copy are not carried over, so reconnect the block’s entry and exit with the then dropdown.
    • This works across workflows and across browser tabs: copy in one workflow, open another, and paste. Copying steps does not change the workflow you copied from.
  6. Copy or remove a step from its card. Each card on the canvas carries an overflow menu (the … button) with two actions:

    • Duplicate makes a second step with the same agent and the same settings, dropped just to the right of the original. Nothing points at the copy yet, so connect it with the then dropdown on whichever step should lead into it - until you do, the builder counts it as a step nothing connects to. Use this when two steps differ in one setting (the same research agent at a different effort, a second condition with one branch changed) instead of configuring the second from scratch.
    • Delete removes the step and clears the connections that pointed at it, so the steps that led into it read end of flow rather than pointing at something that is gone. If you delete the starting step, the start moves to another step, so check which one carries the Start chip afterwards.
  7. Save. Select Create in the top right of the header. If the workflow has problems (no steps, no starting step selected, a required setting missing, or a step that nothing connects to), an orange chip in the header shows the number of issues; hover it to read each one, and each affected card is outlined and carries a warning marker. Fix the issues, then Create again. Beside it, Save as template saves the canvas you have assembled as a reusable template instead - see Save your own as a template.

When you select Create, the workflow is saved and you are taken to its edit view, where a confirmation appears. The new workflow now shows in the Workflows list as a card with the agent icons it uses and any tags you added. Building a workflow does not run it on any records; to do that, open the workflow and run it on a selection of accounts or contacts. See Run a workflow.

To edit a workflow later, open it from the Workflows list (the builder opens with your steps and connections in place) and select Update to save your changes. To make a copy, open the menu on a workflow card and choose Duplicate; this opens the builder pre-filled with the same steps under the name “(original name) (copy)” so you can adjust and save it as a separate workflow. To remove one, choose Delete from the same menu and confirm in the Delete workflow? dialog.

Every workflow card carries a star beside its menu. Select it to add that workflow to your favourites and it jumps to the front of the list; select it again to remove it. The tooltip reads Add to favourites or Remove from favourites, and a favourited star is filled and orange.

Favourites are yours, not the team’s. Starring a workflow changes the order you see it in and nobody else’s view, so two people can each keep their own three workflows at the top of the same shared list. The star is on the cards in both builders, and the same favourites lead the Select workflow dropdown when you launch a workflow on records - see Run a workflow on records now. Evergrowth’s own default workflows can be favourited like any other, and because they do not belong to a single workspace, starring one follows you into every workspace you work in.

This is worth doing the moment your list grows past a screen. A team that has built a dozen workflows usually runs two or three of them daily, and a starred pair at the top saves the scroll and the wrong-workflow mistake every time.

If you know what the workflow should achieve but not which steps get you there, Build with Eva in the Add new menu opens a conversation instead of a canvas. She asks what you want it to do, then assembles it for you.

This is the right route when the sequence is the hard part - which agents have to run before which, what to branch on, what a record needs to already have before a later step can work. Describing the outcome is a shorter conversation than laying out the same thing card by card, and she starts from the prerequisite order the builder would otherwise make you discover by trial. It is worth doing when you are new to workflows, when you are standing up a motion you have not automated before, or when you want a first draft to edit rather than a blank canvas.

What she builds is an ordinary workflow. It opens in the builder like any other, so you can rename it, move steps, change a setting, or throw it away. She can also put it on a schedule in the same conversation - see Set up a Workflow Scheduler automation.

Eva: reached from Add new in the Workflow Builder list, gated on Create workflows like the other two entries. It opens a normal chat with a briefing prompt; there is no separate wizard. The result is a real workflow the customer can then edit in the builder, so never describe it as a preview or a draft mode.

A template is a saved sequence you can open as the starting point for a new workflow, so the shape a strong rep would follow is adapted rather than rebuilt each time. On the Workflow Builder list, choose Add new and then Use template to open the Workflow Templates gallery.

The gallery has two tabs, each with a count: Account templates and Contact templates. A template sits under the tab for the record it starts from - a sequence whose first step works on accounts (finding the website, qualifying or researching the account, finding contacts at it) is an account template; one that starts by qualifying or researching a contact, or finding their email and phone, is a contact template. Your team’s own templates and the ones Evergrowth provides for common go-to-market motions are listed together. Each card shows the icons of the agents the template uses - hover one for its name - so you can tell a qualify-only template from a full qualify, research, and contacts chain at a glance. Search by name to narrow the tab you are on. Add new in the gallery abandons the template route and opens a blank canvas instead.

Select a card to open a preview. It lays out the template’s steps in order, with a marker on any routing step, and shows what the template is for under About this workflow. Choose Use This Template to open the builder pre-loaded with those steps, then tune them, name the workflow, and save it as your own. On a template your team saved, the card’s overflow menu (the … button) also offers Edit template, which opens the template itself for editing rather than creating a workflow from it, and Delete. Evergrowth’s own templates can only be edited or deleted by an admin.

A template is only a starting point. Nothing runs until you save the workflow and launch it on a set of records, so treat a template as a first draft to adapt to how your team sells rather than a finished, running automation. For the packaged, end-to-end motions Evergrowth ships and tunes, see Playbooks.

Each builder has its own template gallery. The gallery you open from the Workflow Builder list holds templates built in the Workflow Builder; the older builder marked Legacy keeps its own separate set. A template saved in one does not appear in the other, and it cannot be, because the two builders assemble a sequence in different ways (see Workflows). If your team saved templates in the older builder and you now want them in the Workflow Builder, rebuild each one there once and save it as a template again - which is worth doing anyway before the older builder is switched off.

Any workflow you assemble in the builder can become a template for the team. With the canvas set up the way you want it, select Save as template in the header, next to Create (or Update on a workflow you are editing). A confirmation appears and the template shows up in the gallery, under the tab for the record it starts from, the next time anyone opens it.

Save as template saves the template only - it does not create or update the workflow itself. If you want both, use Create or Update as well; the two buttons are independent, and the order does not matter. Both need the Create workflows permission, so a teammate who can only view workflows sees them greyed out.

An admin can take one of your team’s own templates and publish it as an Evergrowth template, so every workspace can start from it. On a team template’s card in the gallery, the overflow menu (the … button) offers Make global template for admins; it opens a confirmation explaining that the template moves out of your team templates and is published as an Evergrowth template. This is a one-way move of that template, not a copy: it stays in the gallery, but it now belongs to Evergrowth, so your team can no longer edit or delete it.

Two things happen to the sequence on the way out, because a template that every workspace shares cannot carry your workspace’s own setup:

  • Steps that pick specific things are widened to include all. A step that named particular verticals, research agents, plans, or plays is switched to cover all of them, so each workspace fills the step with its own data instead of pointing at rows that only exist in yours.
  • Anything that cannot be widened blocks the move. If the template filters on workspace-specific data - your qualification answers, your research results, your custom fields, your account plan or play results, or a named vertical, ecosystem, or owner - the confirmation refuses the move and lists every filter to fix, in a condition step or in the target, so you can clear them in one pass. A Contact Finder step set to work per persona type is blocked the same way and needs switching to contacts per account, since other workspaces do not have your persona cards.

Only Workflow Builder templates can be published this way; a template saved in the older Legacy builder cannot. A template that is already global, or that your workspace has set as its default or bound to an agent, is also refused - clear that binding first.

Think before publishing: a global template is Evergrowth-wide, and what makes a sequence great for your team is often the very specificity that has to be stripped out of it. The templates that travel well are the ones whose value is in the shape of the motion - the order of the steps and where the decision points sit - rather than in which of your agents each step calls.

Eva: this is an admin-only action in the Workflow Builder template gallery, reached from a team template card’s overflow menu, and it needs the Create workflows permission on top of the Admin role. The blockers are collected and shown all at once rather than one at a time, so a customer sees the full list of filters to clear in one go. When a customer asks why their template will not publish, the answer is almost always a filter on something only their workspace has - point them at the list the confirmation printed rather than guessing. It is a move, not a copy: after publishing, the template is an Evergrowth template and the team loses edit and delete on it. The gallery no longer splits team and Evergrowth templates into separate groups (it tabs by account and contact instead), so “it disappeared from Team templates” is not a symptom any more - it simply stays in the same tab.

Use it when a sequence you built has proved itself: rather than each rep reassembling the same qualify-research-contacts-plays chain and getting a slightly different version of it, one person saves the version that works and everyone starts from that.