API keys and webhook settings

Owners and Admins can configure integrations in Settings → Developers.

Create an API key

1. Confirm you are in the correct workspace.
2. Create a separate key for each connected tool so its access can be managed independently.
3. Select only the permissions that tool needs. Ask its administrator if you are unsure.
4. Copy the key when it is shown and store it securely. You will not be able to reveal it again.
5. Share it only with the person responsible for connecting the approved tool, using your organization’s secure sharing method.

Revoke a key when the tool no longer needs access, or immediately if the key is exposed. Revoking it stops the tool from using that key.

Map imported lead fields

Under Lead synchronization, choose an API key, enter the provider name agreed with your supplier, and choose Prospect contacts or Companies. Select Load mapping before editing.

For each external field, choose its Qonvera field and who controls changes:

• Protect teammate changes preserves a teammate’s correction, including a cleared field. This is the default.
• External controls this field allows a newer import to replace it.
• Qonvera controls this field prevents imports from setting it.

Choose Save mapping and give the displayed mapping revision to your supplier. If another administrator changed the mapping, reload it before saving again. Your supplier must send only mapped fields.

Prospect imports create or update contacts and companies. They do not create a chat or opportunity, or grant permission to send marketing messages. Customer enquiries should use your established intake connection.

A possible match needs review before the supplier links the import to an existing record. Similar names never link records automatically. Deleted, merged or archived records are not silently recreated by a later import.

Add webhook notifications

A webhook sends a notification to another tool when a selected event happens in Qonvera.

1. Ask the person managing the receiving tool for its notification address.
2. Add that address in the webhook settings.
3. Select only the event types the tool needs.
4. Store the signing secret securely and share it through your approved secure method with the person managing the connection.
5. Choose Send test, then review the delivery result.

The signing secret lets the receiving tool check that a notification came from Qonvera. You do not need to write code to manage these settings.

Deleting a webhook connection stops future notifications to that destination. Confirm it is no longer needed before removing it.

Continue with Check and maintain integrations. Technical connection instructions are available separately in the Qonvera API documentation.

Subscription access

API and webhook integrations must be included in the active subscription. Only authorized Owners and Admins can manage credentials and endpoints. Creating a key does not provide additional plan capacity: lead and other CRM limits still apply to imported records. If access ends, requests and webhook sends stop; existing keys can still be revoked and endpoints paused. Review Settings → Billing or contact your workspace Owner if a feature is not included.