Skip to Content
📚 Documentation is in active development — pages marked TODO will fill out over the next few weeks.
Third-party connectorsInbound webhooks

Inbound webhooks

The platform exposes a generic inbound webhook surface that third parties can POST to. Each webhook is keyed by a per-agency secret + a connector key.

URL shape

POST https://[your-platform]/api/integrations/webhooks/[connector_key]/[account_id] Headers: X-Webhook-Signature: <hmac-sha256 of body, using the secret>

What you can do with an inbound event

  • Create a contact — extract phone / email from the payload, find-or-create ContactProfile
  • Tag — apply tag based on payload (source = "indiamart")
  • Start a flow — drop the new contact into a welcome flow
  • Push to inbox — surface the event as a message in the inbox
  • Custom field write — store the lead’s vehicle interest / property type / etc.

Each connector has its own logic for extracting fields from the incoming payload (e.g. IndiaMART’s lead JSON has different field names than a Pabbly webhook).

Supported connectors

  • IndiaMART — lead JSON via their push API
  • Pabbly Connect / Make / Zapier — generic webhook (use any payload shape)
  • Webhook generic — for one-off integrations
Last updated on