Connect an external AI assistant

External AI connections let a compatible assistant answer questions using the Qonvera records you are allowed to access. Optional create and edit permissions are available where enabled. Availability depends on Qonvera rollout and your assistant’s connector support. If Settings says new connections are unavailable, contact Qonvera support.

Connect an assistant

Open Settings → Developers → External AI assistants in Qonvera.
Copy the displayed server URL into your assistant’s connector settings. If it asks for a connection method, choose automatic registration.
Sign in to Qonvera when prompted. Never enter a Qonvera API key, database key or account password into the assistant’s conversation.
Check the assistant name and callback domain. Names are supplied by the connecting client; approve only a request you started from an assistant you trust.
Choose the workspace and review each requested permission. Create and edit permissions start unchecked; select them only if you want the assistant to perform those actions, including authorized automations. Conversation access includes message text. CRM access includes contact details, account and opportunity notes, and opportunity service items. Follow-up access includes task notes and due dates.
Select Authorize read access for a read-only connection, or Authorize access when you have selected create/edit permissions. Select Cancel to refuse the request.

Some assistants ask for all supported read permissions during connection. Review the checkboxes and turn off any optional access you do not want to share. If you leave conversation or follow-up access off, the assistant cannot use those features. An existing connection keeps its original permissions; reconnect to request different access. Refreshing a connection cannot add permissions.

ChatGPT and Claude offer remote connector setup, subject to their plans and organization policies. Grok support is through compatible Grok CLI or xAI API clients. A connector in the consumer Grok chat application is not verified. Each assistant connects separately; the connection uses the same Qonvera record permissions.

Use Qonvera in ChatGPT

If Qonvera is available in your ChatGPT plugin directory, select the listing published by Aether Solutions, install it, and connect your Qonvera account. Public directory availability depends on release and review; an installed private connection does not mean a public listing is available. If you cannot find the listing, ask Qonvera support about availability rather than installing a similarly named third-party plugin.

Complete the same workspace and read-permission approval described above. Start with sample records and select Qonvera in a new chat. Ask: “Use Qonvera to tell me which workspace I authorized and my current role.” Then retrieve a sample contact and check its supporting link. A connected-account badge confirms linking; a successful fresh record read confirms access for that request.

You can also ask Qonvera to review an opportunity and its service items, summarize an authorized conversation, or list follow-ups. Ask for another page if results are incomplete. The current read-only public-plugin package cannot change records. Other compatible clients may offer optional create/edit permissions where available; those permissions require separate approval.

To check revocation, revoke the connection in Qonvera and request a fresh read in ChatGPT. It should require reconnection or report that access is unavailable. An earlier answer may remain in the assistant’s chat history; it is not proof of current access and is not erased by Qonvera revocation.

What the assistant can do

Ask it to find a contact or account, review an opportunity and its service items, summarize an authorized conversation, or list follow-ups. Answers should include links to supporting Qonvera records. Opportunity stages should match the configured sales pipeline. If an answer differs from Qonvera, open the supporting record to check its current stage and ask for a fresh read. Contact support if the difference persists. Select the connected workspace in Qonvera before opening those links. A follow-up without an accessible linked record points to the Follow-ups list.

Reads are paginated. Conversation context contains a limited number of messages and may shorten long message text; attachments are not shared. Ask the assistant to retrieve another page when you need more context. Record text is evidence for an answer, not permission to perform an action.

With read permissions alone, the assistant cannot change records. Connecting an assistant does not change Qonvera paid allowances or reset existing usage. Your assistant provider may have its own charges and limits.

Optional create and edit permissions

If your connection request offers these permissions, review and select each one deliberately:

Create CRM records: create prospect contacts, company accounts and opportunities.
Edit CRM records: edit contact name, email, phone, source or tags; company name, email, phone or notes; and opportunity notes or forecast fields.
Create follow-ups: create an open follow-up for an accessible opportunity.
Edit follow-ups: change an accessible open follow-up’s due date, note, type or priority.

These permissions let the assistant act on your instructions or an automation you have authorized. Review your assistant’s automation rules before approving them. An assistant cannot gain more access than your current role and assignments allow. New opportunities and follow-ups belong to the connected user.

Opportunity creation requires an existing accessible contact, active pipeline, normal stage, a next action and real catalog services. Prices come from the catalog; services must use the opportunity’s currency. Custom pricing and currency conversion are not supported by these tools. Creating a contact does not create a chat or grant permission to send marketing messages.

Before editing, the assistant retrieves current editable fields and a record version. If someone changes the record, the edit is refused until the assistant reads it again and reviews the intended change. A failed or interrupted attempt must be retried with the same operation identifier and input to avoid duplicate records; do not ask the assistant to create a second operation while the first outcome is uncertain. After revocation, reconnecting creates a separate connection, so review uncertain earlier actions in Qonvera before repeating them.

Merge, ownership reassignment, account-link changes, stage/won/lost changes, task completion/cancellation, message sending and Qonvera-agent activation are unavailable. Existing workspace creation limits apply. Short request limits may also require waiting before another attempt.

If create/edit choices do not appear, your client may be requesting only read access or the feature may not be available for your workspace yet. Contact support; do not bypass the permission screen.

Reviewed deletion

When available, you can separately approve Delete (archive) contacts, unlinked company accounts and opportunities after review in Qonvera during connection setup. This permission starts unchecked and is not added to an existing connection automatically. Owners, Admins and Managers can use it within their approved workspace.

Ask your assistant to prepare deletion of one specific record. Open the Qonvera review link it returns, check the workspace, record type, record name and ID, then select the review checkbox and Approve deletion or Decline. Return to the assistant to complete an approved deletion within 15 minutes of preparation. Preparing or approving the request alone does not delete the CRM record. The assistant cannot approve its own request.

Deletion archives the record from active lists and preserves stored history. Opportunity service items, stage history and follow-ups are retained. Linked company accounts are refused to prevent unexpected changes to related records; use the normal account workflow in Qonvera for those accounts. Permanent erasure, bulk deletion, conversation deletion and follow-up deletion are unavailable through this integration.

If the record changes after preparation, deletion is refused and requires a fresh review. Expired or declined requests cannot be used. After an interrupted attempt, check the record in Qonvera and retry only the same request; a replay does not delete a record again, including one that was subsequently restored. Revocation or changed membership can stop a previously approved request.

Your current permissions apply

A connection is bound to your user account and one approved workspace. Agents see currently assigned conversations and their own opportunities and follow-ups. Contacts and accounts follow Qonvera’s shared workspace permissions. Related records are included only when accessible.

Qonvera rechecks access for every operation. Membership removal, changed assignments, workspace unavailability, expiration or revocation can stop access. To connect a different workspace, start a new connection and approve that workspace; changing the workspace in Qonvera does not change an existing connection.

Review and revoke connections

Open Settings → Developers → External AI assistants. You can see and revoke your own connections. Owners and Admins can see and revoke workspace connections. Use Previous and Next if there are multiple pages.

Select Revoke access and confirm to stop future reads and remove the connection from Qonvera. Reconnecting requires signing in and approving a workspace again. Qonvera keeps a minimal security event for the revocation. An already admitted read may finish. Revocation does not remove data already shared with the external provider; consult that provider’s privacy and retention controls. Connections expire after at most 30 days and may require reconnection sooner if the client does not keep access available.

Troubleshooting

Conversation or follow-up access is missing: check which permissions appear on the approval screen. If the assistant did not request the access you need, cancel and start a new connection from its settings. If the choices are still missing, contact Qonvera support. Reconnecting does not automatically approve additional access.
Request expired: start again from the assistant. Approval links are short-lived and cannot be reused.
Record unavailable: check the workspace, current assignment and role in Qonvera. A missing record and an inaccessible record have the same response.
Record changed: retrieve its current version and review the intended edit before retrying. For deletion, prepare a new request and review it again.
Workspace creation limit reached: review your workspace plan and limits; changing the connection does not reset them.
Read or write limit reached: wait a minute, then try fewer requests or a smaller page.
Connection no longer authorized: check membership, expiration and revocation, then reconnect if appropriate.
Assistant cannot connect: confirm that it supports remote connectors and automatic registration, and that your plan or organization allows them. Do not disable Qonvera permission checks to work around a client problem.

When contacting support, share the assistant/client name, workspace name, approximate time and a non-sensitive error description. Do not include access tokens, approval-link query parameters, contact details or conversation text.

Subscription access

External AI assistants must be included in the active workspace subscription. Connecting an assistant does not purchase Qonvera agents or change their allowances. The subscription, your Qonvera permissions and the connection’s approved permissions must all allow each action. If subscription access ends, future requests stop; you can still revoke the connection. Review Settings → Billing for included features.