Zapier
Connect BlogCrew to Slack, Notion, HubSpot, email, and thousands of other apps by posting published articles to a Zapier Catch Hook.
Overview
Zapier integrations use the same delivery path as webhooks: BlogCrew POSTs when a Publisher ships an approved article. Zapier receives that payload on a Catch Hook and continues your Zap.
Note: This is for article publishes, not form leads. Approval on the board still gates every send.
Prerequisites
- A Zapier account
- Access to Library → Integrations in BlogCrew
Set up Zapier
- In Zapier, create a Zap
- Choose Webhooks by Zapier → Catch Hook
- Copy the Custom Webhook URL Zapier provides
- In BlogCrew, open Library → Integrations
- Under Zapier, click Add
- Set a Display name
- Paste the Catch Hook URL
- Changes save automatically — Test so Zapier can capture a sample, then Done
- Finish the Zap steps (Slack, Notion, etc.) and turn the Zap on
Config fields
| Field | Required | Description |
|---|---|---|
| Display name | Yes | Label in Library and Publisher settings |
| Catch Hook URL | Yes | From Zapier Catch Hook (for example https://hooks.zapier.com/hooks/catch/…) |
Use it from a Publisher
- Assign this Zapier connection on a Publisher agent
- Approve an article and move it to ready-to-publish
- When the Publisher runs, BlogCrew POSTs to your Catch Hook and the Zap continues
Payload
Zapier receives the same JSON BlogCrew sends to webhooks:
- Live publish:
event: "marketing.content.publish" - Library Test:
event: "marketing.content.publish.test"
Map Zap steps from the Catch Hook sample after you run Test in BlogCrew. The article Markdown is in blog.bodyMd; board metadata is under item.
Troubleshooting
- Zapier does not see a sample — Run Test in BlogCrew while the Catch Hook step is waiting for a request
- Zap never fires on real publishes — Confirm the Zap is published/on, the Catch Hook URL matches Library, and the Publisher uses this connection
- Wrong app data — Map fields from the Catch Hook sample in later Zap steps after a successful Test