Zapier integration

How Zapier publishing works

Spron sends each ready article to every active Zapier connection, then your Zap passes the article to the app you choose. You do not need a Spron app in the Zapier directory.

The Zap decides what happens after receipt. For example, you can map the article title and formatted content to fields in the destination app.

A Spron result of Sent to Zapier confirms that Zapier received the article. It does not confirm that later actions in your Zap finished.

• New ready articles go to each active Zap.
• Press Republish in Spron when you want to send a changed article again.
• Use the Spron article ID in your Zap to find and update the same post.

Before you connect Zapier

You need a paid Zapier plan, a Zap with a Webhooks by Zapier Catch Hook, and owner or admin access in Spron. Zapier may charge for actions that run when your Zap receives an article.

Treat the Catch Hook address as a credential. Spron accepts an HTTPS address on hooks.zapier.com with a valid /hooks/catch/... path and rejects addresses with credentials, a custom port, query parameters, or a fragment.

• A paid Zapier plan
• A Zap with Webhooks by Zapier as the app
• Catch Hook as the trigger event
• Workspace owner or admin access in Spron

Connect Zapier to Spron

1. Create your Zap

   In Zapier, create a new Zap and set its trigger to Webhooks by Zapier. You can open the Zapier dashboard to create it.

   Choose Catch Hook, leave the child key field empty, and copy the webhook address Zapier shows. Zapier also provides an official Catch Hook setup guide.

   • App: Webhooks by Zapier
   • Trigger event: Catch Hook
   • Pick off a child key: leave empty

2. Connect Zapier

   In Spron, open the Zapier integration and use the Connect Zapier form. Enter a Connection name and paste the copied URL into Zapier Catch Hook address.

   A connection name can contain up to 80 characters. After Spron accepts the connection, new ready articles are sent to that active Zap.

   • Connection name: use a name that identifies this Zap
   • Zapier Catch Hook address: paste the HTTPS address from Zapier
   • Choose Connect Zapier

3. Try it and turn on your Zap

   On the connection, press Send sample article. Confirm the prompt, then return to Zapier and press Test trigger.

   Map the article title and content to your app. Filter out requests where event_type = test, then turn on your Zap.

   If the Zap is already on when you send the sample, its actions may run and use Zapier tasks.

   • Send a sample article from Spron.
   • Test the trigger in Zapier.
   • Map article.title and article.content_html.
   • Filter sample events before turning on the Zap.

What Spron sends to Zapier

Spron sends the article title, formatted article, images, and search description to Zapier. Use article.title for the title and article.content_html for the formatted content.

Each request also includes event_type, delivery_id, and the Spron article ID at article.id. Sample requests use event_type = test, so your Zap can filter them out before running later actions.

A delivery can arrive more than once. Use delivery_id to skip a delivery your Zap already handled, and use article.id to update the same destination post when the article changes.

Article image download links expire after one hour. Spron signs each request, but Catch Hook does not verify that signature for you.

Check your first post

Open Delivery history in Spron, then check Zap history and the destination app. The table identifies the article, connection, result, and sent date.

A successful receipt appears as Sent to Zapier. Other result labels include Waiting, Sending, and Needs attention.

Check that the destination app received the title, formatted content, and any mapped fields. Results after Zapier receives the article depend on the actions configured in your Zap.

• Check the Spron result for the article.
• Open Zap history to confirm that later actions ran.
• Inspect the resulting post or record in your destination app.

Fix common Zapier connection issues