Auto-Publish ACS Content to Any Platform via Zapier

Zapier connects ACS to thousands of apps. Using an ACS outbound webhook as the Zapier trigger, you can automatically forward published content to virtually any destination — Notion, Medium, Airtable, Slack, and beyond.

The Core Pattern

The same two-step pattern works for every destination:

1. Trigger: ACS outbound webhook → Zapier Catch Hook
2. Action: Zapier sends content to your chosen app

Set up the trigger once and reuse it. For each new destination, clone the Zap and swap out the action step.

Setting Up the Universal ACS Trigger

Step 1: Create the outbound webhook in ACS Go to Settings → Integrations → Outbound Webhooks → Add Destination. Label it for your target app, leave the URL blank, and save.

Step 2: Create a Zapier Catch Hook In Zapier, create a new Zap. Set the trigger to Webhooks by Zapier → Catch Hook and copy the URL Zapier provides.

Step 3: Connect and load sample data Paste the Zapier URL into your ACS destination. Click Send Test in ACS, then Test trigger in Zapier. All ACS content fields will load as mappable sample data.

---

Action Examples by Destination

Notion — Content Archive or Database

App: Notion | Action: Create Database Item

Recommended field mapping:

• Name → title
• Content → body (Notion text fields are plain text)
• Platform → platform
• Published At → published_at
• Slug → slug

Useful for maintaining a running archive of all published content, or syncing a content tracker database.

---

Medium — Cross-Publishing

App: Medium | Action: Create Story (Draft)

Recommended field mapping:

• Title → title
• Content → body_html (Medium accepts HTML)
• Tags → hashtags (add a Zapier Formatter step to convert the array to a comma-separated string)
• Publication Status → set as a static value "draft"

---

Airtable — Editorial Calendar or Content Tracker

App: Airtable | Action: Create Record

Recommended field mapping:

• Title → title
• Body → body (plain text; Airtable text fields do not render HTML)
• Platform → platform
• Published Date → published_at
• Slug → slug
• Meta Description → meta_description

---

Slack — Team Notification

App: Slack | Action: Send Channel Message

Example message template:

*New content published:* {{title}}
*Platform:* {{platform}}
*Type:* {{content_type}}
*Published:* {{published_at}}

Useful for notifying your team or triggering editorial review processes without sending the full body content.

---

Google Docs — Content Archive

App: Google Docs | Action: Create Document from Template

Map title to the document name and body_html or body to the content field. Keeps a Google Drive archive of every published piece.

---

Which Field to Use for Each Destination

Destination Type	Recommended Field
Email-based platforms	body_html + subject_line
Rich text / HTML editors	body_html
Plain text apps (Notion, Airtable)	body
Metadata only (Slack, dashboards)	title, slug, published_at

Handling the Hashtags Array

The hashtags field is a JSON array. If your destination expects a plain string, add a Zapier Formatter → Utilities → Convert Array to String step between the trigger and the action to flatten it into a comma-separated value.

Troubleshooting

Fields showing as empty in Zapier Do not rely on Zapier's built-in empty sample — load a real ACS payload by clicking Send Test in ACS and then Test trigger in Zapier. This populates all fields with actual values.

Zap is on but content is not arriving Verify the destination URL in ACS matches the Zapier webhook URL exactly. Check delivery logs in Settings → Integrations → Outbound Webhooks for error details.