What Are JourneyCARE Automations?
Automations allow JourneyCARE to perform routine tasks automatically, saving staff time while creating a more consistent experience for members. Instead of manually sending emails, updating records, assigning tasks, or tracking follow-up activities, you can build an automation that performs those actions for you. Every automation is built from a series of connected steps, and in JourneyCARE you build automations as workflows — the four core building blocks are triggers, actions, waits, and branches.
Triggers
A trigger is what starts an automation — the event that tells JourneyCARE it's time to begin. Every automation begins with a trigger.
A form is submitted
A contact is created
A tag is added
A payment is received
A membership is renewed
An appointment is scheduled
For the full list of available triggers, see Workflow triggers.
Actions
An action is something JourneyCARE does after the trigger occurs. Most automations include several actions working together.
Send an email
Add a tag
Update a field
Create a task
Send a text message
Add someone to a campaign
Notify a staff member
For the full list of available actions, see Workflow actions.
Waits
A wait tells JourneyCARE to pause before continuing. Wait steps make it possible to create follow-up sequences that unfold over time instead of everything happening immediately.
Wait 10 minutes
Wait one day
Wait until a specific date
Wait until a condition is met
Branches
A branch allows an automation to make decisions. Instead of every contact following the same path, JourneyCARE can check information and decide what should happen next. For example:
If Membership Type = Student, send the Student Welcome Email
Otherwise, send the Professional Welcome Email
Branches make automations more personalized while reducing the need for multiple workflows.
Putting It All Together
A typical automation might look like this:
Form Submitted
Add Tag
Send Welcome Email
Wait 7 Days
Send Reminder
Each step builds on the one before it to create a complete member experience. To start building, see Workflows Overview.
Best Practices
Start with simple automations.
Give automations descriptive names.
Test before turning them on.
Use branches only when needed.
Keep each automation focused on one purpose whenever possible.