1. Understand Keragon’s Core Concepts

Workflow

A workflow is a series of automated steps between two or more apps that complete a specific task.

Every workflow:

• Starts with a trigger

• Includes one or more actions

When your workflow is published, it runs automatically each time the trigger event occurs.

For example, you might describe your automation in the chat like:

“When a patient submits a Jotform intake form, create a new patient in DrChrono.”

Keragon then builds the workflow with the correct trigger and actions for you.

Examples of workflows

• Log patient data from forms into an EHR (Electronic Health Records)

• Notify doctors of new patient appointments via email

• Track patient data in a CRM after a form submission

• Automatically notify patients of upcoming appointments

Trigger

A trigger is what starts a workflow.

You can think of it as the starting signal. A trigger usually happens when something changes in another app.

For example:

• A new form submission

• A patient record is updated

• An appointment is scheduled

When that event happens, Keragon automatically runs the workflow.

Examples of triggers

• A patient filled out an intake form

• A new lab result is posted

• A patient scheduled an appointment

Action

An action is what happens automatically after a trigger.

If the trigger is the starting signal, the action is the work that gets done.

A workflow can have one action or many actions.

For example:

• Create a new patient record in an EHR system

• Send an email reminder to a patient

• Notify doctors about new lab results via email

Each action runs in order after the trigger occurs.

Workflow Run

A workflow run is a single execution of a workflow.

Every time the trigger event happens, the workflow runs once.

It doesn’t matter whether your workflow has:

• 1 step

• 10 steps

• 100 steps

Each full execution counts as one run.