Publishing integration
Publish to Custom webhook
Sends each post as a signed JSON POST to any URL you control -- the mechanism behind the Lovable, Bolt.new, Replit, Rocket.new, Base44, and v0 setups below, and the fallback for any platform without a dedicated adapter.
How it works
Sends each post as a signed JSON POST to any URL you control, the same mechanism behind the Framer, Lovable, Bolt.new, Replit, and other code-first setups. You verify the signature on your end to confirm it's really us.
Before you start
- A receiver endpoint reachable from the public internet
- A way to verify an HMAC signature on incoming requests (a couple of lines of code in most frameworks)
Setup
Three steps to connect
Step 1
Get your signing secret (optional)
If set, every request includes an X-Webhook-Signature header (HMAC-SHA256 of the raw JSON body, hex-encoded) so your receiver can verify it actually came from here.
Optional for Custom webhook, it can run without one.
Step 2
Enter your site details
- Webhook URL *
- Extra headers (JSON, optional)Merged into every request. Use this for a receiver that expects its own auth header instead of (or in addition to) the signature below.
Step 3
Connect and publish
Once connected, approved posts publish straight to Custom webhook automatically. No export, no import, no copy-pasting into a CMS. Setup runs from your own client portal, so credentials for Custom webhook stay with you; the agency never has to hold or request them separately.
Troubleshooting
If something doesn’t connect
Test request never arrives
Confirm the receiver is publicly reachable, not just on localhost, and isn't blocked by a firewall or auth wall in front of it.
Receiver rejects the request as unauthorized
Check the signature is computed over the raw request body, not a re-serialized version of it; re-encoding JSON before verifying changes the bytes being signed.
Frequently asked questions
Anything without a dedicated integration above: a custom app, an internal tool, or a platform we haven't built a direct connection for yet.
Every request is signed with HMAC, so your receiver can check the signature before trusting the payload.
Yes, extra headers can be set during setup and are sent with every request alongside the signature.
Credentials are encrypted at rest and only ever used server-side to publish. Nobody, including us, can view them again once saved.
Nothing changes on Custom webhook itself. Everything already published stays exactly as it is. New posts just stop syncing until it's reconnected.
Still have questions? Talk to our team.
Ready to connect Custom webhook?
Book a call and we'll get your site's publishing integration set up together.