> For the complete documentation index, see [llms.txt](https://www.kauneonga.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.kauneonga.com/docs/useful-resources/integrations.md). # Integrations
Illustration showing Liberty connecting with external business applications and communication platforms.

Liberty supports external delivery, communication, and account workflow integrations.

Use this page to understand how Liberty connects with external systems that support delivery, automation, and operational workflows. Use this section for product-facing setup and workflow guidance. Use the shared API reference for endpoints, authentication details, payloads, and response formats. Account setup API reference Omnichannel {% hint style="info" %} Integration availability depends on account configuration, enabled features, and the target system. {% endhint %} ### Start here {% stepper %} {% step %} ### Identify the workflow Decide whether the integration supports secure delivery, billing, telephony, or a custom system handoff. {% endstep %} {% step %} ### Confirm the account setup Make sure the account has the required feature enablement, delivery method, and target details. {% endstep %} {% step %} ### Configure and test Add the integration settings, then validate delivery with a real workflow before rollout. {% endstep %} {% endstepper %} ### In this section * [QliqSOFT](/docs/useful-resources/integrations/qliqsoft.md) * [TigerConnect](/docs/useful-resources/integrations/tigerconnect.md) * [Zapier](/docs/useful-resources/integrations/zapier.md) * [External API dispatching](/docs/useful-resources/integrations/external-api-dispatching.md) * [Script API](/docs/useful-resources/integrations/script-api.md) ### At a glance * secure delivery for on-call and escalation workflows * no-code workflow automation options * external dispatch handoffs to client systems ### Common integration categories Most broader app connections use Zapier or a custom API workflow. Common categories include: * CRM and case systems for client context, updates, and follow-up work * calendars and scheduling tools for bookings, reminders, and coordination * collaboration, billing, and line-of-business tools for downstream actions ### Common scenarios * Send on-call notifications to TigerConnect or QliqSOFT groups. * Use Zapier when a team needs a faster no-code workflow path. * Hand off events to external platforms through External API dispatching. * Connect Liberty activity to CRM, calendar, chat, or billing workflows when teams need downstream updates. ### Choose the right integration path #### Clinical and secure messaging TigerConnect and QliqSOFT can receive on-call notifications and message delivery events. Use this path for healthcare delivery, secure communications, and escalation workflows. #### Workflow automation Zapier connects Liberty workflows to a wide range of downstream business apps. This path fits CRM, calendar, chat, billing, and practice management workflows without building a direct integration first. Common examples include Salesforce, HubSpot, Zoho, Google Calendar, Microsoft Bookings, Calendly, Slack, Microsoft Teams, Zendesk, Stripe, Clio, MyCase, and PracticePanther. Use this path when the team wants faster no-code setup and the workflow does not require a custom API implementation. #### Custom external handoff External API dispatching supports account-specific notification and system handoff workflows from Oncall delivery paths. Use this path when the workflow depends on a specific external endpoint. #### Script-connected integration Script API integration supports real-time lookups and workflow decisions from inside guided agent scripts. Use this path when Liberty needs to interact with another system during intake instead of only after a message or dispatch event. ### Keep the docs split clean Use the docs in this space for: * where the feature lives in Liberty * when to use it * rollout guidance * validation guidance Use the shared API reference for: * endpoint details * authentication methods * payload structure * response handling ### Related pages * [Accounts and resources](/docs/portals/admin-portal/clients-and-accounts.md) — Review account-level setup that supports integrations. * [Omnichannel](/docs/portals/admin-portal/omnichannel.md) — Configure chat, SMS, and task-based workflows. * [Profile, reports, and API keys](/docs/portals/user-portal/profile-reports-and-api-keys.md) — Manage API tokens and review shared technical access. * [Admin Portal](/docs/portals/admin-portal.md) — Start from the main admin workflow overview. * [API reference](https://www.kauneonga.com/docs/api-reference/) — Review technical implementation details. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://www.kauneonga.com/docs/useful-resources/integrations.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.