A webhook destination posts every article you publish to a URL you control. The receiver gets the whole article in one request: title, slug, HTML, Markdown, SEO title and description, tags, images, structured data (JSON-LD) and the brand. From there a no-code tool or your own code can put it on any site Rank Prompt does not connect to directly.
Publishing sends article.published, publishing again sends article.updated with the same post_id, and removing the article sends article.unpublished. You can publish now or schedule a date. Drafts are not sent, since a webhook has nowhere to keep one.
An https URL that answers 2xx to a POST (a Zapier, Make or n8n catch hook, or your own endpoint)
A Rank Prompt plan with publishing (Starter or higher), and the owner of the brand
Open Integrations > Publish Content. In the More platforms card, click + (Connect a platform), pick Webhook and click Continue.
Paste the Webhook URL.
Keep the Signing secret we made, or make a new one, and copy it into your endpoint. Every request carries an X-RP-Signature header made with it.
Optional: a Custom header (a name and a value) for catch hooks that check one. The value is stored encrypted and never shown again.
Optional, under Format: JSON-LD inside the HTML adds the structured data to the HTML body, and Front matter in the Markdown starts the Markdown with YAML (title, slug, date, tags, image) for static site generators.
Click Connect webhook. We send a test article first, so the URL has to answer, and a no-code tool can map the fields from it.
The card lists the webhook by its host. Check connection (the arrows) sends another test, and Connection settings (the gear) lets you change the settings or remove it. Changing the settings asks for the secret again.
When your endpoint answers 2xx with JSON holding published_url (and optionally post_id), that URL is recorded as where the article lives, so page tracking and the citation reports follow it:
{ "published_url": "https://yoursite.com/blog/the-article", "post_id": "812" }Without it, the article is marked published with no URL.
X-RP-Signature looks like t=<timestamp>,v1=<hmac>: an HMAC-SHA256 of <timestamp>.<body> with your signing secret. X-RP-Event names the event. The Developer API article shows the check in full.
Message | What to do |
|---|---|
The webhook URL must start with https://, since the article and its signature travel in it. | Use the https address of your endpoint. |
That URL does not resolve to a public address. | Use an address reachable from the internet, not a local or private one. |
Nothing answered at this URL (404). | Check the address, and that the Zap, scenario or workflow behind it is turned on. |
The webhook answered (a status) to a test article. | Your endpoint refused the test. Fix it and connect again. |
A webhook receives published articles only, so it cannot keep a draft. | Publish the article or schedule it. |
This article is over the 4 MB a webhook request can carry. | Remove the files embedded in its text and try again. |
A webhook destination is not the same as the webhooks under Developers > Webhooks, which tell your tools when reports and schedules finish. Publishing to a webhook costs no credits.