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

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

Use this page to understand where ASC connects with external systems and delivery tools. 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 Channels & delivery {% 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 * TigerConnect * SignalWire fax setup * [Zapier](https://answeringservicecare.com/docs/api-reference/api-clients/zapier) * [HubSpot](/docs/useful-resources/integrations/hubspot.md) * [External API Dispatching](https://answeringservicecare.com/docs/api-reference/api-clients/external-api-dispatching) ### At a glance * secure delivery for on-call and escalation workflows * fax-related BYOC setup where required * no-code workflow automation options * native HubSpot CRM delivery for contacts, companies, and tickets * external dispatch handoffs to client systems ### Common scenarios * Send on-call notifications to TigerConnect or QliqSOFT groups. * Use Zapier when a team needs a faster no-code workflow path. * Send the messages you choose to HubSpot as contacts and tickets by adding a HubSpot delivery method to the on-call calendar. * Hand off events to external platforms through External API dispatching. ### 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 supports a custom branded workflow automation path between ASC and other business systems. Use this path when the team wants a custom Zapier add-on instead of a direct custom API implementation. #### CRM sync HubSpot sends callers and messages into your HubSpot CRM as contacts, companies, and tickets. Connecting HubSpot only authorizes ASC: records are created for messages that reach a HubSpot delivery method on the on-call calendar, with optional field mapping on that delivery method. Use this path when the team runs on HubSpot instead of a custom API or Zapier workflow. #### 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. ### Keep the docs split clean Use the docs in this space for: * where the feature lives in ASC * 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: Review account-level setup that supports integrations. * Omnichannel: Configure chat, SMS, and task-based workflows. * Profile, reports, and API keys: Manage API tokens and review shared technical access. * Admin Portal: Start from the main admin workflow overview. * 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://answeringservicecare.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 what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.