> ## 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: Resync Account

> Starts (or polls the status of) a resynchronization of a LinkedIn or Telegram account’s messaging data in Unipile. Includes SDK V2 examples, schemas, and cost.

Starts (or polls the status of) a resynchronization of a LinkedIn or Telegram account’s messaging data in Unipile.

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

## 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_resync_account',
  {
    "account_id": "123456789"
  },
);

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

### CLI

```bash theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
deepline tools execute unipile_resync_account --input '{
  "account_id": "123456789"
}' --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": "AccountResync",
    "status": "SYNC_STARTED"
  }
}
```

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

## Input reference

This route can be used both to initiate a sync process (from scratch or within a specific time span) and to monitor its status via regular polling. Supported providers: LinkedIn and Telegram. Instagram and WhatsApp are not supported by this route.

| Name | Type | Required | Default | Details |
| - | - | - | - | - |
| `payload.chunk_size` | `number` | No | — | The number of chats to be synchronized in a single chunk. Supported for LinkedIn and Telegram. |
| `payload.partial` | `boolean` | No | — | LinkedIn only. Whether the account should be partially resynchronized (keeping already synced data) or fully resynchronized. |
| `payload.linkedin_product` | `"classic" \| "recruiter" \| "sales_navigator"` | No | — | LinkedIn only. The LinkedIn messaging feature to synchronize. Leave blank to process all connected features. Allowed: `classic`, `recruiter`, `sales_navigator`. |
| `payload.before` | `number` | No | — | The end of the time span (lowest Epoch time in ms). Supported for LinkedIn and Telegram. |
| `payload.after` | `number` | No | — | The start of the time span (highest Epoch time in ms). Supported for LinkedIn and Telegram. |
| `payload.account_id` | `string` | Yes | — | The id of the account to resynchronize. |

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

  ### Input JSON Schema

  ```json theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
  {
    "type": "object",
    "description": "This route can be used both to initiate a sync process (from scratch or within a specific time span) and to monitor its status via regular polling. Supported providers: LinkedIn and Telegram. Instagram and WhatsApp are not supported by this route.",
    "properties": {
      "chunk_size": {
        "type": "number",
        "description": "The number of chats to be synchronized in a single chunk. Supported for LinkedIn and Telegram."
      },
      "partial": {
        "type": "boolean",
        "description": "LinkedIn only. Whether the account should be partially resynchronized (keeping already synced data) or fully resynchronized."
      },
      "linkedin_product": {
        "type": "string",
        "description": "LinkedIn only. The LinkedIn messaging feature to synchronize. Leave blank to process all connected features.",
        "enum": [
          "classic",
          "recruiter",
          "sales_navigator"
        ]
      },
      "before": {
        "type": "number",
        "description": "The end of the time span (lowest Epoch time in ms). Supported for LinkedIn and Telegram."
      },
      "after": {
        "type": "number",
        "description": "The start of the time span (highest Epoch time in ms). Supported for LinkedIn and Telegram."
      },
      "account_id": {
        "type": "string",
        "description": "The id of the account to resynchronize."
      }
    },
    "required": [
      "account_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` | `"AccountResync"` | Yes | — | Allowed: `AccountResync`. |
| `result.data.status` | `"SYNC_STARTED" \| "SYNC_RUNNING" \| "SYNC_DONE" \| "SYNC_ERROR" \| "CHUNK_DONE"` | Yes | — | The status of the 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`, `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": [
              "AccountResync"
            ]
          },
          "status": {
            "type": "string",
            "description": "The status of the 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",
              "SYNC_RUNNING",
              "SYNC_DONE",
              "SYNC_ERROR",
              "CHUNK_DONE"
            ]
          }
        },
        "required": [
          "object",
          "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.