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.
What syncs
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.
How to connect Close
1
Create an API key in Close
In Close, go to Settings > Developer > API Keys and create an organization API key. Copy it.
2
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.
3
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.
4
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.
5
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.
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.
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.
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.