What a workflow can do
A workflow starts when something happens: a person is added, a guest moves to a new stage, someone submits a form, a person moves along their member journey or sits at one stage for a number of days, or someone stops (or starts) showing up, being in a group or serving. Conditions narrow it down by membership type, tag or custom field.
Then it acts. It can add a tag, put a task with a due date on a board for a named person or for that person’s shepherd, send an email from one of your templates or, if you use texting, send a text during the church’s daytime hours.
Safe to switch on
A new or edited workflow stays paused until you preview it on a real person and switch it on, so a typo can’t email half the church. Workflows react only to what happens from then on, and imported people don’t count as “person added”, so bringing over your directory won’t create four hundred welcome tasks.
Every time a workflow runs, it checks again that whoever built it still has the permissions it needs and that the person still wants to hear from you.
Tasks land on a board
Workflow tasks go onto the task board under Calendar & tasks, next to everything your team adds by hand. You set up the columns, and anyone can see and finish the tasks assigned to them, from the web or the app.
Reports that answer your question
Custom reports cover people, giving, attendance and guests. Pick the columns, filters and date range, show individual rows or grouped totals, and save it. A saved report is private to the person who made it and checks the reader’s permissions every time it opens, so a people report filtered by giving needs giving access too. Downloading a CSV needs export permission.
You can schedule a report to arrive by email. The email holds a link, not the data, so no names or totals sit in anyone’s inbox.
By Moriah LLC, makers of ChurchFoundry · Reviewed
