Trigger criteria
A trigger defines which event activates a Worker Bee. Each trigger specifies an event type — for example, a contact being created, a payment being recorded, or a form being submitted.
Payload filters
Triggers can optionally include one or more payload filters to narrow which events fire the rule. Each filter matches on a specific field within the event.
| Field | Description |
|---|---|
| Field | The name of the field within the event payload to match on (e.g. source) |
| Operator | The comparison to apply. Currently supported: equals |
| Value | The value the field must equal for the trigger to fire |
Multiple filters are combined with AND logic — all filters must match for the Worker Bee to run.
Action types
Each Worker Bee performs one action when its trigger fires.
| Action type | What it does |
|---|---|
| Webhook | Sends an HTTP request to a specified URL. Supports POST and PUT methods. Custom headers can be included. |
| Emit event | Fires an internal event within ThirdSectorBee, which can trigger other Worker Bees or processes. |
| Notification | Sends an email notification to a specified team member. |
Worker Bee statuses
| Status | Meaning |
|---|---|
| Active | The Worker Bee is running and fires when its trigger conditions are met |
| Inactive | The Worker Bee is paused and will not fire |