Web chat integration

Connect any web chat widget to a shared inbox

The short answer

Apavin bridges any web chat widget through a signed inbound webhook and an outbound reply URL you configure. That means a widget with no public REST API, such as HippoChat, still lands in your shared inbox without waiting for an official integration.

Most chat widgets ship an SDK and no documented public API, which is normally where an integration project dies. Guessing at an undocumented endpoint produces something that breaks on the vendor's next release.

So Apavin does the honest version. It issues you a signed inbound webhook URL that your widget posts customer messages to, and it posts replies back to a URL you configure. Both directions are yours to point wherever you need.

This works with HippoChat today, and it will work with the next widget you adopt without any new code from us.

How it works

  1. 1Create the web chat channelApavin issues a signed inbound webhook URL unique to your workspace.
  2. 2Post messages inConfigure your widget or a small server side hook to POST visitor messages to that URL.
  3. 3Give Apavin a reply URLAdd the endpoint Apavin should POST agent replies to.
  4. 4Treat it like any channelWeb chat conversations route, assign and report exactly like the rest.

At a glance

InboundSigned webhook URL, unique per workspace
OutboundApavin POSTs replies to a URL you configure
Works withHippoChat and any widget you can hook server side
Why a bridgeMost widgets ship SDKs, not documented public REST APIs

Frequently asked

Why is this a bridge instead of a native integration?

Because most widgets, HippoChat included, do not publish a documented public REST API. A bridge is stable where a guessed endpoint is not, and it works with the next widget too.

Is the inbound URL secret?

It is signed and unique to your workspace. Treat it like a credential and rotate it if it leaks.

Can I use this for a custom in house widget?

Yes. Anything that can make an HTTP POST can feed the inbox.

Every conversation, one calm inbox.

Twelve channels, one thread per customer, and an AI teammate that handles the routine. Three days free.

Start the trial

Related channels and use cases