Webhook OUT: an automatic content archive
Every publication is automatically saved to your archive.
Telegram The problem
All your content lives only in the channels and in the cross-posting service. If a channel is blocked, a post is deleted, or you need to pull up old material — there's nowhere to restore the history from.
How Crosslybot solves it
Crosslybot's outgoing webhook sends an event about every publication into your storage — a database, S3 or a file archive. The full content history stays on your side forever.
Crosslybot can automatically archive all content via an outgoing webhook. After every publication the service sends an event — with the text, platform, link, metadata and trace_id.
The receiver saves the event into your storage: a database, S3 or a file archive. The full content history stays on your side and doesn’t depend on the platforms or third-party services. The event is HMAC-signed, and delivery is retried on failures.
How to set up
Stand up a receiver
Build an endpoint that accepts the event and saves it to a database, S3 or file storage.
Set up Webhook OUT
In the Crosslybot dashboard, specify the receiver URL and enable the outgoing webhook for the project.
Verify the signature
Validate the request's HMAC signature — the event definitely came from Crosslybot.
Store it in the archive
Save the text, links and metadata of every publication into your storage.
What's inside
The content history is yours
The publication archive lives in your storage and doesn't depend on the platforms or third-party services.
Full publication data
The event has the text, platform, link, date, metadata and trace_id. Enough to restore the content.
Reliable delivery
The event is HMAC-signed, and if the receiver is unavailable, delivery is retried automatically.
Result
A full archive of all published content — on your side, independent of platforms and services.
FAQ
What comes in the event?
The post text, the platform, a link to the publication, the date, metadata and a trace_id.
Where can I store the archive?
In any storage that accepts HTTP data: a database, S3-compatible storage, a file backend.
Are media files saved?
The event contains links to media and metadata. The files themselves can be downloaded in the receiver if needed.
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.
