Trigger events
These are the events offered in Events on the Trigger step. Triggered by in flight history shows the technical name.
| Group | Event | Technical name | Record it’s about | Linked records |
|---|---|---|---|---|
| Relationships | Contact created | ContactCreated |
Contact | Organisation, Resource |
| Relationships | Contact updated | ContactUpdated |
Contact | Organisation, Resource |
| Relationships | Organisation created | OrganisationCreated |
Organisation | Contact |
| Relationships | Touchpoint added | TouchpointAdded |
Touchpoint | Contact, Fundraising activity |
| Tasks | Task created | TaskCreated |
Task | Contact, Organisation, Payment, Case, Touchpoint |
| Tasks | Task updated | TaskUpdated |
Task | Contact, Organisation, Payment, Case, Touchpoint |
| Cases | Case created | CaseCreated |
Case | Contact, Programme |
| Cases | Case closed | CaseClosed |
Case | Contact, Programme |
| Engage | Form submission received | FormSubmissionReceived |
Form submission | Form |
| Taxes | Gift Aid claim submitted | GiftAidClaimSubmitted |
Gift Aid claim | none |
| Taxes | Gift Aid claim paid | GiftAidClaimPaid |
Gift Aid claim | none |
| Payments | Payment created | PaymentCreated |
Payment | Contact, Organisation, Fundraising activity, Fundraising page, Tribute fund, Restricted fund |
| Memberships | Membership renewal due | MembershipRenewalDue |
Membership renewal | Contact (the payer) |
An action that needs a contact, such as Email a contact, is only offered when the event has Contact as its record or a linked record.
Membership renewal due
This event is published daily for memberships due for renewal this week, this month, this quarter, or in the next 7, 14, 30, 60 or 90 days. It’s also published when someone chooses Fire worker bees on the renewals dashboard. Filter on Due within to choose which window your bee acts on, and on Raised by (scheduled or manual) to tell the two apart. Each membership is announced once for each window, so without a Due within filter the bee runs several times as a renewal approaches (for example at 90, 60, 30, 14 and 7 days), and the same member could be contacted each time.
Fields you can filter on
These are the PRIMARY fields for each record. The same fields appear in Insert data.
| Record | Fields |
|---|---|
| Contact | First name, Last name, Email address, Phone, Is a beneficiary, Is a donor, Supporter number, Country |
| Organisation | Name, Subtypes, Country |
| Touchpoint | Touchpoint type, Direction, Date, Restricted access |
| Task | Title, Status, Due date, Assigned to |
| Case | Title, Case status, Duration type, Start date, Expected end date, Programme |
| Form submission | Form, Status, Submitted at |
| Gift Aid claim | Claim type, Status, Tax year, Donations total, Donation count |
| Payment | Amount, Currency, Status, Direction, Payment method, Date paid, Ineligible for tax relief, Has a linked contact, Has a linked organisation |
| Membership renewal | Due within, Raised by, Membership type, Status, Membership number, Expiry date, Days until renewal |
Filters
Comparisons offered
| Field type | Comparisons |
|---|---|
| Text | is, is not, contains, is set, is not set |
| Option list | is, is not, is set, is not set |
| Number, amount or date | is, is greater than, is less than, is set, is not set |
| Yes / no | is |
| Present | is set, is not set |
How filters are matched today
- Only is matches. Every other comparison is saved with the bee but never matches, so a bee with one won’t fly. This includes is set and is not set on the Payment fields Has a linked contact and Has a linked organisation.
- All conditions must match in a single set, or in a swarm branch.
- Matching is exact and case-sensitive. A yes/no field matches only True or False, and a number matches only a number. Dates are compared as stored text, so an is condition on a date rarely matches.
- LINKED fields aren’t looked up. The condition is checked against a field of the same name on the triggering record, not on the linked record, so it usually won’t match.
- Some option lists are examples. The Form and Programme options are fixed sample names rather than your beehive’s forms and programmes, so conditions on them won’t match.
- Hidden fields never match. If the bee’s owner isn’t allowed to see a field the condition uses, the bee doesn’t fly for that event.
- No filter means every event. Removing a filter broadens the bee.
For a swarm, the first branch whose conditions all match runs; a branch with no conditions always matches. See Choose between actions with a swarm.
Statuses
| Where | Status | Meaning |
|---|---|---|
| Worker Bees list | Active | Runs when its event happens and its filters match |
| Worker Bees list | Inactive | Doesn’t run |
| Worker Bees list | Pending | Newly created and still being saved |
| Flight history | Succeeded | The action completed |
| Flight history | Failed | The action didn’t complete and won’t be retried; see Read a Worker Bee’s flight history |