Skip to main content
← Back to Webhooks

​
How it works

Zapier’s Webhooks by Zapier trigger listens for incoming HTTP POSTs. You give TryRoki the Zapier-generated URL, and every time an article is created or updated TryRoki sends the full payload there. Zapier parses the JSON automatically, so you can map fields like title or content to any action step without writing code.

​
Step-by-step setup

1

Create a new Zap

Log in to zapier.com and click + Create Zap in the sidebar.
2

Add a Webhooks by Zapier trigger

In the trigger search box type Webhooks by Zapier and select it. Choose the event Catch Hook and click Continue.Zapier displays a unique webhook URL — copy it. It looks like:
3

Add the URL to TryRoki

In the TryRoki dashboard go to Integrations → Webhooks and click Add webhook. Paste the Zapier URL into the Endpoint URL field. Tick On create and/or On update depending on which events you want, then click Add Webhook.
4

Send a test event

Back in Zapier, click Test trigger. Zapier waits for an incoming request. In TryRoki, publish or update any article to fire the webhook. Within a few seconds Zapier shows the captured data:
If you see these 12 fields the trigger is wired correctly.
5

Set up an action step

Click + Add step → Action and choose your destination app. Common choices:
  • Google Sheets — create or update a row, mapping title, target_keyword, image, etc. to spreadsheet columns.
  • Slack — post a message like “New article: ” to a channel.
  • Notion — add a new database item, mapping content to a text property.
  • Webhooks by Zapier → POST — forward the data to another URL, e.g. a CMS ingestion endpoint.
6

Map the TryRoki payload fields

In any action step, click into a field and then pick from the trigger data on the right panel. Every field from the TryRoki payload is available:
7

Turn on the Zap

Once your action is configured and tested, toggle the Zap to On. From now on every matching TryRoki event triggers the Zap automatically.

​
Tips

  • To filter on event type, add a Filter step between the trigger and action. Zapier captures all events from TryRoki (both create and update) at the same URL — use a filter if you only want to act on new articles.
  • The content field is Markdown and content_html is the rendered HTML. Map whichever your destination expects natively; use Zapier’s Formatter step if you need to convert between them.
  • Zapier’s free plan supports 100 tasks/month. Each article event consumes one task per Zap step it passes through.