Trigger events offered by the builder
| Area | Events |
|---|---|
| Relationships | Contact created, Contact updated, Organisation created, Touchpoint added |
| Tasks | Task created, Task updated |
| Cases | Case created, Case closed |
| Engage | Form submission received |
| Taxes | Gift Aid claim submitted, Gift Aid claim paid |
| Payments | Payment created |
Multiple selected events create multiple Worker Bees, one per event.
Filter behaviour and current limitation
The builder offers comparisons such as is, is not, contains, is greater than, is less than, is set and is not set, depending on the field. However, the current event matcher accepts only the API equality operator eq; the builder sends different operator values. Those visual conditions therefore do not match.
For API-configured filters, all conditions must match. The matcher compares fields in the triggering event payload; it does not fetch linked records to evaluate their fields. Equality is type-sensitive. See the API reference and validate a configuration before relying on it.
Actions
The action picker uses the current workspace’s action catalogue. Available actions depend on enabled providers, modules, integrations, permissions and the entities available from the trigger. Fill the inputs shown for the chosen action rather than assuming a fixed set of three action types.
Standard mode can contain multiple actions. Swarm mode contains ordered branches, each with conditions and actions; only the first matching branch runs. A branch with no conditions is a fallback and should be last.
Statuses
| Status | Meaning |
|---|---|
| Active | Eligible to run when its event and conditions match |
| Inactive | Does not run |
| Pending in the list | A newly submitted bee is awaiting confirmation in the list |
| Succeeded in flight history | The recorded execution succeeded |
| Failed in flight history | The recorded execution failed; investigate the action and destination |