Integrations / Close
Close
Close CRM platform for managing leads, contacts, sales opportunities, tasks, and activity notes.
What Telara does
Capability matrix
Before you connect
Prerequisites
Vendor setup
Get the credential
Permissions Telara requests
- all.full_accessOAuth 2.0
- offline_accessOAuth 2.0
In Telara
Connect in Telara
OAuth 2.0 authorization-code connection. offline_access is required for refresh tokens; Close rotates the refresh token on every refresh, so the credential store must replace the previous value.
In Telara, open Settings → Integrations, choose this connector, and click Connect. Telara sends you to the vendor to approve access, then returns you here. You do not create an OAuth app or paste a client secret.
Close API key over HTTP Basic Auth. Use the API key as the username and leave the password blank (or any placeholder value — it is ignored). Confirmed against the spec's components.securitySchemes.ApiKeyAuth entry, which declares type http and scheme basic with the description "Use your API key as the username and leave the password empty" — not a bearer/header token scheme, despite the "api_key" name. An alternate oauth2 (authorization-code, scopes all.full_access/offline_access) security scheme also exists on every operation but is out of scope here; this connector only implements the API-key/Basic path.
In Telara, open Settings → Integrations, choose this connector, and enter the username and password (or key) Telara asks for.
- API key
- Password
Knowledge
What gets indexed
| Resource | Coverage |
|---|---|
| Lead | Partial — not every record the vendor holds is synced |
| Opportunity | Partial — not every record the vendor holds is synced |
| Contact | Partial — not every record the vendor holds is synced |
Sync
Freshness & sync
| Resource | Lag | Deletions |
|---|---|---|
| Lead | Up to 1 day | Removed records disappear on the next full sync |
| Opportunity | Up to 1 day | Removed records disappear on the next full sync |
| Contact | Up to 1 day | Removed records disappear on the next full sync |
Data handling
Permissions & data handling
The scopes above are the permissions this connector requests. They come from the catalog, not from a hand-written page.
Excluded from semantic search: Lead, Opportunity, Contact.
After connect
Verify it worked
After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.
Honesty