CRM, sales & support · wired today
Drive Close with governed agents
Pipeline truth lives here, and agents are only as honest as their source. The Close connector is one of 205 executable connectors and gives agents 4 read-only tools, with the credential held in the vault and every call receipted.
What agents can run against Close
| Tool | What it does |
|---|---|
me | Get the Close user the API key belongs to (own user id, email and the organizations it can reach) |
list_leads | List Close leads (companies) with their status and primary contact details |
get_lead | Get one Close lead by ID, including its contact ids and description |
list_opportunities | List Close opportunities (deals), optionally narrowed to one lead or one status type |
Every tool above is read-only. Write surfaces ship only after live testing, and always behind approval gates.
What the Close connector needs
You provide API key from your Close account; Quox sends it as HTTP basic credentials. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.
Where to get it: Close's own API documentation ↗ covers creating and scoping the credential.
How proven is this?
This connector was blind shape-proven against the real Close API: every endpoint it declares answered measurably differently from a deliberately bogus control request, without any account or credential involved. It is Beta: proven against the live API surface, not yet run with a real credential.
Close integration FAQ
What can Quox agents do with Close?
Agents can run 4 read-only tools against Close: me, list leads, get lead, list opportunities. Every call is receipted in the evidence trail.
What does the Close integration need?
You provide API key from your Close account; Quox sends it as HTTP basic credentials. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.
Do agents see my Close credentials?
No. Credentials live encrypted in the Quox vault and are resolved server-side at call time. Agents invoke tools; they never receive the underlying secret.
How proven is the Close connector?
This connector was blind shape-proven against the real Close API: every endpoint it declares answered measurably differently from a deliberately bogus control request, without any account or credential involved. It is Beta: proven against the live API surface, not yet run with a real credential.