Integration

The escape hatch for everything we do not integrate with

Any PingPlug automation can post JSON to a URL you control. That is how PingPlug connects to systems it has no built-in integration for — your own API, an internal tool, a spreadsheet endpoint, or a workflow service you already pay for.

Start free See pricing

How it connects

An automation step makes an HTTP POST to the URL you configure, carrying the relevant contact and event data as JSON. It is outbound only.

What you get

Fires from any automation

Whatever can trigger an automation can trigger a webhook — a new contact, a tag applied, a form submitted, a deal moved.

Goes straight to you

PingPlug to your endpoint, with no third party holding the data in transit.

Covers what we do not build

Rather than waiting for a connector to your particular CRM, ERP or internal tool, you can post to it today.

What this is not

— Outbound only. There is no inbound webhook API for pushing data INTO PingPlug from your systems.
— No retry queue with a dashboard. A failing endpoint is logged; it is not held and replayed for you.
— Requests are not cryptographically signed. You can set a secret header the receiving end checks, which is the practical equivalent, but there is no HMAC signature to verify.
— You build and host whatever receives it.

Setting it up

1
Stand up an endpoint that accepts a POST.
2
Add a webhook step to an automation and give it the URL.
3
Trigger the automation once and confirm the payload is what you expected before relying on it.

Questions

Can I push data into PingPlug this way?

Not with these. Webhooks here are outbound. Contacts arrive from conversations, forms, the chat widget and Meta lead ads instead.

What happens if my endpoint is down?

The failure is logged and the automation moves on. There is no replay queue, so an endpoint that is down for an hour loses what would have been sent in that hour. If that matters, make the receiving side resilient rather than relying on redelivery.

How do I verify a request came from PingPlug?

Set a secret header on the webhook step — a long random value — and have your endpoint reject anything without it. That is not the same as a cryptographic signature, which we do not send, but it does stop anyone who merely guessed the URL. Use an unguessable URL as well, and do not let the endpoint do anything destructive on the strength of a request it has not checked.

Try it on your own setup

Free plan, 100 contacts, no card required.

Start free