Automations: How to Route, Tag, and Follow Up—Automatically

Automations in Connection Card Pro let you apply actions (like adding someone to a group, starting a workflow, tagging, etc.) the moment someone interacts with your church—submits a Digital Guest Card, completes an Event registration, finishes a Custom Form, uses a Unique Donation Link, or when a Workflow (or Workflow Step) runs.

The target of the automation is the person who completes the form, registration, digital guest card donation or who the workflow is being run for.

You’ll see the Automations interface embedded directly inside: Digital Guest Cards, Events (registration), Custom Forms, Workflows and Workflow Steps, and Unique Donation Links.

User Interface Overview
Available Actions
Conditions (Run This Only If…)
- Common Field Types & Operators
- Context-Only Condition Fields
When Automations Fire (By Context)
Multiple Automations, Order, and Duplicates
Permissions
Practical Recipes
Tips & Gotchas
Building Reliable Automations (Best Practices)

User Interface Overview)

Select an action category
Choose a type
Configure the specifics
(Optional) Add Conditions — all conditions must be true for the automation to run

You can add multiple automations to the same item. Each one evaluates its own conditions and runs if they’re met.

Available Actions (What an Automation Can Do)

Assign individual to a campaign

Choose a Campaign (Communications > Campaigns).
Being “in” a campaign makes the person eligible for that campaign’s scheduled emails/texts (your prebuilt touchpoints).

Assign a Point of Contact

Set a Point of Contact value for the person (e.g., how this person was connected to your organization).

Assign individual to a custom list

Add to Custom, Invite, Mailing, or Prospect lists.
Use lists for quick pulls, mail merges, or targeted comms later.

Assign individual to a group

Pick any group type (Departments, Divisions, Classes, Class Streams, Crews, Small Groups, Teams).
Optionally set a Group Classification at the same time (within the selected group).
Classes note: “Class (No Stream)” adds them to the class without a specific stream.

Assign a Classification (organization-level)

Set a Classification (global to the person and your organization).

Assign Tags to the individual

Apply People Tags (Custom, Project, Fundraiser).
You can apply multiple tags at once.

Assign the individual to another person

Set a responsible person (e.g., pastor, deacon, overseer).
In a Workflow Step context you can select “Whoever this Step is Assigned to.”

Assign the individual to a Workflow (start a new Run)

Select a Workflow and (optionally) start at a specific Step; otherwise it begins at First Step (default).

Conditions (Run This Only If…)

Add conditions to restrict when the action applies. All conditions must be met (logical AND).

The UI adapts based on the context (Guest Card / Events / Forms / Donations / Workflow Step). Operators and inputs change automatically per field type.

Common Field Types & Operators

Text fields (First Name, Last Name, Email, Cell Phone, Prayer Need, Comments)
Operators: Equal To, Not Equal To, Blank/Empty, Filled In, Contains, Starts With
Numbers (Number of Family Members added in a Guest Card)
Operators: Equal, Not Equal, >, ≥, <, ≤
Dates / Age / Birthday
Operators: Equal, Not Equal, > (After), ≥, < (Before), ≤
No “contains/starts with” for date-like fields.
Picklists with defined values (Status, Household Status/Role, Marital Status, Grade, Classification, Tags, Group Membership, Event Registered/Attended, Active Pledge, Received Template, Active Recurring Gift)
Operators vary by field; typically Equal and/or Not Equal with a value selector.
Tags
Operators relabeled to: Contains/Has Any, Contains/Has All, Lacks Any, Lacks All.
Totals & metrics (All-Time Total Giving, YTD Giving, Current Pledge Completion %, Absent X Weeks, Served in last X Weeks)
Operators: Equal, Not Equal, Starts With, >, ≥, <, ≤
Inputs: enter numbers (e.g., completion as 0–100 without the % symbol; weeks as integers).

Context-Only Condition Fields

Digital Guest Card

Family Member Type (Spouse/Child/Neither)
Number of Family Members
Optional Comments
Prayer Request
Requests Contact by a Leader
General person info is also available; Allergies/Medical Concerns are hidden for guest card completions.

Events (registration)

Individual is Participant (whether or not the person in question is a participant in the event)
Number of Participants (that they registered in this registration)
Price per Participant
Total Price for Registration

Donations / Unique Donation Links

Created Recurring Gift
Donation Amount
Recurring Gift Frequency
Plus Giving-related person conditions like Active Recurring Gift, Total Giving TD/YTD, Pledge/Completion.

Workflow Step (richer person context)

Organization Connection: Active/Inactive/Archived, Belongs to Group, Current Classification, Tags
Engagement: Absent X Weeks, Served in last X Weeks
Events: Registered for Event, Attended Event
Household: Role (Primary, Manager, Spouse, Child, Other), Assigned/Not Assigned
Marital Status

Past Communication (any context)

Has Received Email Template (choose Any or a specific template; “in last X days” input is provided)
Has Received Text Template (choose Any or a specific template; “in last X days” input is provided)

Matched an Existing Person (Guest, Donation, Events, Forms)

No operator/value needed—simply checks if the submission matched an existing person.

When Automations Fire (By Context)

Digital Guest Cards / Custom Forms: on successful submission
Events: on completed registration (after payment for paid events)
Unique Donation Links: on successful one-time gift and/or when a recurring gift is created (depending on the condition you choose)
Workflows / Workflow Steps: when a Workflow runs or a Step is processed

Automations evaluate once at trigger time. They do not retroactively re-run if data changes later.

Multiple Automations, Order, and Duplicates

You can add unlimited automations.
Each automation evaluates its own conditions and runs if true.
They run in the order you added them, but generally won’t affect each other.
- Exception: If an automation changes a value (e.g., Classification) that another automation checks, set the value-changing one first.
Idempotent for membership: adding to a Group or List won’t duplicate if they’re already in it.
Messages: no deduping—if you added multiple send steps elsewhere, they will all send.

Permissions

Automations are available to users who have permission to access the parent module they’re configuring:

Guest Cards → Guest Card permissions
Events → Events permissions
Forms → Forms permissions
Donations (unique links) → Giving/Financial permissions (as applicable)
Workflows/Steps → Workflow permissions

Practical Recipes (Copy These)

New Guest asks for contact (guest cards)

Conditions: Requests Contact = yes
Actions:
Assign to Campaign: New Guest Follow-up;
Tag Prospect;
Assign to Group: Guest Follow-up Team (Classification: “Needs Call”);
Start Workflow: First-Time Guest.

Online Event—high participant count

Conditions: Number of Participants ≥ 4
Actions:
Tag Family,
add to Mailing List: Event Families,
assign Point of Contact to the Event.

New Recurring Donor (Donation Link)

Conditions: Created Recurring Gift = true
Actions:
Assign to Campaign: New Givers Onboarding;
Tag Recurring Giver;
Start Workflow: 30-Day Thank-You Path.

Care follow-up (Workflow Step)

Conditions: Absent ≥ 3 weeks AND Tags Lacks Any of “Contacted”
Actions:
Assign to Whoever this Step is Assigned to,
Tag Needs Contact,
add to Prospect List.

Tips & Gotchas

All conditions are ANDed (every condition must be true).
For numeric fields (giving totals, pledge completion, weeks), enter pure numbers; for % use 0–100.
Campaigns = your drip/timed messages; assigning someone enrolls them to receive that sequence.
Classification vs. Group Classification:
- Assign individual to a group → optional Group Classification is within that group.
- Assign a Classification to the individual → a organization-level classification.
Classes & Streams: choosing “Class (All Streams)” adds to the class (no stream), not every stream.
Past Communication conditions allow specifying in last X days.
No auto-removal: If you add someone to a group/list via automation, they won’t be auto-removed later unless another automation or process removes them.

Building Reliable Automations (Best Practices)

Start with actions that set baseline data (tags/classifications), then add actions that depend on those values.
Keep conditions simple and testable; add one at a time and test with sample data.
Use Tags generously—they’re great for segmenting future campaigns and reports.
Document your automation set in a shared note so staff know what happens after each submission/registration/gift.

Connection Card Pro Help & Documentation