Workflow step types and settings
This is the full catalogue of steps the Workflow Builder offers and the settings each one exposes - the newer of the two workflow builders in the workspace, the one with condition steps and goals (see Workflows). Use it when you are assembling a multi-step run and want to know exactly what every step does and every toggle it carries. The builder groups its steps into three lists: Agents (the research and enrichment work a step performs on a record), Actions (steps that label a record or write a value onto it), and Routing (the Condition step that sends records down different paths).
The Workflow Builder appears for teams with the Create workflows permission; most teams will not see it in the left navigation until an admin grants that access. See Teams, roles, and permissions.
Agent steps
Section titled “Agent steps”Each agent step runs one agent against every record that reaches it. You pick the step from the Possible steps list on the left of the builder, drop it on the canvas, and open it to set its options.
| Step | What it does |
|---|---|
| Website Finder Agent | Finds and verifies the company’s website. |
| Account Qualification Agent | Checks whether the account fits your ICP. |
| Account Research Agent | Researches accounts for relevant signals and context. |
| Account Plans Agent | Turns account research into a strategic plan. |
| Contact Finder | Finds the right people at each account. |
| Contact Qualification Agent | Checks whether a contact matches your buyer persona. |
| Contact Research Agent | Researches contacts for relevant context. |
| Email/Phone Finder | Finds a verified email and phone for a contact. |
| Play Agent | Writes personalized outreach for a contact. |
There is no separate Digital Twin step to add. A contact’s Digital twin is generated automatically once Contact Qualification Agent has qualified it as an ideal-buyer-profile fit with a persona - there is nothing extra to configure for it here.
Some agent steps depend on earlier ones. When a step needs prior results, the builder shows a note at the top of its panel listing what the record must already have. Those prerequisites are:
| Step | Record must already have results from |
|---|---|
| Account Research Agent | Account Qualification Agent |
| Account Plans Agent | Account Qualification Agent |
| Contact Finder | Account Qualification Agent |
| Contact Qualification Agent | Account Qualification Agent |
| Contact Research Agent | Contact Qualification Agent |
| Play Agent | Account Qualification Agent, Account Research Agent, Contact Qualification Agent |
Website Finder Agent and Email/Phone Finder have no prerequisites.
Settings shared across agent steps
Section titled “Settings shared across agent steps”Skip already-processed records
Section titled “Skip already-processed records”Every agent step opens with a switch that lets you reuse earlier results instead of running the agent again. It saves credits and keeps a workflow consistent with previous runs. The wording is tailored to each step:
| Step | Switch heading |
|---|---|
| Website Finder Agent | Skip accounts that have already been searched |
| Account Qualification Agent | Skip accounts that have already been qualified |
| Account Research Agent | Skip accounts that have already been researched |
| Account Plans Agent | Skip accounts that already have an account plan generated |
| Contact Qualification Agent | Skip contacts that have already been qualified |
| Contact Research Agent | Skip contacts that have already been researched |
| Email/Phone Finder | Skip contacts that already have a verified email and phone |
| Play Agent | Skip contacts that already have plays generated |
Contact Finder does not carry this switch.
Run on a chosen set vs everything
Section titled “Run on a chosen set vs everything”The agent steps that draw on a library of items you configure in the Training Center (research agents, account plans, plays) and the Account Qualification step (which draws on your verticals) share an Auto-include all switch:
| UI label | What it means | Values |
|---|---|---|
| Auto-include all | Selects every item and automatically includes any new ones added in the future. | On / off |
When Auto-include all is off, you pick the exact items from a searchable list. What you pick differs by step:
| Step | What you select when Auto-include all is off | Validation |
|---|---|---|
| Account Qualification Agent | The verticals (grouped under their ecosystems) to qualify against. | At least one vertical required. |
| Account Research Agent | The account research agents to run. | At least one required. |
| Account Plans Agent | The account plans to generate. | At least one required. |
| Contact Research Agent | The contact research agents to run. | At least one required. |
| Play Agent | The plays to generate. | At least one required. |
Filtering records to a subset of the accounts or contacts in the run (rather than choosing which agents fire) is done with a Condition step, described below.
Website Finder Agent settings
Section titled “Website Finder Agent settings”| UI label | What it means | Values |
|---|---|---|
| Skip accounts that have already been searched | Reuses an earlier Website Finder result for the account instead of searching again. | On / off |
| Effort level | How hard the agent works to identify and confirm the company. Low Effort is best when the right company is easy to find or confirm; High Effort is best when identifying the correct company needs deeper reasoning; Smart Mode starts with the quick search and runs the deep search only when no website is found, finding about as many websites as High for fewer credits. | Low Effort (0.3 credits), High Effort (0.5 credits), Smart Mode (~0.37 credits on average: 0.3 when the quick search is enough, 0.8 when the deep search also runs) |
Account Qualification Agent settings
Section titled “Account Qualification Agent settings”| UI label | What it means | Values |
|---|---|---|
| Skip accounts that have already been qualified | Reuses the previous ICP decision instead of re-qualifying the account. | On / off |
| Auto-include all | Qualifies against every vertical and auto-includes new ones. | On / off |
| Verticals | When Auto-include all is off, the verticals to qualify against, grouped by ecosystem and searchable. | Your configured verticals; at least one required |
Account Research Agent settings
Section titled “Account Research Agent settings”| UI label | What it means | Values |
|---|---|---|
| Skip accounts that have already been researched | Reuses existing research findings instead of researching again. | On / off |
| Auto-include all | Runs every account research agent and auto-includes new ones. | On / off |
| Agents | When Auto-include all is off, the account research agents to run. | Your configured research agents; at least one required |
Account Plans Agent settings
Section titled “Account Plans Agent settings”| UI label | What it means | Values |
|---|---|---|
| Skip accounts that already have an account plan generated | Keeps an existing plan instead of generating a new one. | On / off |
| Auto-include all | Generates every account plan and auto-includes new ones. | On / off |
| Plans | When Auto-include all is off, the account plans to generate. | Your configured plans; at least one required |
When you configure this step, the builder reminds you that an account plan is only as good as the account research feeding it - pair it with the research agents relevant to the account and keep their results current for the strongest output.
Contact Finder settings
Section titled “Contact Finder settings”Contact Finder combines finding the right people with optionally searching for their email and phone. It has no skip-already-processed switch.
Search for email
Section titled “Search for email”| UI label | What it means | Values |
|---|---|---|
| Search for email | Turns on email finding for each contact found. | On / off |
| Email verification | Verifies found emails with third-party providers. | On / off |
| If we can’t find an email for a contact | Skip and try someone else: the system looks for an additional contact. Add them anyway: the contact is still added to your list but excluded from later steps (Contact Research, play generation) so you don’t spend credits on contacts you can’t reach. | Skip and try someone else, Add them anyway |
Search for phone number
Section titled “Search for phone number”| UI label | What it means | Values |
|---|---|---|
| Search for phone number | Turns on phone finding for each contact found. | On / off |
| Phone intent scoring | Scores phone numbers for buying intent. Available only when the phone-scoring integration is connected; otherwise the option is disabled with a link to set it up. | On / off |
| Phone scoring model | Shown when phone intent scoring is on. Lightning Scoring is a single-pass model that identifies a large portion of high-propensity contacts (under-24-hour turnaround); Titan Scoring uses a multi-pass model to extract every identifiable high-propensity contact (under-5-day turnaround). | Lightning Scoring, Titan Scoring |
| If we can’t find a phone number for a contact | Skip and try someone else: the system looks for an additional contact. Add them anyway: the contact is still added to your list but excluded from later steps (Contact Research, play generation). | Skip and try someone else, Add them anyway |
You must enable Search for email or Search for phone number (or both) for the step to be valid.
Effort and contact selection
Section titled “Effort and contact selection”| UI label | What it means | Values |
|---|---|---|
| Effort level | How much reasoning the agent applies to each candidate. Low: best when your persona is simple and clearly defined; the same contact search as Medium with less per-match assessment. Medium: looks more carefully at each candidate before deciding fit, best for complex personas. High: uses stronger reasoning models throughout, best when contacts are hard to find or the fit call is difficult. | Low (1 credit), Medium (2 credits), High (3 credits) |
| Select what contacts would you like to find | Chooses how the per-account headcount is set: a flat number per account, or a per-persona breakdown. | Contacts per account, Contacts per persona |
| Contacts per account | Shown for the “Contacts per account” option. How many contacts to find at each account. | A number from 1 to 100 |
| Country (optional) | Shown for the “Contacts per account” option. Restricts the search to a country, or leave unset. | Any country, or none |
| Per-persona counts | Shown for the “Contacts per persona” option. Personas are grouped by expertise with a running total shown at the top; for each persona you set a count with a plus/minus counter, and can turn on a country filter for that persona alone. Personas come from the verticals on the accounts in the run. | A count per persona (up to 50 each); optional country per persona |
| Custom instructions | Free-text guidance for the agent. | Optional text |
For the per-persona option, at least one persona must have a count above zero, and no single persona may exceed 50.
Contact Qualification Agent settings
Section titled “Contact Qualification Agent settings”| UI label | What it means | Values |
|---|---|---|
| Skip contacts that have already been qualified | Reuses the previous persona match instead of re-qualifying the contact. | On / off |
| Follow contacts who changed jobs | When a contact has left their company, marks them as not a fit on the original account and creates a new account for them at their current company. | On / off |
| then (step picker) | Shown when “Follow contacts who changed jobs” is on: the step that the newly created account and contact continue to. | Any other step in the workflow |
| Find a replacement for contacts who left | When a contact has left their company, searches their original account for one person with the same persona (or the same job title, if the contact who left had no persona). A replacement who fits continues to this step’s own then step. Works on its own or together with “Follow contacts who changed jobs”. Charged as a Contact Finder search. | On / off |
Contact Research Agent settings
Section titled “Contact Research Agent settings”| UI label | What it means | Values |
|---|---|---|
| Skip contacts that have already been researched | Reuses existing research instead of researching the contact again. | On / off |
| Auto-include all | Runs every contact research agent and auto-includes new ones. | On / off |
| Agents | When Auto-include all is off, the contact research agents to run. | Your configured research agents; at least one required |
Play Agent settings
Section titled “Play Agent settings”| UI label | What it means | Values |
|---|---|---|
| Skip contacts that already have plays generated | Keeps existing plays instead of generating new ones. | On / off |
| Auto-include all | Generates every play and auto-includes new ones. | On / off |
| Plays | When Auto-include all is off, the plays to generate. | Your configured plays; at least one required |
Email/Phone Finder settings
Section titled “Email/Phone Finder settings”The standalone Email/Phone Finder step finds verified contact details for contacts you already have.
| UI label | What it means | Values |
|---|---|---|
| Skip contacts that already have a verified email and phone | Uses existing contact details instead of running the search again, so you don’t pay for the same email or phone twice. | On / off |
| Search for email | Turns on email finding. | On / off |
| Email verification | Verifies found emails with third-party providers. | On / off |
| If a contact already has an email | Keep the existing email: skips the email search for that contact. Always search for a fresh one: runs the search anyway and can replace what is there. | Keep the existing email, Always search for a fresh one |
| Search for phone number | Turns on phone finding. | On / off |
| Phone intent scoring | Scores phone numbers for buying intent. Available only when the phone-scoring integration is connected; otherwise disabled with a link to set it up. | On / off |
| Phone scoring model | Shown when phone intent scoring is on. | Lightning Scoring, Titan Scoring |
| If a contact already has a phone number | Keep the existing number: skips the phone search for that contact. Always search for a fresh one: runs the search anyway and can replace what is there. | Keep the existing number, Always search for a fresh one |
You must enable Search for email or Search for phone number (or both) for the step to be valid.
Action steps
Section titled “Action steps”Action steps do no research. They put something on every record that reaches them, so a later list, filter, or CRM view can find exactly the records that took a particular path through the workflow. Both are free: they use no credits. Each has an Entity type at the top of its panel - Account or Contact - and the sidebar lists each step once; you choose which kind of record it works on in the panel. The card on the canvas carries an account or contact chip to match, and a one-line summary of what it will do, or missing configuration until it is set up.
| Step | What it does |
|---|---|
| Add tags | Adds the tags you choose to the account or contact. |
| Set attribute | Writes a value into one of your custom fields on the account or contact. |
Add tags settings
Section titled “Add tags settings”| UI label | What it means | Values |
|---|---|---|
| Entity type | Whether the step tags accounts or contacts. The tag list offers that record type’s existing tags. | Account, Contact |
| Tags | The tags every record that reaches this step receives. Pick existing tags, or type a new name and press Enter to create it. | At least one tag; each up to 255 characters |
Tags are only ever added: a record keeps any tags it already had. The canvas card shows the first three tags and a +n chip for the rest. The same tag typed twice in different capitals is applied once.
Set attribute settings
Section titled “Set attribute settings”| UI label | What it means | Values |
|---|---|---|
| Entity type | Whether the step writes to accounts or contacts. Switching it clears the chosen field, because account and contact custom fields are separate lists. | Account, Contact |
| Custom field | The custom field to write to, searchable. If you can manage settings, Create new adds a field without leaving the builder. With none defined yet, the panel says so and points to Settings. | One existing custom field of the chosen entity type |
| Value | The text written to that field on every record that reaches this step. | Required, free text |
One step sets one field. To set several fields, add one Set attribute step per field. The value replaces whatever that field held on the record before. The canvas card reads “[field] set to [value]”.
How action steps behave in a run
Section titled “How action steps behave in a run”- The tag or value is written the moment a record reaches the step, not at the end of the run.
- A record that is not saved in your workspace is skipped by the step, with a reason in the run report.
- If the write fails - for example because the custom field was deleted after the workflow was built - that step shows an error for the record, and the record still carries on to the step’s then step. A failed label never holds up the rest of the workflow.
- When a record passes more than one of these steps, the results add up: it ends with the tags from all of them, and if two steps set the same field, the later one wins.
Use them to close the loop on a run. A tag on every account that came back a fit, or a campaign name stamped on every contact that got plays, turns “the records this workflow handled” into something a saved view, an export, or your CRM can pick up later without anyone rebuilding the list by hand. See Define custom fields for creating the fields a Set attribute step writes to.
Eva: action steps exist only in the Workflow Builder - the Legacy builder has no equivalent, and neither can be launched on its own as an agent outside a workflow. In the run report and task feed they appear as “Tag account”, “Tag contact”, “Set account attribute” and “Set contact attribute”. The run report explains a skip as the record not being saved in the workspace (“nothing to tag” / “the attribute couldn’t be set”), and a failure as the tags or value not being accepted, with a hint that the custom field may have been deleted and to check it in Settings under Custom fields. Treat a customer quoting either as the behaviour described above, not as a bug. When Evergrowth turns a workflow into a shared Evergrowth template, a Set attribute step loses its custom field (each workspace has its own fields) and has to be picked again. Values are fixed text: the step does not compute a value from research or copy one field into another.
Condition step (routing)
Section titled “Condition step (routing)”The Condition step is the only step in the Routing group. It does no enrichment; it routes records down different paths based on rules. The builder calls it Condition.
| UI label | What it means | Values |
|---|---|---|
| Entity type | Whether this Condition routes accounts or contacts. The filters you can build depend on this choice; changing it clears any filters already set. | Account, Contact |
| Branches | The ordered set of routes leaving this step. Each branch sends matching records to a chosen next step. | Add as many as you need |
Each branch carries:
| Branch element | What it means | Values |
|---|---|---|
| Filters | Optional. With no filters the branch always runs; the panel reads “Always runs (add filters to restrict)”. Add filters and it reads “Run when filters match:”. You can build filters by hand or prefill them from a saved view of the matching entity type. | Filter group, or none |
| next / then | The step that records take when the branch runs. It is labeled “next” while the branch has no filters and “then” once you add filters (in which case records take it when the filters match). | Any other step |
| else | Shown only once a branch has filters: the step that records take when the filters do not match. | Any other step, or none |
Every step: where it goes next, and the starting point
Section titled “Every step: where it goes next, and the starting point”These two controls are not agent-specific.
| Control | What it means | Values |
|---|---|---|
| then (next step) | On every agent and action step, the step that records continue to after this one. | Any other step, or none |
| Make this step as starting point for this workflow | Marks the step where the workflow begins. Exactly one step is the starting point; the builder flags any other step that nothing connects to as unreachable. | On / off |