Integrations and webhooks
Check provider availability, connection status and outbound automation events.
Connecting a new messaging service? Start in Integrations. Its catalog shows the features and connection status of each provider, including partly supported integrations and features planned for later. Check the provider card before deciding which customer messages or data can actually reach Convor.
Search the catalog
Search by provider or category. On each card, look for its connection status and the operations it supports. Messenger can deliver conversations after Meta authorization, while a webhook sends chosen Convor events to another system without becoming a messaging inbox. These are different workflows, even when both appear in the same catalog. Check permissions before connecting either.
Send events with webhooks
Your billing system needs to know when a support conversation closes. Open Integrations → Webhooks and add an HTTPS endpoint that your server controls, then subscribe to the relevant event. Verify each request's signature on the receiving server. Do not paste a live signing secret into a support chat or public repository. Test one event end to end before relying on it.
Configure the receiver, events and site scope
A webhook needs a Webhook URL and at least one Event. Select the events your application actually uses. TopSoft4U's billing system might need the conversation-closed event, but it has no reason to receive every message, assignment and status update.
Under Sites, choose Only selected sites if the receiver belongs to one storefront. All sites, including future ones makes the webhook apply to sites you create later, so check who owns that endpoint before widening the scope. When a webhook is created, Convor generates a signing Secret. Save it securely on your receiving server. Regenerate changes the secret and requires a corresponding change in your application.
Verify delivery and handle failures
Start with one event your integration needs. Confirm its type in the supported-event list, then send a test to your HTTPS receiver and check the signature and delivery status. If the receiver was offline, open the error details before retrying. Your handler also needs to recognize repeated deliveries, since a retry must not create the same invoice or task twice.
API: Use POST Register a new webhook to register a destination and GET List webhook events to select supported event types. Inspect delivery history and retry a failed delivery when needed.
For customer messaging providers, read the channel overview. Email now supports connecting Google, Microsoft and IMAP/SMTP mailboxes. Allegro remains available for Rules and Knowledge scope, without a public account-connection workflow.
Was this page helpful?