Check and maintain integrations

Test a connection

1. Open Settings → Developers in the intended workspace.
2. Check that the webhook destination and selected event types match the connected tool.
3. Choose Send test.
4. Review the delivery attempt in Qonvera.
5. Ask the receiving tool’s administrator to confirm that the test arrived.

A successful delivery confirms receipt by the tool; check that the tool also performed the action you expected. Use test records when checking a connection that creates or updates customer data.

Check lead synchronization

In Settings → Developers → Lead synchronization, select Refresh status to see each connection’s status, last successful write and import, and its created, updated, skipped, review-required and failed import counts for the last 30 days. These are Qonvera import results; ask your supplier whether its complete synchronization run finished.

A skipped import can mean the source record is older, unchanged, or contains protected teammate edits. Review-required imports need your supplier to check the matching Qonvera records before linking them. Failed imports show a reference code that you can share with the supplier or support, together with the workspace and approximate time. Do not share customer content or secrets.

For an unchanged request whose result is uncertain, ask the supplier to retry the same request safely. Changing the request or its retry reference can repeat an action. Older requests marked for support review must be reconciled before retrying.

A request-limit error means the supplier should wait before retrying. A plan-limit error means the workspace’s allowance has been reached; review your plan or wait for the next allowance period. Saving mappings does not reset usage.

A delivery failed

Read the delivery status and error shown in Qonvera. Check the destination with the person responsible for the receiving tool. After the problem is corrected, choose Resend when that action is available.

Check the tool before resending if the outcome is unclear, so you do not repeat an action it already performed. Resend keeps the original event reference and attempt history. The receiving tool must recognize duplicate events. Pausing or removing a destination prevents new dispatches; a request already admitted may still reach it. For persistent failures, share the delivery reference, time, and visible error with support—never the API key, signing secret, or customer message content.

Replace or remove access

• Revoke an exposed API key immediately.
• For a planned key replacement, coordinate with the tool’s administrator and Qonvera support first. Imported lead identities remain assigned to their original connection; support must arrange their transfer before the new key resumes those imports. Never use a new key to bypass a request whose outcome is unknown.
• Remove webhook destinations that your organization no longer uses.
• Review integration access when a supplier, teammate, or business process changes.

Revoking a key or deleting a webhook connection requires confirmation. If copying a newly shown secret fails, select and copy it manually before leaving the page; it is only shown once.

If integration access or delivery is unavailable, contact Qonvera support with the visible message. For instructions on building or changing the connection itself, share the separate Qonvera API documentation.