> For the complete documentation index, see [llms.txt](https://help.pickyassist.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.pickyassist.com/setting-up-guide/connecting-channels/call-blaze-v2/call-syncing-into-3rd-party-platforms.md).

# Call Syncing into 3rd Party Platforms

### Overview

CallBlaze integrates with third-party platforms through Picky Assist [Connector](https://help.pickyassist.com/setting-up-guide/setting-up-connector/introduction). This integration automatically sends CallBlaze call activity to external applications in real time.

Configure a Connector in Global settings with the required C**all Status** as its trigger event. When that status occurs, system sends the complete call-log details to the Connector in a structured JSON format. The details are available as attributes and can be mapped to the required fields in the destination application.

Use the [HTTP API](https://help.pickyassist.com/setting-up-guide/setting-up-flow-builder/steps/trigger-http-api) action in a Connector to send call data directly to a third-party platform's API.

<figure><img src="https://3382165395-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LlJChpzcxtwOYGcBd1q%2Fuploads%2FdrzIiOJhpuFU7NIxVxgY%2Fimage.png?alt=media&amp;token=d189ed8a-0047-4316-a54e-dc573a4c55a5" alt=""><figcaption></figcaption></figure>

**Example: Sync Calls to an External CRM**

Suppose a customer uses an external CRM and wants all calls made through Call Blaze to be updated in that CRM.

They can:

1. Create a Connector for the required CallBlaze user.
2. Select the required Call Status as the trigger event.
3. Add an HTTP API action to the Connector.
4. Configure the API details of the external CRM.
5. Map the Call Blaze call log attributes to the required fields in the external CRM.

Whenever the configured call event occurs, the Connector is triggered and the call details are automatically sent to the external CRM through its API.&#x20;

This allows Call Blaze call activity to be synchronized with third-party platforms in real time.

Below image is a sample call log data in Json format in Connector

<figure><img src="https://3382165395-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LlJChpzcxtwOYGcBd1q%2Fuploads%2FGBAmYIbenfsyBXU8aj9T%2FConnector%20Log.png?alt=media&amp;token=d8395681-2a8a-4ad0-9f20-35daa54c43d9" alt=""><figcaption></figcaption></figure>

#### Sample Json

```json
{
  "channel_id": 90,
  "crm_record_id": "6ab0fd9357106258220f19d8",
  "agent_sim": "SIM 1",
  "agent_number": "91730643xxxx",
  "Customer number": "91860676xxxx",
  "agent": {
    "id": 503621,
    "name": "Akshay",
    "email": "ak@picky.com",
    "phone": "9187451xxxx",
    "internal_reference_id": ""
  },
  "contact": {
    "id": 201670340,
    "name": "Aswin",
    "email": "aswin@gmail.com",
    "phone": "91860676xxxx"
  },
  "call_direction": "Outgoing Call",
  "call_status": "Answered Call",
  "call_duration(in seconds)": "30",
  "call_start_time": "21 Sep 26 03:18 PM",
  "call_end_time": "21 Sep 26 03:18 PM"
}
```


---

# 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://help.pickyassist.com/setting-up-guide/connecting-channels/call-blaze-v2/call-syncing-into-3rd-party-platforms.md?ask=<question>&goal=<user_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.