Cituna publishes straight to WordPress, Shopify, Webflow, Wix, Ghost, Sanity, Contentful and GitHub. For any other place your posts live, Zapier is the no-code route: Cituna sends each finished article to a Zap, and the Zap creates the post with whichever app you pick. It runs on the same delivery as the webhook destination, without the code, and daily articles feed it the same way they feed every other destination.
What this assumes
1. Start a Zap with a Catch Hook
In Zapier, create a Zap. For the trigger choose Webhooks by Zapier with the event Catch Hook, and copy the webhook URL it shows. It starts with https://hooks.zapier.com/hooks/catch/.
2. Connect it in Cituna
Choose the brand in the top bar, open Integrations and click Connect on the Zapier card. Paste the URL under Catch Hook URL and click Connect Zapier. Cituna sends one sample article with the event article.sample and saves nothing unless Zapier accepts it.
The Zapier card and the Webhook card share one connection per brand, so connecting Zapier replaces a webhook the brand already had.
3. Filter out samples
Back in the Zap, click Test trigger and pick the request from Cituna: every field of a real article is there, including the title, slug, html, markdown, description and metaTitle. Then add a Filter by Zapier step that continues only when Event exactly matches article.created, so samples stop there instead of creating posts.
4. Add your action and turn on daily articles
Add the action that creates the post in your app, map the title, the HTML body, the slug and the description, and turn the Zap on. article.publish is true when the brand publishes straight away and false when it wants a draft, so map it to the post status if your app has one.
Then open Articles. Under Where should the articles go?, choose Webhook, since Zapier receives articles through the brand's webhook, pick an answer under Who approves them?, and turn on Write articles every day.
Troubleshooting
The Zapier card refuses my URL.
It takes only a Catch Hook address, which starts with https://hooks.zapier.com/hooks/catch/. Copy it from the trigger step of your Zap. For any other endpoint, use the Webhook card.
An article shows as delivered but no post appeared.
Open the Zap history in Zapier. A Zap that is off, a filter that does not match article.created, or an action that failed all accept the delivery first, so Cituna cannot see them.
Why does the picture not arrive?
The webhook carries the hero picture as inline bytes, which a Zap cannot use, so Cituna makes no picture for a brand that publishes through Zapier.
Will Cituna send the same article twice?
Not on its own. A Zap usually creates a new post each time it runs, so Cituna does not resend a delivered article to Zapier when it refreshes it. Clicking Update on Webhook in Articles sends it again with the event article.updated, which the Filter step keeps out.
Drafted with AI assistance from our own research and Search Console data, and reviewed by Rahul A before publishing. Rules and prices change; check the linked official source before you act.
