> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt

# Linking Close as a source

Canonical URL: https://posthog.com/docs/data-pipelines/sources/close

> **Cloud region:** This page uses US Cloud hosts. For an EU Cloud project, use `https://eu.posthog.com` instead of `https://app.posthog.com` (app host for links).

## On this page

- [Available tables](#available-tables)
- [Configuration](#configuration)
- [Supported tables](#supported-tables)

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_9608fcca70)

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_dark_a92b0e022d)

Let AI connect your sources for you

Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.

`npx @posthog/wizard warehouse`

![PostHog Wizard hedgehog](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)

![](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)Let AI connect your sources for you

The Close connector syncs your sales CRM data – leads, contacts, opportunities, activities, tasks, users, statuses, pipelines, and email templates – into PostHog.

To link Close:

1.  Go to the [sources tab](https://app.posthog.com/data-management/sources) of the data pipeline section in PostHog.

2.  Click **\+ New source** and then click **Link** next to Close.

3.  Next, you need an API key from Close. In your Close dashboard, go to **Settings** → **Developer** → **API Keys**. Create a new key – we recommend using a read-only key for this integration. Copy the key value.

4.  Back in PostHog, paste the API key in the `API key` field and click **Next**.

5.  On the next page, set up the schemas you want to sync and modify the method and frequency as needed. Once done, click **Import**.

Once the syncs are complete, you can start using Close data in PostHog.

## Available tables

| Table | Description | Sync method |
| --- | --- | --- |
| `leads` | Sales leads in your Close account | Full refresh |
| `contacts` | Contacts associated with leads | Full refresh |
| `opportunities` | Sales opportunities (deals) | Incremental |
| `activities` | Activities like calls, emails, and meetings | Incremental |
| `tasks` | Tasks assigned to users | Incremental |
| `users` | Users in your Close organization | Full refresh |
| `lead_statuses` | Available lead status options | Full refresh |
| `opportunity_statuses` | Available opportunity status options | Full refresh |
| `pipelines` | Sales pipelines | Full refresh |
| `email_templates` | Email templates | Full refresh |

**Incremental** tables sync only new or updated records on each run. **Full refresh** tables reload all data on each sync.

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| `API key` | password | Yes |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `Leads` | A lead — a company or person being sold to, the central CRM record in Close. | Incremental, Full refresh | date\_created, date\_updated | — |
| `Contacts` | A contact — a person associated with a lead, with their emails and phone numbers. | Incremental, Full refresh | date\_created, date\_updated | — |
| `Opportunities` | An opportunity — a potential sale tied to a lead, with value and pipeline status. | Incremental, Full refresh | date\_created, date\_updated | — |
| `Activities` | An activity logged against a lead — a call, email, note, meeting, or status change. | Incremental, Full refresh | date\_created | — |
| `Tasks` | A task — a to-do item assigned to a user, usually tied to a lead. | Incremental, Full refresh | date\_created, date\_updated | — |
| `Users` | A user (member) of the Close organization. | Full refresh | — | — |
| `LeadStatuses` | A configured status that a lead can be in within the organization. | Full refresh | — | — |
| `OpportunityStatuses` | A configured status that an opportunity can be in within a pipeline. | Full refresh | — | — |
| `Pipelines` | A sales pipeline — an ordered set of opportunity statuses in the organization. | Full refresh | — | — |
| `EmailTemplates` | A reusable email template used when sending emails from Close. | Full refresh | — | — |
| `Events` | An event log entry — one change to a Close object, with the fields that changed and their previous values. Close keeps about 30 days of history. | Incremental, Full refresh | date\_updated | — |
| `Outcomes` | A call or meeting outcome — the standardized result a rep picks when logging one. | Full refresh | — | — |
| `Organizations` | The Close organization — the environment a team works in, with its memberships. | Full refresh | — | — |
| `LeadCustomFields` | A lead custom field definition. Resolves the opaque custom.cf\_\* keys carried on the Leads rows. | Full refresh | — | — |
| `ContactCustomFields` | A contact custom field definition. Resolves the opaque custom.cf\_\* keys carried on the Contacts rows. | Full refresh | — | — |
| `OpportunityCustomFields` | A opportunity custom field definition. Resolves the opaque custom.cf\_\* keys carried on the Opportunities rows. | Full refresh | — | — |
| `ActivityCustomFields` | A activity custom field definition. Resolves the opaque custom.cf\_\* keys carried on the Activities rows. | Full refresh | — | — |
| `SharedCustomFields` | A custom field definition usable on more than one object type. Resolves the custom.cf\_\* keys on the objects it is associated with. | Full refresh | — | — |