Automations

Creating Your First Automation

Building your first automation follows one simple pattern: something happens, and JourneyCARE responds automatically. The best first project is a welcome email that goes out after someone submits a form. In JourneyCARE you build automations as workflows, and this tutorial walks through one from start to finish — for the building blocks behind it, see What Are JourneyCARE Automations?.

Example Workflow

Our example automation looks like this:

  • Form Submitted

  • Add Tag

  • Send Email

This simple workflow introduces the three most common automation components: a trigger, followed by two actions.

Step 1: Choose a Trigger

Every automation begins with a trigger. For this example, choose the Form Submitted trigger.

  1. Open Automations > Workflows and add a new trigger.

  2. Choose Form Submitted.

  3. Select the specific form the workflow should listen for.

Whenever someone submits the selected form, the automation begins.

Step 2: Add a Tag

Next, add an action that applies a tag to the contact — for example, Interested in Volunteer Program.

  1. Click + in the workflow to add an action.

  2. Choose Add Tag and apply the Interested in Volunteer Program tag.

Tags help organize contacts and can be used later for Smart Lists, reporting, future automations, and email campaigns.

Step 3: Send an Email

After the tag is added, add a Send Email action with a confirmation or welcome email. The email might:

  • Thank the person for completing the form

  • Explain what happens next

  • Share useful resources

  • Introduce your organization

  • Set expectations for follow-up

The entire process happens automatically within seconds of the form submission.

Testing Your Automation

Test the automation before using it publicly. A workflow runs only after you Publish it — while it is a draft, it never triggers.

  1. Submit the form yourself.

  2. Confirm the automation starts.

  3. Verify the tag is added.

  4. Check that the email is delivered.

  5. Review the contact record to ensure everything worked correctly.

Testing every automation before using it publicly helps prevent unexpected behavior.

Growing from Here

Once you're comfortable with this simple workflow, you can expand it by adding:

  • Wait steps

  • Internal notifications

  • Task creation

  • Conditional branches

  • Text messages

  • Additional emails

  • CRM updates

Most complex automations are simply combinations of these same basic building blocks.

Best Practices

  • Build one step at a time.

  • Test after every major change.

  • Give your automation a clear name.

  • Keep your first workflow simple.

  • Add complexity only after the basics are working.

Was this helpful?
Was this helpful?