You can personalise a Worker Bee’s message or task with details from the event that triggered it, such as the supporter’s first name or the amount of their gift. Each detail is written as a token that ThirdSectorBee swaps for the real value when the bee runs.
Add a token
In a setting that supports it, choose Insert data (the braces button beside the box), or type {. Pick a field from the list, or search for one. The token is placed where your cursor was.
The list shows fields from the record the trigger event is about, under a heading such as Contact fields. If you chose several events, it shows the first event’s fields.
These settings support tokens:
| Action | Settings |
|---|---|
| Create task | Title, Description |
| Post to Slack, Post to Microsoft Teams | Message |
| Email a contact | Subject, Body |
| Text a contact | Message |
Token format
A token is {{ payload. followed by the field’s name and }}. Spaces inside the braces are optional.
| You write | When the bee runs |
|---|---|
Welcome, {{ payload.firstName }}! |
Welcome, Amira! |
Gift of {{ payload.amount }} {{ payload.currency }} |
Gift of 25 GBP |
{{payload.title}} |
The task or case title |
You can reach a nested value with dots, such as {{ payload.address.town }}, if the event carries one. The field names are listed in Trigger events and filters; Insert data inserts the matching technical name for you.
Things to know
- A missing value becomes blank. If the event doesn’t carry the field, or it’s empty, the token is replaced with nothing. Write wording that still reads well, for example “Thank you for your gift” rather than “Thank you, {{ payload.firstName }}” for an event that may have no name.
- Linked records aren’t available. A token reads the triggering record only. A Task created event, for example, doesn’t carry the linked contact’s name.
- Check the spelling. Only
{{ payload.… }}is recognised. Something like{{ contact.name }}or{{ name }}isn’t replaced, and the action is refused because of it, so the flight fails. - Several events share one set of actions. If the events you chose are about different records, a token from one may be blank on the other. Create separate bees instead.
- Limits apply to the finished text. Character limits, such as 200 for an email subject, are checked again after the tokens are filled in, so a long value can push the result over the limit and the action fails.
- Contact and Consent purpose never take tokens. Contact names the event field that holds the contact’s ID, such as
contactId, without braces.