Attribute Rules allow you to automate emails and notifications based on when an attribute is added to a contact or when specific events occur.
They can be used to create automated workflows such as:
- Donor journeys and thank-you emails.
- Membership renewal reminders.
- Volunteer notifications.
- Birthday greetings.
- Internal notifications to administrators.
- Follow-up emails after donations or registrations.
Each Attribute Rule is attached to a specific attribute. When that attribute is added to a contact, the configured workflow is triggered according to the selected rule.
Before You Begin
Before creating an Attribute Rule, ensure you have:
- Created the attribute you want to use.
- Created the document (email template) that will be sent as part of the workflow.
- Configured the appropriate Workflow Email (From email address).
Creating an Attribute Rule
- Navigate to Admin > Attributes.
- Locate the attribute you want to configure.
- Click Go To Advanced Attribute Form.
Select Add Attribute Rule.
Selecting an Attribute Rule Type
When you click Add Attribute Rule, you will first be prompted to select the type of workflow you want to create.
The available options are:
Contact Attribute Email
Creates an email workflow based on a contact attribute.
Use this option when you want to send emails triggered by an attribute being added to a contact or by events related to that contact, such as birthdays, membership renewals, or follow-up communications.
Examples:
- Welcome email after joining.
- Membership renewal reminders.
- Birthday greetings.
- Donor journey emails.
Payment Attribute Email
Creates an email workflow based on a payment attribute.
Use this option when the workflow should be triggered by payment activity with the assigned attribute, such as a successful donation or membership payment. Payment attributes can be assigned automatically when a payment is made through a Vega widget.
Examples:
- Thank you email after a donation.
- VIP donor acknowledgement.
- Donation reminder several months after a successful payment.
Contact Attribute SMS
Creates an SMS workflow based on a contact attribute.
This option works in the same way as Contact Attribute Email, but sends an SMS message instead of an email.
Note: SMS workflows require a configured Twilio integration before they can be used. For setup instructions, see the Twilio Integration article.
Payment Attribute SMS
Creates an SMS workflow based on a payment attribute.
This option works in the same way as Payment Attribute Email, but sends an SMS message instead of an email.
Note: SMS workflows require a configured Twilio integration before they can be used. For setup instructions, see the Twilio Integration article.
Choose the rule type that matches the event you want to automate before configuring the workflow settings.
This will open the Add Attribute Rule window, where you can configure the workflow settings.
Attribute Rule Settings
Workflow Document
Select the document (email template) that will be sent when the workflow is triggered.
Workflow Email
Select the email address that the document will be sent from.
Workflow Rule
Choose the event that will trigger the workflow.
Some workflow rules require a Rule Value, such as the number of minutes, hours, days or months before or after an event.
Available Workflow Rules
| Workflow Rule | Trigger | Rule Value | Example |
|---|---|---|---|
| Birthday | Sends the selected document on the contact's birthday. | Not required | Automatically send birthday greetings. |
| Send Minutes After | Sends a document a specified number of minutes after the attribute is added. | Minutes | Send information shortly after a donation or enquiry. |
| Send Hours After | Sends a document a specified number of hours after the attribute is added. | Hours | Send a follow-up survey one hour after registration. |
| Send Days After | Sends a document a specified number of days after the attribute is added. | Days | Send a follow-up email three days after signup. |
| Send After Payment Received | Sends a document after a successful payment is received. | Minutes | Automatically acknowledge VIP donations. |
| Send Reminder Months After Successful Payment | Sends a reminder a specified number of months after a successful payment. | Months | Invite donors to make another donation after 3, 6 or 12 months. |
| Send Days Before Renewal Due | Sends a reminder before an attribute reaches its end date. | Days Before | Membership renewal reminders. |
| Send Days After Renewal Due | Sends a reminder after an attribute has expired. | Days After | Follow up members who have not yet renewed. |
| Send to Membership Admin | Notifies contacts with the Membership Admin attribute when the attribute is added. | Not required | Notify administrators of new memberships. |
| Send to Membership Admin Days After Unrenewed | Notifies Membership Admin contacts after a membership has expired without renewal. | Days After | Prompt staff to follow up overdue memberships. |
| Send to Volunteer Admin | Notifies Volunteer Admin contacts when a volunteer-related attribute is added. | Not required | Alert volunteer coordinators of new registrations. |
| Send to Financial Admin | Notifies Financial Admin contacts when the attribute is added. | Not required | Notify finance staff of relevant activity. |
| Send to Financial Admin when Payment Received | Notifies Financial Admin contacts after a successful payment. | Minutes | Alert finance staff when donations are received. |
| Send After Distribution Received | Sends a document after a successful payment is received. | Minutes | Used when an attribute is assigned as part of a payment, such as a donation or membership with multiple distributions. |
Additional Workflow Filters
These optional settings allow you to control exactly who receives the workflow.
Exclude Contacts with These Attributes
Prevents contacts with selected attributes from receiving the workflow.
Example: Exclude existing Regular Givers from receiving an email encouraging them to become regular donors.
Include Contacts with These Attributes
Only sends the workflow to contacts who also have the selected attributes.
Example: Only send emails to contacts whose communication preference is Email.
Exclude Contacts Who Have Received These Documents
Prevents duplicate or unnecessary communications by excluding contacts who have already received selected documents.
This is particularly useful when multiple workflows may reach the same contact.
Include Contacts Who Have Received These Documents
Only sends the workflow if the contact has previously received one or more specified documents.
This is useful when creating multi-step communication journeys.
Important Notes
- Workflow documents are only sent to contacts who are Active and OK to Contact.
- A single attribute can have multiple Attribute Rules, allowing you to build more complex communication journeys.
- Test your workflows before using them in production to ensure the correct documents are sent to the intended recipients.
“Some content in this article may have been developed with the assistance of AI tools and reviewed by staff.”
Comments
0 comments
Please sign in to leave a comment.