RankPine docs
Integrations

Zapier, Make & n8n

Fan each published article out to thousands of apps by pasting a catch-hook URL from Zapier, Make, or n8n.

Zapier, Make, and n8n all work the same way: they give you a catch-hook URL, you paste it into RankPine, and every published article is sent to it as JSON. From there, the automation can do almost anything — post to another CMS, add a CRM record, notify a channel, or update a spreadsheet.

Under the hood these use the same delivery as the webhook integration, so the JSON payload is identical. The only difference is a branded setup flow.

Zapier

Start a Zap with a Catch Hook

Create a Zap and choose the Webhooks by Zapier → Catch Hook trigger. Zapier generates a custom webhook URL — copy it.

Connect in RankPine

Go to Integrations, click Connect on Zapier, paste the URL, and connect. RankPine sends a verification ping so Zapier can capture the payload.

Build the rest of your Zap

Add whatever actions you like. The article fields (title, slug, markdown, html, metaDescription, language, images, …) are available to map.

If your site publishes in more than one language, each version fires this trigger separately — so route on article.language, and use article.translationGroupId to tell which versions are the same article.

Make

Add a Custom webhook module

In a Make scenario, add a Webhooks → Custom webhook module and click Add to generate its address. Copy it.

Connect in RankPine

Click Connect on Make, paste the URL, and connect.

n8n

Add a Webhook node

In an n8n workflow, add a Webhook node (method POST) and copy its Production URL.

Connect in RankPine

Click Connect on n8n, paste the URL, and connect. (For a self-hosted n8n, the URL must be reachable on the public internet.)

Tip: capture the real field structure

Zapier and Make learn their field mapping from the first payload they receive. If a field looks missing during setup, publish one real article (or re-run the connection test) and re-read the incoming data.

On this page