Key Concepts
Unlock the full potential of Morf workflows by first mastering the fundamental building blocks
Webhook: The way third-party tools inform Morf of a data change.
Event: A processed webhook sent from a third-party tool that triggers workflows in Morf.
Payload: The specific data sent from one application to another. Payloads are unique by event.
Trigger: Conditions under which a workflow starts executing. This is driven by a specific event from a source application, e.g. Appointment event from Healthie.
Node: An individual step in a workflow that processes data, applies logic, or interacts with third-party tools.
Workflow execution: Instance of a workflow getting triggered and all the steps that occurred.
Source: A third-party tool that sends webhooks to Morf, e.g. Feathery, Healthie, Acuity.
Destination: A third-party tool that Morf sends data or events to, e.g Hubspot, Slack, Google.
Common Expression Language (CEL): The scripting language used in Morf workflows for defining conditions, transformations, and filters. See complete documentation here
Property: An attribute on a Morf profile, either standard (predefined by Morf) or custom (defined by your organization), e.g. first_name
, provider_id
.
Profile: A unique user in Morf with third-party identifiers and properties.
-
Lead: A type of Morf profile; a user that has entered the system, but doesn’t exist in your EHR, e.g. abandoned a sign up flow before scheduling an appointment. Leads with the same email and/or phone number may be merged based on org settings.
-
Patient: A type of Morf profile; a user that exists in your EHR. Patients with the same email and/or phone number may be merged based on org settings.