​
Trigger Node

(standard to all Morf workflows)

This specifies what event will kick off the workflow, e.g. Healthie - Appointment, Feathery - Form Response, Morf - Track. Inputs differ by source, but you may optionally specify the event type and any custom conditional logic via CEL. Find Morf’s webhook URL on the Connect tab which can be used to register webhooks in third-party tools. Morf’s Track trigger allows you to build workflows triggered by structured event and profile data sent to Morf.

​
Profile Lookup Node

(standard to all Morf workflows)

Based on identifying information on the payload, we’ll attempt to match this event to an existing Morf profile. Clicking on the profile lookup node in your workflow editor will display the different execution routes based on your configuration.

​
Profile Properties Update Node

(standard to all Morf workflows)

Map values on the payload to profile IDs and properties. Establish criteria for profile merging based on phone number and email.

​
Action Nodes

From here on out, you’re the in the drivers seat! Use Morf’s library of logic, third-party actions, and Morf actions to build custom automation to fit your needs. See different types of nodes you can add to your workflow below.

  • Filter: Check for certain criteria on the event payload, Morf profile, or another action to determine if the execution should proceed. Filters accept CEL input and must evaluate to true or false, e.g. check if the patient has a provider_id
  • Wait: Create a pause in your workflow. Specify a date time relative to the time of execution, a date time on the event payload, or a date time on another action. Wait nodes accept CEL input and must evaluate to a date time, e.g. wait until 30 minutes after the appointment to resume workflow execution
  • Destination Action: Send and retrieve data to a third-party tool, e.g. Create or Update Contact, Update Patient, Send Slack Message
  • Fetch Action: Retrieve data from a third-party tool, e.g. Get Appointment, Search Contacts, Send SMS, Send Email, Send HTTP Request
  • Branch: Make actions and logic run independently of one another using branches
  • Restart Workflow: Run this event through the workflow again from the triggering node