---
title: "Publish to any tool with a webhook"
description: "Send each article, whole and signed, to Zapier, Make, n8n or your own CMS, and record where it went live."
url: https://help.rankprompt.com/en/articles/111-publish-to-any-tool-with-a-webhook
collection: "Integrations"
updated: 2026-11-19
language: en
---

# Publish to any tool with a webhook

Send each article, whole and signed, to Zapier, Make, n8n or your own CMS, and record where it went live.

## What it does

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.

* * *

## What you need

-   An https URL that answers 2xx to a POST (a Zapier, Make or n8n catch hook, or your own endpoint)
    
-   Starter or a higher plan, and you must own the brand
    

* * *

## Connecting a webhook

1.  Open **Integrations > Publish content**. In the **More platforms** card, click **+** (Connect a platform), pick **Webhook** and click **Continue**.
    
2.  Paste the **Webhook URL**.
    
3.  Keep the **Signing secret** the form made, or click **Make a new secret**, and copy it into your endpoint. Every request carries an `X-RP-Signature` header made with it.
    
4.  Optional: a **Custom header** (a name and a value) for catch hooks that check one. The value is stored encrypted and never shown again.
    
5.  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.
    
6.  Click **Connect webhook**. A test article goes out 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 and a short code taken from its URL, like hooks.zapier.com · 3f9a1c, so several hooks on one host read apart, here and wherever you pick where an article goes. The code never shows the URL's path, which works as the hook's password. Each webhook counts as one of the brand's 10 publishing sites. **Check connection** (the arrows) sends another test, and **Connection settings** (the gear) lets you change the settings or remove it. When you change the settings, a secret or custom header value left empty keeps the saved one. If the new URL points to another host, enter the header value again: the saved one is never sent to a host you did not give it to.

* * *

## Recording where the article went live

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:

```json
{ "published_url": "https://www.yourbrand.com/blog/the-article", "post_id": "812" }
```

Without it, the article is marked published with no URL.

* * *

## Checking the signature

`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](https://help.rankprompt.com/en/articles/96-developer-api.md) article shows the check in full.

* * *

## Autopilot changes

When [Autopilot](https://help.rankprompt.com/en/articles/128-autopilot.md) sends its changes to your webhook, each approved change set goes to the same URL as a signed `page.updated` request: the page's `url` and a list of `changes`, each with a `target`, an `operation` and its value. Your endpoint applies them on your side and answers 2xx; we then check the live page to see they stuck.

```json
{ "url": "https://www.yourbrand.com/pricing", "changes": [{ "target": "meta_description", "operation": "set", "value": "Plans for teams of every size." }] }
```

-   **Fields** (search title, meta description, Open Graph, canonical, H1) go as `set` with the new value.
    
-   **New text** goes as `insert`, with the `anchor` it goes after and its `html`, and comes out as `remove`.
    
-   **A rewritten section** goes as `replace`, only to an endpoint that said it can. Add `"capabilities": ["replace"]` to the JSON of your 2xx answer to the test article (or to any article you receive). A `replace` carries the section's heading as `anchor`, the new `html` and `before_html`, the section as your live page shows it. If you cannot apply it, answer 409 with `{"code": "anchor_not_found"}` (no such heading), `"section_ambiguous"` (the heading is there twice) or `"section_changed"` (the section no longer reads as `before_html`), and the rewrite waits in **Tasks** with the text to paste.
    
-   **Image alt text** goes as `set` on the target `alt`, a list of `{"src", "alt"}` with each image's address as the page shows it, and **language links** go as `set` on the target `hreflang`, `{"<locale>": url, "x-default": url}` with every language link the page carries. They go only to an endpoint that lists `"alt"` and `"hreflang"` in the same `capabilities` list, for example `{"capabilities": ["replace", "alt", "hreflang"]}`. Otherwise they wait in **Tasks** with the alt text or the tags to paste.
    

A check whose answer lists no `capabilities` turns them off again. **Undo** sends the same requests with the previous values: the old field or alt text, the language links the page had before (`{}` for none), and a `replace` the other way round.

* * *

## Troubleshooting

<table style="min-width: 50px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>Message</p></th><th colspan="1" rowspan="1"><p>What to do</p></th></tr><tr><td colspan="1" rowspan="1"><p>The webhook URL must start with https://, since the article and its signature travel in it.</p></td><td colspan="1" rowspan="1"><p>Use the https address of your endpoint.</p></td></tr><tr><td colspan="1" rowspan="1"><p>That URL does not resolve to a public address.</p></td><td colspan="1" rowspan="1"><p>Use an address reachable from the internet, not a local or private one.</p></td></tr><tr><td colspan="1" rowspan="1"><p>Nothing answered at this URL (404).</p></td><td colspan="1" rowspan="1"><p>Check the address, and that the Zap, scenario or workflow behind it is turned on.</p></td></tr><tr><td colspan="1" rowspan="1"><p>The webhook answered (a status) to a test article.</p></td><td colspan="1" rowspan="1"><p>Your endpoint refused the test. Fix it and connect again.</p></td></tr><tr><td colspan="1" rowspan="1"><p>A webhook receives published articles only, so it cannot keep a draft.</p></td><td colspan="1" rowspan="1"><p>Publish the article or schedule it.</p></td></tr><tr><td colspan="1" rowspan="1"><p>This article is over the 4 MB a webhook request can carry.</p></td><td colspan="1" rowspan="1"><p>Remove the files embedded in its text and try again.</p></td></tr></tbody></table>

A webhook destination is not the same as the webhooks on the **Webhooks** tab of the API page (under Developers in Settings), which tell your tools when reports finish, whether they run once or on a schedule. Publishing to a webhook costs no credits.

* * *

## Questions?

Email [support@rankprompt.com](mailto:support@rankprompt.com) and I'll help.
