Webhook OUT: every post to your CRM and analytics
Every publication — an event into your CRM or analytics.
Telegram The problem
Crosslybot publishes posts, but the publication data stays inside the service. The team needs the content history in their own CRM or BI system: what went out, when and where — to build reports and link publications to metrics.
How Crosslybot solves it
The outgoing webhook (Webhook OUT) sends an event about every successful publication to your system: text, platform, link, metadata and a trace_id. The event is HMAC-signed — you can trust the source.
Crosslybot sends publication data outward via an outgoing webhook. As soon as a post is successfully published, the service sends a POST to your system — with the text, platform, link, metadata and trace_id.
The event is HMAC-signed, so the receiver can trust the source, and on a failure delivery is retried automatically. The content history is fully on your side: it can be stored in a CRM or BI and used to link publications to metrics.
How to set up
Stand up a receiver
On your side, build an endpoint that accepts a POST from Crosslybot.
Set up Webhook OUT
In the Crosslybot dashboard, specify the receiver URL and enable the outgoing webhook for the project.
Verify the signature
On the receiver, validate the request's HMAC signature — this guarantees the event came from Crosslybot.
Store it in the CRM
Record the events in your CRM, database or BI — you have the full publication history.
What's inside
An event for every publication
A post is published — Crosslybot sends a POST with the text, platform, link, metadata and trace_id.
HMAC signature
Every outgoing request is signed — the receiver verifies the signature and trusts the source.
The full history is yours
Content data lives in your system — build reports and link publications to metrics.
Result
The content history is fully on your side. Publications are linked to CRM and BI metrics with no manual export.
FAQ
What comes in the event?
The post text, the platform, a link to the publication, metadata and a trace_id for end-to-end tracking.
How do I make sure the request is from Crosslybot?
Every outgoing request is HMAC-signed. The receiver verifies the signature with the endpoint secret.
What if my receiver was unavailable?
Outgoing webhook delivery is retried automatically — the event won't be lost on a brief outage.
What plan is needed?
Webhook OUT is available on the Pro plan and above.
Ready to try?
Connect the bot in 2 minutes. Free plan — no cards, no signup.
