Integration with Keragon

Keragon is a HIPAA-compliant workflow automation platform designed for healthcare and other data-sensitive industries. It allows you to integrate applications and streamline processes through a visual, no-code workflow builder. Keragon supports custom integrations and offers a range of healthcare-oriented tools and connectors. Using Keragon, you can build workflows that exchange data between Caspio and other systems that your organization relies on (such as EHR platforms, scheduling tools, or patient-facing applications).

Typical use cases include automating data flows into or out of Caspio, keeping information synchronized across systems, or triggering follow-up tasks based on events in external services.

There are two types of functionality in Keragon to interact with Caspio:

• Caspio Triggers – Start workflows automatically when records are created or updated in Caspio tables.
• Caspio Actions – Perform data operations or retrieve lists of tables, fields or records.

Note:

• Caspio is not affiliated with Keragon, and Keragon’s fees are managed separately.
• Configuring and executing Keragon workflows that use Caspio triggers or actions consumes the integrations calls resource in your Caspio account.

Authentication

To use Keragon’s workflow builder to construct automations involving Caspio data, configure an authentication with Keragon using credentials from a Caspio Web services profile.

Prerequisites:

• A Caspio account with the Integrations feature.
• A Keragon account where you can create and manage workflows.

Steps:

1. In Caspio, create a Web services profile. Verify that the Enable access to all objects and Profile can create objects checkboxes are selected.
2. Save the profile and open it from the list. You will need the Integration URL, Client ID, and Client Secret for configuring the Keragon authentication.
3. In Keragon, from the left panel, click Authentications.
4. Click the Create new button and from the list of services, select Caspio.
5. On the Create new authentication screen, in the Hostname field, paste the Integration URL from your Web services profile in Caspio. Paste the Client ID and Client secret.
6. Save the connection by clicking Connect.

Triggers

When you configure a Trigger for Caspio, Keragon automatically creates a webhook in your Caspio account to listen for the selected event type. When the event occurs, Caspio sends an outgoing webhook to Keragon, starting the workflow instantly. Webhooks created by Keragon display the name of the Web services profile used by the Keragon authentication.

Supported trigger events:

• table.recordInsert – triggers a workflow when a new record is created.
• table.recordUpdate – triggers a workflow when an existing record is modified.

Triggers are useful for keeping data synchronized across systems or performing follow-up actions automatically. For example, when a new record is added to a Caspio table, you can use Keragon to create a record in another system.

Note: Avoid manually editing or deleting Keragon-managed webhooks in Caspio to ensure your triggers continue functioning as expected.

Actions

Caspio Actions in Keragon let you retrieve tables, fields, and records, as well as perform data operations in your Caspio account:

• Get tables – retrieves all tables
• Get table fields – retrieves all table fields
• Get table records – gets a list of table records
• Create table record – inserts a new record
• Update table records – edits all records that match specific criteria
• Create or update table record – inserts a new record or updates the first record that matches specific criteria
• Delete table records – deletes all records that match specific criteria

Ending integration with Keragon

If you decide to stop using Keragon with Caspio, it is important to follow the correct order of steps to avoid leaving inactive webhooks or credential errors:

1. Delete your workflows in Keragon first. This ensures that Keragon no longer attempts to connect to Caspio using the credentials you provided.
2. After deleting workflows, remove the associated Web services profile in Caspio.

Following this order prevents orphaned webhook connections and ensures your Caspio environment remains clean after ending integration with Keragon.

Note: If you already removed the Web services profile before deleting the workflows, log in to your Caspio account and, in Outgoing Webhooks, manually delete relevant webhooks that use the Keragon outgoing URLs.

If you accidentally deleted an outgoing webhook that is required by an active Keragon workflow, you can deactivate that workflow in Keragon and then activate it again. This ensures that all the required webhooks are recreated.