Skip to main content
Configure your care flow's custom actions

Perform custom actions via third-party extensions

Sanne Willekens avatar
Written by Sanne Willekens
Updated over a week ago

An action is the most low level and granular building block at design-time in a care flow. Compared to tracks and steps which purely help you organize a pathway, an action defines what needs to happen by who.

There are two types of actions:

  1. There are default or native actions in Awell like a form, message, checklist, and calculation.

  2. There are custom actions in Awell, which are tied to the 3rd party Extension enabled in your care flow design, like 'Send Chat', 'Send Email', 'Get Appointment'.

In this section we're going to focus on the latter, so you can define how to use it in your design. If you're interested in reading up about the native actions, please navigate to this collection in our Help Center.

Add a custom action to your Step

Pre-requisite: you need to have at least 1 extension enabled for your care flow. Read here how to enable your extensions.

  1. Double click on the step you'd like to add a Custom action to

  2. Click "Add action" in the side pane and select one of the available custom actions in the drop-down list.

    1. Configure the required input fields of the custom action

    2. (Optional) Determine the data points which you'd like to store as a result of that custom action in the Care flow

Below are two examples to help you navigate between the different types of custom actions and how to use them.

Configure a custom action without storing data points

Certain custom actions do not generate data points to use in an Awell care flow. Typical examples of such custom actions are the "Send email" or "Send SMS" actions, tied to communication providers like SendGrid, Twilio, MessageBird, ... where an Awell care flow performs a unidirectional action: Awell β†’ Send SMS β†’ Recipient.

Configure a custom action AND store data points

In other instances, you explicitly want to reach out to a 3rd party provider and return some data to ingest in your care flow. Typical examples of such custom actions are the "Get Patient" or "Get Appointment" actions, which return information about a patient's profile or date of the appointment which is registered in the external system.

In such instances, you'll likely want to store that information to use in your care flow design to then generate a personalized message, or activate a step at a specific timing.

Did this answer your question?