Connecting Zapier to Goji

Zapier connects thousands of applications to each other, and connecting it to Goji turns every new article into a trigger. Anything Zapier can do — add a row to a spreadsheet, notify a Slack channel, create a task, push to a platform Goji does not support directly — can now happen automatically whenever you publish.

What connecting Zapier gives you

• Any app Zapier supports. If Zapier integrates with it, your articles can reach it, without waiting for a dedicated channel here.
• The full article data. Each event carries the title, summary, link, picture and tags, so a Zap can use whichever fields it needs.
• Your own logic. Filters, delays, formatting and multi-step Zaps all work as usual — Goji simply provides the trigger.
• No approval process. Nothing to register and nothing to review; a Catch Hook is created in seconds.

Before you start

You need a Zapier account. Webhooks are a premium Zapier feature on their pricing, so check your plan covers them before setting this up — that requirement comes from Zapier rather than from Goji, and the connection cannot work around it.

How to create the Catch Hook

1. In Zapier, create a new Zap.
2. For the trigger, choose Webhooks by Zapier, then the Catch Hook event.
3. Zapier gives you a custom webhook URL. Copy it.
4. Leave the Zap open — you will come back to test it once the first article arrives.

That URL is effectively a private address for your Zap. Anyone who has it can send data into it, so do not publish it or paste it into a shared document.

How to connect it in Goji

1. Open Channels from the sidebar and choose Zapier.
2. Paste the webhook URL.
3. Give the connection a name you will recognise later — useful once you have several Zaps.
4. Save.

Then publish an article, or wait for the next one, and use Zapier's Test trigger step to pull in the sample. Zapier needs one real event before it can show you the fields to map, which is why the test step matters.

Building the rest of the Zap

Once Zapier has a sample, every field is available to later steps by name. A few things worth knowing: the link is the canonical article URL on your own site, the picture is a full URL rather than an uploaded file, and tags arrive as a list. If a downstream app needs a single string, Zapier's Formatter step will join them.

If something goes wrong

• Zapier never receives anything. The Zap is turned off, or the URL was copied incompletely. Zapier's Task History shows whether anything arrived at all.
• The test step finds no sample. No article has published since you connected. Publish one, then test again.
• Fields are missing in later steps. The sample Zapier captured came from an article that had no picture or no tags. Capture a fuller one and re-map.
• It stopped after a while. Check whether your Zapier plan's task limit was reached — Zapier pauses Zaps when it is.

Common questions

How is this different from the Custom Webhook channel? Zapier is a Catch Hook with Zapier's own tooling behind it. The custom webhook channel sends to any URL you control and is signed for verification.

Can I connect several Zaps? Yes — one connection per Catch Hook URL.

Does it retry a failure? Delivery failures are retried; what your Zap then does is Zapier's business.

Can I use Make or n8n instead? Yes — use the Custom Webhook channel and paste their incoming URL.