Integrations

Keragon Integration

Create healthcare automations with Keragon for Atlas

Overview

This guide explains how to create automations with Keragon for Atlas.

For any trigger or action you’ll have to log in to your Atlas account in Keragon and authorize the app.

Available Triggers and Actions

Triggers

Call State Changed

This unified trigger activates when a call changes state in Atlas. When configuring, you must select:

  • Campaign (choose from available Atlas campaigns)
  • Event (select one of two options):
    • call_started: Triggers when a new call begins
    • call_completed: Triggers when a call ends

Output Data for call_started event:

  • Campaign Id
  • Agent Id
  • Call Id
  • Customer Number
  • Customer Name
  • Campaign Name
  • Agent Name

Output Data for call_completed event:

  • Campaign Id
  • Agent Id
  • Call Id
  • Customer Number
  • Customer Name
  • Campaign Name
  • Agent Name
  • Campaign Type (outbound | inbound | voice-bubble)
  • Call Summary
  • Ended At
  • Started At
  • Duration Ms
  • Duration Seconds
  • Duration Minutes

Use Cases:

  • Record call details to external systems
  • Send notifications based on call states
  • Store call data in databases
  • Trigger follow-up workflows based on call outcomes

Actions

Start Call

Initiates an outbound call from an Atlas campaign.

Required Parameters:

  • Campaign (select from available Atlas campaigns)
  • Phone Number (target number to call)
  • Customer First Name
  • Customer Last Name
  • Scheduled Date (optional - if not provided, call starts immediately)

Use Cases:

  • Schedule follow-up calls based on form submissions
  • Initiate calls when specific events occur
  • Set up automated call sequences

Creating Basic Automations

Example 1: Log Completed Calls to External Database

  1. Start a new automation in Keragon
  2. Add the “Call State Changed” trigger for Atlas
  3. Select the target campaign
  4. Choose call_completed as the event
  5. Add a database connector action
  6. Map the call data fields to your database columns
  7. Save and activate the automation

Example 2: Trigger Follow-up Call After Form Submission

  1. Start with a form submission trigger
  2. Add the “Call A Number” Atlas action
  3. Map form fields to call parameters (name, phone number)
  4. Set scheduling options if needed
  5. Save and activate the automation

Example 3: Send Notification When Call Starts

  1. Add the “Call State Changed” Atlas trigger
  2. Select the relevant campaign
  3. Choose call_started as the event
  4. Add a notification action (email, messaging service, etc.)
  5. Create a message template using call data (Campaign Name, Customer Name)
  6. Save and activate the automation

Best Practices

  • Test your automations thoroughly before activating them
  • Use filters to process only relevant calls
  • Consider adding error handling paths

For more advanced workflows, consider combining multiple triggers and actions or incorporating data transformation steps between modules.