Add an action to a worker
Updated September 21, 2026 · 1 min read
Pick actions the worker may take — like sending a Slack message or updating Crisp — and fill in the required settings.
Open Worker actions
- Open a worker and go to its Knowledge tab.
- Under Actions, click the + button to add one.
Pick an action and configure it
- Choose an action from the list (Slack, Crisp, log a knowledge gap, or a connected MCP tool) and fill in its required settings, such as a Slack channel or message template.
- Leave Optional off if the action should run automatically every time the worker runs; turn Optional on to let the model decide whether to call it.
Override per Skill
- Open a Skill's Actions tab to enable or disable inherited actions for just that Skill, or add a skill-only action.
FAQ
What's the difference between Mandatory and optional?
Mandatory actions run automatically — once per worker execution, or once when a skill-only action's Skill loads. Optional actions become a tool the model can choose to call.
Can different Skills use different actions?
Yes. Open a Skill's Actions tab to enable or disable inherited pool actions for just that Skill, or add a skill-only action.
Do connected MCP tools show up here too?
Yes. Any connected custom MCP source's tools appear in the Actions list once that connection tests OK.
Related articles
- Add a custom worker
Create a Support chatbot for your Crisp inboxes, or a Success worker for onboarding, upsell, and churn, with the Add Worker wizard.
- What is a worker
A Worker is an always-on automation trained on your knowledge that starts as a copilot, then can go live on its own.
- Add a trigger to a worker
Add a live or scheduled trigger so a worker only runs on the events you choose.
- Add or edit Guards
Add misbehaviour rules on Guards so drafts can't skip the policy you care about.
- Edit Agent Skills for a worker
Open Knowledge → Agent skills to edit the playbook a worker reads at runtime.