Use this task when you want to send a notification to the person in the queue or to anyone else.
The following configuration is available:
Name - the name of the task. This appears in the workflow canvas and wherever the task is shown (change logs and drop downs).
Description - an optional brief description for the task. This in the task when viewing the workflow editor as well as in the task properties and when an assignee is viewing their assignment.
Notification Type - options for the type of notification include Email, Text Message, and Webhook
Who is this from? - Choose the sender, either from a specific person or from your organization. Email replies will go back to the sender.
Recipients - the person or people who will receive the email being sent.
Email current person in task? - whether to email the person that is currently in this task within the workflow. If the person does not have an email, nothing will happen. This is automatically checked when you add the task.
Email others - the list of additional emails to send the message to. These addresses will appear in the To field on the email so they will be visible to others on the email. BCC gives the option to add other people whose email addresses aren't visible to others. The current person in the task should not be listed here if the option above is chosen to send to the current person in the task.
Subject - the subject line on the email
Open Editor- the body of the email. You can create email templates by clicking the 3-dots menu to the right of the Template dropdown and/or choose a template for your email. You can use the Merge Variables button in the editor to add placeholders which will be replaced with the appropriate data (e.g., person's name in the queue or your organization details). Click on the "< >" button to modify the HTML if desired. Additional email editor buttons are available for the body.
Text Message Fallback - the option to send a text message if person does not have an email address. Text messages can also have templates as described in the Open Editor section above. See additional information on sending texts here.
Text Message
Per message data rates apply. Please make sure there are enough funds to send a text message. Click here for the current rates. If remaining balance falls to $0.00, no text message will be sent out when a person reaches this task, and they will continue to the next one.
Recipients - the person or people who will receive the text being sent
Text current person in task? - whether to text the person that is currently in this task within the workflow. If the person does not have a mobile number, nothing will happen. This is automatically checked when you add the task.
Text others - the list of additional people to send the message to. The mobile numbers should be added to the To field so those people receive the notification.
Template - optional field. Choose a text template or create one, if desired.
Message - the body of the text message. Use the arrow next to the Message label to add a variable into the text, such as the person's name or the name of your organization. We recommend keeping messages kept to 160 characters or less. Character count and cost estimate per number texted is displayed under the message field.
Receive Replies? – When enabled, a notification will be emailed to the person chosen when the text recipient replies. Responses can be sent by replying directly to that email, and the system will convert that message back to text. For best results, remove all text above the “##- Please type your reply…” line in the email received, including any email signatures.
Email Fallback? - this applies only to the person currently in the task and can be included in the event a person doesn't have a mobile number. Fallback email can be edited with the same instructions used in the Email Notifications.
Once you are finished configuring the task, click on Save Now to finish adding it to the workflow.
Webhook
A webhook in One Church Software can trigger an action in a third-party application when a specific event occurs, such as creating or updating a record. For example, if a new member is added in One Church, a webhook will send a real-time message to another app, prompting it to automatically add that person to a mailing list or notify a team member. Configuration settings include:
Callback URL - the URL that receives the webhook notification, pulled from the third-party application
Protect webhook URL with basic authentication? - when enabled, a username and password will need to be supplied to allow the webhook to function.
Email errors to - provides an email notification to the person or people chosen in the event the webhook encounters an error
Once you are finished configuring the task, click on Save Now to finish adding it to the workflow.