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

# Close

> Two-way CRM sync between Olympus Connect and Close: contacts, opportunities, tasks, and notes

Close connects your Close.com CRM to Olympus Connect. Changes made in either system flow to the other: a note added in Olympus lands on the Close lead, and an opportunity moved in Close moves in Olympus.

<Note>
  Close is rolling out gradually. The card stays locked in environments where the integration has not been activated yet. If the card shows as coming soon, your workspace is waiting on activation.
</Note>

## What syncs

| Record        | Direction | Notes                                                                   |
| ------------- | --------- | ----------------------------------------------------------------------- |
| Contacts      | Both ways | An Olympus contact maps to a Close lead plus contact pair               |
| Opportunities | Both ways | Includes name, value, and stage placement through your stage mapping    |
| Tasks         | Both ways | Create, reschedule, and complete. Only Close lead tasks participate     |
| Notes         | Both ways | Notes attach to the owning Close lead and to the linked Olympus contact |

Two things stay out of scope:

* **Engagement history is not synced yet.** Calls, emails, SMS, and meeting activity recorded in Close do not import into Olympus. This is planned, not missing by accident.
* **Olympus never sends anything through Close.** The sync moves records. It does not place calls, send emails, or send SMS on your behalf, and it never will through this integration.

Olympus also never changes your Close pipeline or status definitions. It imports them read-only for mapping.

## How to connect Close

<Steps>
  <Step title="Create an API key in Close">
    In Close, go to **Settings > Developer > API Keys** and create an organization API key. Copy it.
  </Step>

  <Step title="Connect from Olympus">
    In Olympus, open **Settings > Integrations** and click **Connect** on the Close card. Paste the API key. Olympus verifies the key live against Close before anything is saved. A key that fails verification is not stored.
  </Step>

  <Step title="Webhook registration happens for you">
    On a successful connect, Olympus registers its webhook subscription with Close automatically. You do not need to configure anything in Close.
  </Step>

  <Step title="Map your stages">
    Olympus imports your Close pipelines and opportunity statuses, then asks you to map each Close status to an Olympus pipeline stage. Outbound sync stays off until you save this mapping. Inbound records that arrive with an unmapped status wait as sync issues instead of being placed somewhere wrong.
  </Step>

  <Step title="Historical import runs first">
    After connecting, Olympus imports your existing Close leads, contacts, opportunities, tasks, and notes. The import is resumable: if it is interrupted, it picks up where it left off. Nothing from the historical import is pushed back out to Close.
  </Step>
</Steps>

## How the sync works

Close notifies Olympus of changes through webhooks, and Olympus applies them within a couple of minutes under normal load. Two repair mechanisms cover gaps: a scheduled sweep replays missed events from the Close Event Log (Close keeps 30 days of events), and gaps older than that fall back to a search of recently updated leads.

The sync never guesses. When something cannot be applied safely, it becomes a sync issue you can review, and the rest of the connection keeps running:

* An opportunity whose Close status has no mapping pauses instead of moving.
* A record edited in both systems at nearly the same time is flagged instead of overwritten.
* A record deleted or merged in Close is never deleted in Olympus. The link between the two records is retired and the divergence is recorded.

A change that started in Close is never echoed back to Close, and a change that started in Olympus is delivered to Close exactly once.

## Troubleshooting

* **Webhooks paused.** Close pauses a webhook subscription after about 72 hours of failed deliveries. Olympus checks subscription health on a schedule and raises a sync issue when it finds the subscription paused. Disconnecting and reconnecting registers a fresh subscription.
* **Rate limits.** Close rate-limits its API. When Olympus is throttled, it backs off and retries, so a large burst of changes can take longer to settle. Nothing is lost.
* **Sync issues panel.** The Close card in **Settings > Integrations** shows connection health, the last successful inbound and outbound sync, pending work, and open sync issues.
* **Disconnecting.** Disconnect removes the stored API key and the Close webhook subscription. Your imported records, record links, and stage mappings are kept, so reconnecting later resumes cleanly without duplicates.

<Note>
  **If your Olympus domain changes.** Close webhook subscriptions store the exact URL registered at connect time. When the app's public URL changes, each organization's Close webhook subscription must be updated to the new URL through the Close API, and subscription health verified afterward. Until that happens, Close keeps posting to the old address.
</Note>

## A note for administrators on AI access

Content synced from Close, including note text and contact fields, becomes CRM data in Olympus. Team members who connect an AI assistant through the [Olympus MCP endpoint](/modules/integrations/mcp) can read that data, and their assistants also hold write access to the CRM.

Olympus limits the blast radius: text that arrives from Close is treated as data, never as instructions to an assistant; write bodies are size-bounded; guarded changes such as moving an opportunity backward require the assistant to ask for explicit confirmation; and every write runs with the member's own role permissions. Even so, you should know that text synced from Close reaches an AI that can write to your CRM. If that does not fit your policies, do not enable API keys for your team.

## What to do next

Set up Claude access to work your CRM from Claude Code. See [Work from Claude](/modules/integrations/mcp).