Connection
Use the client-specific address supplied by Ocliq and complete OAuth sign-in for the intended account.
MCP access, permissions and actions
Connect a compatible AI assistant to exposed Ocliq CRM operations. Start with account scope and read tools, then review any proposed writes separately. Connection details are provided for your account during activation.
Separate connection, permission and authorization
Permission
Available operations are constrained by the connection’s applicable scope and account context. Confirm the exposed tool set with your administrator.
Authorization
Review the target, values and effects before a write. The reviewed catalog flags writes for approval and idempotency; client confirmation behavior must be checked in the actual deployment.
Result
A successful preview does not prove live authorization. Inspect the operation result and record any partial failure before retrying.
Data shared with the assistant
The assistant processes the CRM data returned to it. Review the assistant provider’s terms, access settings and your organization’s data policy. Do not assume the connection keeps every record inside the CRM or grants access to every record. Disconnect or restrict unused connections through the relevant client and account controls; prior conversation retention follows the provider’s terms.
Common errors to resolve
- Authentication or expired connection: reconnect using the account’s setup process.
- Missing permission or unavailable operation: ask the administrator to check the exposed scope.
- Validation error: describe the operation again and supply required fields.
- Ambiguous contact, pipeline or calendar: resolve the target before a write.
- Duplicate/retry concern: follow the operation’s idempotency requirements; do not blindly repeat writes.
Start with your real workflow
Bring your lead sources, stages and tools. We define the configuration and scope before implementation.
Plan a demo