Communication · wired today
What can agents actually do with Crisp?
Messages and calls are where work actually gets decided. The Crisp 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.
The Crisp tool list, exactly as agents see it
list_conversations— List conversations for one Crisp website (first page), newest activity firstget_conversation— Get one Crisp conversation by session ID, with its state, visitor metadata and last messageget_people_stats— Get the number of people stored in one Crisp website's CRMlist_people_profiles— List people profiles in one Crisp website's CRM (first page), optionally filtered by a quick search text
Every tool above is read-only. Write surfaces ship only after live testing, and always behind approval gates.
What the Crisp connector needs
You provide identifier, key from your Crisp 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: Crisp's own API documentation ↗ covers creating and scoping the credential.
How proven is this?
This connector was blind shape-proven against the real Crisp 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.
Crisp integration FAQ
What can Quox agents do with Crisp?
Agents can run 4 read-only tools against Crisp: list conversations, get conversation, get people stats, list people profiles. Every call is receipted in the evidence trail.
What does the Crisp integration need?
You provide identifier, key from your Crisp 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 Crisp 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 Crisp connector?
This connector was blind shape-proven against the real Crisp 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.