Publishing integration
Publish to Framer
Framer has no confirmed public write API for CMS content -- this sends the same signed webhook payload as Custom Webhook, to a receiver you set up that performs the actual write on Framer's side.
How it works
Framer doesn't expose a public API for writing CMS content, so this runs through a Custom Webhook pointed at a small receiver you control (a Framer site's own API route, or a lightweight middleware worker) that performs the actual write on Framer's side.
Before you start
- A receiver endpoint you control that can accept a signed POST request and write to Framer on its own (an API route, or a small middleware worker)
- That endpoint's URL, reachable from the public internet
Setup
Three steps to connect
Step 1
Get your signing secret (optional)
Same HMAC signing as Custom Webhook -- see that integration's help text.
Optional for Framer, it can run without one.
Step 2
Enter your site details
- Webhook URL *
- Extra headers (JSON, optional)
Step 3
Connect and publish
Once connected, approved posts publish straight to Framer automatically. No export, no import, no copy-pasting into a CMS. Setup runs from your own client portal, so credentials for Framer stay with you; the agency never has to hold or request them separately.
Troubleshooting
If something doesn’t connect
Test request times out
Framer's own hosting doesn't run custom server code, so the receiver has to live somewhere else (a Vercel/Cloudflare function, for example) and forward the write into Framer.
Not sure whether a request really came from Comppound
Every request is HMAC-signed. Verify the signature against the shared secret before your receiver acts on the payload.
Frequently asked questions
Framer's CMS is built for its visual editor and doesn't offer a stable public write API. The webhook approach avoids relying on an undocumented endpoint that could break without notice.
It needs one extra piece, a receiver endpoint, but once that's in place, publishing works exactly the same as any other integration.
We can help set it up on the call if you don't already have one; it's usually a short function, not a project.
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 Framer 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 Framer?
Book a call and we'll get your site's publishing integration set up together.