All Collections
Latest Version, sheepCRM Alpine
sheepCRM Settings
Communications: Lifecycle Email Triggers Explained
Communications: Lifecycle Email Triggers Explained
Tom Byrom avatar
Written by Tom Byrom
Updated over a week ago

Below are all of the most common triggers you might want to use when sending out automated communication from the SheepCRM. If you want to use any of these you simply need to create an email template and use the trigger action as the name of the email.

Membership

New member emails

The time period after represents the time after they became a member.

  • new_membership

  • new_membership_1d

  • new_membership_180d

  • new_membership_1wk

  • new_membership_2wk

  • new_membership_3wk

  • new_membership_4wk

Membership Renewal emails

- Manual Renewal (membership plans not set to auto-renew)
Labelled expiring because they will expire without action, the time period represents the time before expiring.

  • expiring_1wk

  • expiring_2wk

  • expiring_3wk

  • expiring_4wk

  • expiring_soon (time period designated automatically by Sheep; typically the day before for an annual membership)

- Automatic Renewal (auto-renewing membership plans)

The time period represents the time before renewal.

  • renewing_1wk

  • renewing_2wk

  • renewing_3wk

  • renewing_4wk

  • renewing_soon (time period designated automatically by Sheep; typically the day before for an annual membership)

- Renewal Confirmation

  • renewal_confirmation (triggered when the user renews)

  • renewed_membership (triggered when the renewed membership starts)

  • renewed_membership_1wk (triggered 1 week after the renewed membership starts)

Expired membership emails

  • lapsed_180d

  • lapsed_1d

  • lapsed_1wk

  • lapsed_2wk

  • lapsed_3wk

  • lapsed_4wk

  • lapsed_90d

Cancelled membership emails

  • cancelled_membership

Linked Members

  • linked_member_added_no_useraccount (or inactive user account)

  • linked_member_added

  • linked_member_removed

Payments

  • membership_payment_received

  • ticket_payment_received

  • donation_payment_received

  • payment_failed (just GC)

  • no_payment_membership_1d

  • no_payment_membership_1wk

  • no_payment_membership_2wk

  • no_payment_membership_3wk

  • no_payment_membership_4wk

Events

ticket_confirmation is sent for each ticket ordered, if you order 4 tickets at the same time you will receive 4 ticket confirmation emails. order_payment_received sends a single email per order, it's useful to send information about the total cost and payment, like a receipt. It does not contain any ticket information.

Please note: Comms will go to the person who placed the order not the attendees.

  • ticket_confirmation

  • order_payment_received

  • ticketed_event_minus_1d

  • ticketed_event_minus_2d

  • ticketed_event_minus_1wk

  • ticketed_event_minus_2wk

  • ticketed_event_minus_90d

GoCardless

Only available if you're using GoCardless

  • mandate_active: the mandate has been successfully set up by the customer’s bank

  • mandate_cancelled: the mandate has been cancelled

  • mandate_expired: the mandate has expired due to dormancy

  • mandate_failed: the mandate could not be created

  • mandate_pending_customer_approval: the mandate has not yet been signed by the second customer

  • mandate_pending_submission: the mandate has not yet been submitted to the customer’s bank

  • mandate_submitted: the mandate has been submitted to the customer’s bank but has not been processed yet

  • payment_failed

Invoices

Invoices without a payment triggers

  • no_payment_invoice_*

Available for 1wk, 2wk, 90d and 180d.

Note this is a check for invoices with no payment. A deposit or part payment will cause this trigger not to fire.

Fundraising

  • donation_payment_received
    ​

Deprecated/Legacy

  • donation

  • pledge

**Timing

Events old than 36 hours will not trigger an event. This allows you to enter older data without fear of triggering actions. e.g. backfilling payments without sending receipts.

Events dates use the date of the thing that are referring to e.g. for payments it is the payment date, tickets use the creation date of the record (usually representing the purchase date)

Did this answer your question?