How to run a worker
Updated September 21, 2026 · 3 min read
Use Run Worker when you want a test or a one-off run. Day to day, the worker wakes from Triggers or live events — this article is only the on-demand path.
Open the worker
- In the left nav, open Operations and select the worker you want to test or run on demand.
- On the worker page, click Run Worker in the header (play icon, next to the Enabled switch).
Choose Batch or Single event
The Run worker dialog opens with Run mode. Pick the card that matches the job.
Batch
Loads many items from an input source and runs once per item. Choose an input such as Crisp, Intercom, Slack, Spreadsheet, API / IDs, MCP tool, or Datadog RUM (the list depends on the worker and which integrations you have connected).
- Select Batch, then pick the input source and any extra fields it asks for (inbox, Slack channel, spreadsheet file, or id list).
- If the source needs a time window, set Time window (Last period presets, or Advanced for a custom From / To range). Customer Support Chat batches from Crisp conversations cannot exceed 24 hours. Preventive Outreach signal windows cannot exceed 7 days.
Single event
Runs one unit from a payload you paste. Use this to try a worker on one message or event without loading a cohort.
- Select Single event. Choose Free text and paste the message, or switch to JSON and paste an object (fields become the unit payload).
Optional customer segments
Under Customer segments you can add criteria applied to each item. Leave this empty to run every matched item. Click Add segment, give it a name, and describe who or what should match in Criterion.
Queue the run
- Click Run. The dialog shows Queuing worker run… until the job is accepted.
- Wait for Worker run queued. The toast reports how many items matched and how many were queued.
Find the results
- Stay on the worker page and open the Results tab. Charts and the outcome table update as unit runs finish — the same table used by Trigger runs. Widen the date range on Results if a just-queued batch does not show yet.
After you test
If the worker should keep running on its own, open Settings → Triggers and add a live or scheduled trigger. Do not click Run Worker for every window you want to repeat.
FAQ
When should I use Run Worker vs Triggers?
Use Run Worker for tests and one-off batches or single events. Use Triggers for always-on events and repeating schedules. Both land on the same Results tab.
Does Run Worker replace my schedule?
No. A manual run queues once. Scheduled and live Triggers keep running until you change them under Settings → Triggers.
When should I use Batch vs Single event?
Use Batch to process a cohort from an input source (conversations, tickets, spreadsheet rows, and similar). Use Single event to paste one Free text message or JSON object and run a single unit — useful when you want to try the worker on one example.
Where do I see what the worker did?
Open the Results tab on that worker. Each queued item becomes its own row as it finishes. If nothing appears, check the Results date range and that the worker is enabled.
Can I repeat the last manual run?
Yes. Open Run Worker and click Load last run. Zentesimal stores the last preset in this browser for your user, company, and that worker. It does not sync to other devices.