> ## Documentation Index
> Fetch the complete documentation index at: https://deepline.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Unipile: Sync Attendee History

> Starts (or polls the status of) a resynchronization of every chat with one attendee. Starting a sync changes sync state in Unipile.

Starts (or polls the status of) a resynchronization of every chat with one attendee.

> [!NOTE]
>
> Tool ID: `unipile_sync_attendee_history`

## Run this action

Use the TypeScript SDK for one call. Use `ctx.tools.execute(...)` inside a Play for durable calls, scheduled calls, or CSV processing.

```ts theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
import { Deepline } from 'deepline';

const deepline = await Deepline.connect();
const result = await deepline.tools.execute(
  'unipile_sync_attendee_history',
  {
    "account_id": "123456789",
    "attendee_id": "attendee_123"
  },
);

console.log(result.toolResponse.raw);
```

### CLI

```bash theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
deepline tools execute unipile_sync_attendee_history --input '{
  "account_id": "123456789",
  "attendee_id": "attendee_123"
}' --json
```

## Example response

The SDK returns this shape at `result.toolResponse.raw`. The example values illustrate the response.

```json theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
{
  "data": {
    "object": "AttendeeHistorySync",
    "attendee_id": "attendee_123",
    "status": "SYNC_STARTED"
  }
}
```

Use `deepline describe unipile_sync_attendee_history --json` for the latest machine-readable contract.

## Input reference

Starts or monitors the synchronization of all chats for a given attendee.

| Name | Type | Required | Default | Details |
| - | - | - | - | - |
| `payload.account_id` | `string` | Yes | — | The id of the account to use. |
| `payload.attendee_id` | `string` | Yes | — | The Unipile ID or provider ID of the attendee. |

<details>
  <summary>Show raw input schema</summary>

  ### Input JSON Schema

  ```json theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
  {
    "type": "object",
    "description": "Starts or monitors the synchronization of all chats for a given attendee.",
    "properties": {
      "account_id": {
        "type": "string",
        "description": "The id of the account to use."
      },
      "attendee_id": {
        "type": "string",
        "description": "The Unipile ID or provider ID of the attendee."
      }
    },
    "required": [
      "account_id",
      "attendee_id"
    ],
    "additionalProperties": false
  }
  ```
</details>

## Output reference

Standard tool result payload.

| Name | Type | Required | Default | Details |
| - | - | - | - | - |
| `result.data` | `object` | Yes | — | Provider response payload. |
| `result.data.object` | `"AttendeeHistorySync"` | Yes | — | Allowed: `AttendeeHistorySync`. |
| `result.data.attendee_id` | `string` | Yes | — | Minimum length: 1. |
| `result.data.status` | `"SYNC_STARTED" \| "CHAT_DELETED" \| "SYNC_RUNNING" \| "SYNC_DONE" \| "SYNC_ERROR" \| "CHUNK_DONE"` | Yes | — | The status of the attendee synchronization. You can setup a regular polling on the same route to get updates on its status. A new request after a SYNC\_DONE, CHUNK\_DONE or SYNC\_ERROR response will start a fresh sync. Allowed: `SYNC_STARTED`, `CHAT_DELETED`, `SYNC_RUNNING`, `SYNC_DONE`, `SYNC_ERROR`, `CHUNK_DONE`. |
| `result.meta` | `object` | No | — | Additional response metadata (status, paging). |

<details>
  <summary>Show raw output schema</summary>

  ### Output JSON Schema

  ```json theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
  {
    "type": "object",
    "description": "Standard tool result payload.",
    "properties": {
      "data": {
        "type": "object",
        "description": "Provider response payload.",
        "properties": {
          "object": {
            "type": "string",
            "enum": [
              "AttendeeHistorySync"
            ]
          },
          "attendee_id": {
            "type": "string",
            "minLength": 1
          },
          "status": {
            "type": "string",
            "description": "The status of the attendee synchronization. You can setup a regular polling on the same route to get updates on its status. A new request after a SYNC_DONE, CHUNK_DONE or SYNC_ERROR response will start a fresh sync.",
            "enum": [
              "SYNC_STARTED",
              "CHAT_DELETED",
              "SYNC_RUNNING",
              "SYNC_DONE",
              "SYNC_ERROR",
              "CHUNK_DONE"
            ]
          }
        },
        "required": [
          "object",
          "attendee_id",
          "status"
        ],
        "additionalProperties": false
      },
      "meta": {
        "type": "object",
        "description": "Additional response metadata (status, paging).",
        "additionalProperties": true
      }
    },
    "required": [
      "data"
    ],
    "additionalProperties": false
  }
  ```
</details>

## Deepline cost

* Pricing model: `fixed` (per call).
* Estimated Deepline credits: `0` per pricing unit.
* Provider-native pricing may still exist outside Deepline credit billing.

## Related documentation

* [Unipile provider guide](https://deepline.com/docs/providers/unipile/guide.md)
* [SDK V2 quickstart](https://deepline.com/docs/sdk-v2/quickstart.md)
* [SDK reference](https://deepline.com/docs/sdk-v2/sdk-reference.md)
* [Run tools across a CSV](https://deepline.com/docs/sdk-v2/batch-csv.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.