Run a workflow on records now

A workflow runs a fixed sequence of agents over the accounts or contacts you choose, in one launch, instead of starting each agent by hand. Run one when you want the same set of steps applied to a record or a batch right now. For what a workflow is and how the steps fit together, see Workflows.

You can launch a workflow from a single account or contact, or from a selection on the accounts or contacts list. The launch control is hidden if you have read-only access, since read-only roles cannot start agents.

Before you start

You need a saved workflow to run. The picker lists the workflows that exist for your company, which always includes Evergrowth’s own Evergrowth Account Default and Evergrowth Contact Default - so there is something to run before your team has built anything. To build your own, see Build a workflow.
Pick the right list for the workflow. Account workflows run from the accounts side; contact workflows run from the contacts side.
Keep each account under 500 contacts per run. When a workflow reaches an account that brings 500 or more of its contacts into the run, it does not work that account: none of the workflow’s steps run on it, and those contacts are marked skipped. On a very large contact list, launch in smaller batches so no single company carries that many - see An agent did not run on a record.

Eva: the 500-contact ceiling is counted per account, per run - the contacts of one company that are in the same workflow run, not the size of the account in the workspace and not the total size of the selection. 600 contacts spread over many companies run normally; 600 contacts at one company do not. The run records the reason on the account as “Account has N contacts; the limit per run is 500. Split the account or reduce its contacts.” Retrying the same launch hits the same ceiling. It is a current safeguard for very large accounts and may change.

Steps

From a single account or contact

Open the account or contact you want to work on and look at the action row at the top of the page.
Open the Select workflow action. A searchable dropdown opens listing your workflows by name, from both builders. Each row shows the workflow name and any tags on it. Hover a row for a preview: a Workflow Builder workflow draws its step chain, branches included, while an older legacy workflow shows its fixed pipeline, and both show the About this workflow description and tags underneath. The preview is how you confirm you have the right one before launching on a large selection. In the browser extension the dropdown has no hover preview, but the star works there too.
Type in the search box to narrow the list if you have many workflows. Your favourites are already at the top of it: the star on each row adds or removes a workflow from your own favourites, and favourited ones lead the list before the rest, which stay in alphabetical order. The favourites are personal to you, so starring one changes only your list - see Keep the ones you use at the top.
Click the workflow you want. A Launch workflow dialog opens, showing the record you selected. On a launch of more than one record it carries a Stop early at a target card, so you can end the run once it has produced enough instead of pushing every record through every step - see Stop a run early at a target below. On a single record the card does not appear, since one record cannot stop early.
Read the Estimated N credits line beside the record count before you commit. It prices this exact launch - these steps, these records, your current settings - and re-prices itself as you change them. Hover it for a breakdown by kind of work and the assumptions behind the figure. It is usually a range: the top assumes every record goes through every step, the bottom takes off work your workspace has already done. Credits and billing explains how to read it.
Optionally switch on Credit limit, just under the estimate, and type the most this run may spend. The run pauses once it reaches that number instead of carrying on - see Cap what a run can spend below.
If the workflow includes a qualification, research, or account plan step, a Boost switch sits in the dialog’s header. Turn it on to run this launch at Fast speed: the qualification and research work in it costs double, and the estimate reads (2x boosted). The saved workflow and its agents are not changed. See Boost a single run.
Select Launch to start the run. You will see a confirmation that the workflow launched.

To set the workflow to run automatically instead of right now, use the Schedule button on the workflow’s row in the picker. That opens New Workflow Scheduler, pre-filled with your selected records, rather than launching now. See Set up a Workflow Scheduler automation.

On selected accounts or contacts

Open the accounts or contacts list.
Tick the checkbox on each record you want to include. The action bar appears once at least one record is selected.
Select Select workflow in the action bar and choose a workflow from the dropdown, the same way as above.
The same Launch workflow dialog opens, here counting the records you selected, with the same credit estimate beneath it. Optionally switch on Stop early at a target, set a Credit limit, and turn on Boost, then select Launch to run the workflow. The action is greyed out while no records are selected.

The picker scopes the run to exactly the records you chose. A contact workflow run from the accounts list, or the reverse, will not match, so launch each workflow from its own list.

Stop a run early at a target

The same card sits in every launch window that works on more than one record: Launch workflow, and the windows of the Website finder, Qualification, Research, Account plan, Contact finder, Email/Phone finder and Play agents. It is off unless the workflow you are launching was saved with a target.

Read the card while it is off. Switched off, it reads as one sentence: the title Stop early at a target, and beneath it what will happen, for example “All 40 accounts will be processed”, plus what switching on would do.
Switch it on. The card becomes Stop at [number] [unit]. Type the number, and use the dropdown to pick what counts toward it.
Pick what counts. The dropdown offers what this run actually produces, the most downstream result first:
- accounts with a website - the Website finder.
- qualified accounts - accounts that come back ICP yes.
- researched accounts and researched contacts - research.
- accounts with a plan - account plans.
- contacts found - the Contact finder, plus contacts with an email and contacts with a phone for the searches you have switched on.
- contacts with an email and contacts with a phone - the Email/Phone finder, for the channels you have switched on.
- qualified contacts - contacts that come back IBP yes.
- contacts with plays - plays.
- records matching custom conditions - always offered. It opens a small editor: choose Count records of type (Account or Contact) and add the filter conditions a record has to meet to count.
A workflow offers one of these for each agent step it contains. From the Research, Account plan and Play windows, the count follows what you ticked in the window: a record counts once any one of the selected research agents, plans or plays has a result for it (for a research agent that reports whether it found something, once it has found it). A workflow counts research once the record’s research is recent.
Check the button. The launch button repeats the target, for example Start, stop at 10 or Launch, stop at 25, so you confirm the run knowing where it ends.

The other records stay untouched and cost nothing. Records already being worked on when the target is reached still finish, so a run can end slightly above the number - the information icon beside the note says so.

The number has to be reachable. A target at or above the number of records you selected (for the Contact finder, the most contacts the run can find) could never end the run early, so the card warns “A target needs to be below N, the most this run can reach.”

Account targets can start from your own number. If your profile has your weekly accounts target under How you work (see Manage your profile), an account target opens with that number filled in, and the information icon says where it came from. Contact targets, and accounts when your profile has no such number, start empty.

A workflow’s saved target is a default, not a rule. A workflow saved with a target opens with the card already on and a Workflow default chip beside the note: “Prefilled from this workflow’s target. Changes here apply to this run only.” Changing the number, or switching the card off, affects this launch only and does not edit the saved workflow. Switching it off and on again brings back what you had typed. In the browser extension, the card only appears for a workflow that has a saved target, so you can switch it off.

Where the records came from is shown beside the count. When you used Select all on the list, a chip next to the record count in the footer names what the selection covers, for example All matching “Not qualified”, Whole list, or First 500 of the list, so you can tell a whole filtered list from rows you picked by hand.

Eva: “goal” and “target” are the same thing - the workspace called it a goal until October 2026 and now labels it a target everywhere (the launch card, the builder’s Target tab, the scheduler’s Target & limits step). Since then it is offered on the single-agent launch windows too, not only on workflows; the only agent launch without one is a phone re-check, which works through an explicit list and has nothing to stop at. A target never appears for a single record. Overshoot is expected: records already in progress when the count is reached finish, so “it stopped at 12, I asked for 10” is normal behaviour, not a bug.

Cap what a run can spend

A target says when a run has produced enough; a credit limit says when it has spent enough. The Credit limit switch sits under the Estimated N credits line in every launch window - Launch workflow, and each individual agent’s window - so you can put a ceiling on this one run without touching anyone’s personal or team limits.

Read the estimate first. It tells you what the run is likely to cost, which is the number a sensible limit is set against.
Switch on Credit limit and type an amount in credits. Leaving the box empty (it shows No limit) means no cap.
Check for the warning. If the amount is below the bottom of the estimate, the window warns “Below the estimate - the run will pause once the limit is reached”. That is allowed - it is a deliberate way to try a run on a small budget first - but expect it to stop before every record is done.
Launch. The limit travels with this run only. It does not change the workflow, the agents, or the next launch.

When the run’s spend reaches the limit, it pauses with Workflow limit reached, keeps everything it finished, and waits for you. Raise the limit or remove it from the task feed to carry on - see Resume a run that stopped for credits. You can also set, change or remove the limit while the run is still going, from its credits figure in the run report. Unlike the personal and team limits, this one is a hard ceiling. Before a paid step starts on a record, the run sets aside the most that step could cost and only goes ahead if that still fits under the limit, so a run never spends more than you allowed. It can stop a little short of the limit instead, because a step is held back whenever its full possible price would not fit, even if it might have cost less. A step that does not fit first waits briefly for the steps already running on other records, which often finish below their maximum, and only then does the run pause.

Eva: the per-run credit limit is separate from personal and team limits and from the workspace balance - it belongs to one launch, is set in the launch window (or the scheduler’s per-run cap), and can be changed on the running task. It was built earlier but stayed switched off until October 2026, so a customer who remembers a launch window with no credit limit switch is remembering correctly. A paused run labelled Workflow limit reached is never fixed by a top-up or by an admin raising a person’s limit: only raising or removing that run’s own limit continues it. Since early October 2026 it is a hard cap: each paid step, and each individual contact search, reserves its maximum possible price before it runs, and runs only if what is already spent, plus what other running steps have reserved, plus that maximum still fits. So a run never ends above its limit; ending somewhat below it is normal, and is not lost money - nothing is charged for the work that was held back. A step that does not fit waits up to about ten minutes for other running steps to settle before the run pauses, so the pause can land a few minutes after spending stops moving. Free steps never wait. Raising the limit by only a credit or two can pause the run again almost at once when the next step’s maximum is larger than the new headroom, so suggest leaving room for the work still to do. Runs from before the change checked the limit as each record started a step and could end slightly above it.

What happens next

The workflow is handed off and starts running. Results land in two places:

On the record. As each step finishes, it writes back to the account or contact: a qualification verdict, research findings and signals, an account plan, found contacts, verified email and phone, plays, or a digital twin, depending on which steps the workflow includes. While agents are running on an account, a small working indicator shows next to its name and on its Activity tab. Changes are also synced to your connected CRM. If a run pauses partway through with Out of credits, User limit reached, Team limit reached or Workflow limit reached, it kept everything finished so far - see A run stopped because a credit limit was reached.
In the task feed. Open the Activity tab on the account or contact and stay on Agent tasks (or use the workspace-wide task feed) to watch progress. Each task shows a status of In queue, In progress…, Finished, Stopped, Error, or Skipped, plus a progress bar of how many records are completed, in progress, and still in queue. You can filter the feed by Status, Action, Source, Created by, and Date added.

How long it takes depends on how many records you launched on and how many steps the workflow runs; larger batches and heavier steps take longer. Refresh is automatic. If a task stays at In progress… far longer than expected, or shows Error, see Task stuck and Agent job error. To check the detailed outputs once a task finishes, see Review agent outputs.