Skip to content
Convor
Convor Docs
Integrations

Zapier Integration

Connect Convor to thousands of apps using Zapier REST hooks. When events happen in Convor (new conversations, messages, assignments), Zapier can automatically t

Connect Convor to thousands of apps using Zapier REST hooks. When events happen in Convor (new conversations, messages, assignments), Zapier can automatically trigger actions in your CRM, email, project management, or any other connected service.

How It Works

Convor uses Zapier's REST Hooks pattern (subscription-based webhooks). You register a subscription from your Zapier dashboard, and Convor sends HTTP POST requests to Zapier's callback URL whenever a matching event occurs. Each payload is HMAC-signed so Zapier can verify authenticity.

Available Triggers

The following events are available as Zapier triggers:

EventDescription
conversation.createdA new conversation is started by a visitor
conversation.resolvedA conversation is marked as resolved
message.createdA new message is sent in a conversation
conversation.assignedA conversation is assigned to an operator
csat.submittedA visitor submits a CSAT satisfaction rating

Setup Guide

To connect Convor to Zapier, follow these steps:

  • Log in to your Convor dashboard and navigate to Integrations → Zapier
  • Click the subscribe button to generate a Zapier target URL (or enter one from your Zapier account)
  • Select which events you want to trigger Zapier actions for
  • In Zapier, create a new Zap and choose 'Webhooks by Zapier' as the trigger app
  • Select 'Catch Hook' as the event type
  • Copy the webhook URL from Zapier and paste it into the Convor subscription form
  • Test the connection by clicking 'Test' in Convor to send a sample event
  • Back in Zapier, click 'Test trigger' to receive the sample data and continue building your Zap

Event Payload Format

Each event is delivered as a JSON POST with the following structure:

{
  "event": "conversation.created",
  "timestamp": "2025-01-15T10:30:00.000Z",
  "data": {
    "conversationId": "uuid-...",
    "visitorId": "uuid-...",
    "status": "open",
    "channel": "widget"
  }
}

Webhook Security

All webhook payloads are signed with HMAC-SHA256. The signature is included in the X-Convor-Signature header in the format sha256=<hex-digest>. The event type is in the X-Convor-Event header. Use these headers in Zapier to verify payload authenticity.

{
  "X-Convor-Signature": "sha256=a1b2c3d4...",
  "X-Convor-Event": "conversation.created",
  "Content-Type": "application/json"
}

Tip

Subscription target URLs must use HTTPS and cannot point to localhost or private IP addresses. You can create up to 10 subscriptions per organization.

Troubleshooting

  • Events not reaching Zapier: Verify the subscription is active in Convor and the target URL matches Zapier's webhook URL exactly
  • Signature verification errors: Ensure you are comparing the raw request body when computing the HMAC hash, not a parsed version
  • Duplicate events: Check that you do not have multiple subscriptions for the same event type pointing to the same Zapier hook
  • Rate limiting: Convor does not rate-limit Zapier subscriptions, but Zapier may throttle incoming webhooks on their end
  • Test endpoint not working: Use the 'Test' button in Convor's Zapier integration settings to send a sample event and verify delivery

Was this page helpful?

On this page