Skip to main content
The Zapier integration turns three Carousify events — Post Published, Post Scheduled, and Post Publishing Failed — into Zap triggers. From there, you can route them into any of the 5,000+ apps Zapier supports without writing code: log every published post into a Google Sheet for client reports, post a card in Microsoft Teams, append a row to Airtable, send an SMS via Twilio, anything. This is the integration to reach for when Carousify’s native Slack and Notion integrations don’t cover what you want to wire up.
Carousify on Zapier is currently invite-only — you’ll use a public invite link to install the integration on your Zapier account. Once you’ve accepted, every Zap you build with Carousify behaves exactly like a publicly-listed app.

What you can build

A few of the most common Zaps teams set up on day one:
Use caseTriggerAction
Log every published post for client reportsPost PublishedGoogle Sheets — Create Spreadsheet Row
Alert a Microsoft Teams channel on publish failuresPost Publishing FailedMicrosoft Teams — Send Channel Message
Append scheduled posts to a content calendarPost ScheduledAirtable — Create Record
SMS the team when a high-priority client’s post failsPost Publishing Failed (filtered by Account)Twilio — Send SMS
This page walks through the Google Sheets example end-to-end. The same pattern works for any other action Zapier supports.

Triggers

Carousify exposes three instant triggers:
TriggerFires when
Post PublishedA post goes live on LinkedIn (instant or scheduled).
Post ScheduledA post is queued for a future date and time.
Post Publishing FailedLinkedIn rejected the post or auth expired before publishing.
All three are “Instant” triggers — Carousify pushes the event to Zapier in real time, so Zaps run within seconds of the event firing in your Carousify workspace.

Trigger payload

Every event sends the same shape so you can map fields consistently across Zaps. Here’s the reference:
FieldTypeNotes
Eventstringpost.published, post.scheduled, or post.failed.
Timestampunix msWhen the event fired.
Data IdstringThe internal Carousify post ID.
Data Workspace IdstringWhich workspace the post belongs to.
Data User IdstringThe Carousify user who created the post.
Data Account Typestringprofile or pages.
Data Account IdstringLinkedIn vanity name of the account/page (e.g. carousify).
Data ContentstringThe post body text.
Data Titlestring (optional)Post title, if you set one. Often empty.
Data Mediaarray (optional)URLs of images/videos attached to the post.
Data Statusstringscheduled, published, failed.
Data Post Urnstring (optional)LinkedIn URN once published — useful as a stable identifier.
Data Utm Campaignstring (optional)UTM tag if link tracking was on.
Data Posting TimeISO 8601When the post is/was scheduled to publish.
Data Created AtISO 8601When the post record was created in Carousify.
Data Updated AtISO 8601Last modification timestamp.

Step 1 — Generate a Carousify API key

In Carousify, go to Manage Workspace › Integrations and click Connect on the Zapier card. Give the key a name you’ll recognise later (e.g. Carousify Zapier) and click Create API Key. Carousify Create an API Key for Zapier modal Carousify reveals a 32-character key. Copy it — you’ll paste it into Zapier in Step 4. Generated Carousify API key with copy and Done buttons
Treat this key like a password. Anyone with it can pull post data and connect to Carousify on your behalf. If it leaks, click Disconnect on the Zapier card in Carousify — that revokes the key — and run through the flow again to generate a new one.

Step 2 — Accept the public invite

Open the Carousify-on-Zapier invite in a new tab: zapier.com/developer/public-invite/240907/e0a7c942dc2c8d7f5c376a77233141a0/ Zapier 'You've been invited to use Carousify' page with Accept Invite button Click Accept Invite & Build a Zap. Zapier installs the Carousify app on your account and lands you on your Zaps dashboard.

Step 3 — Start a new Zap

Click Create Zap (or + Create in the sidebar). Zapier opens an empty editor with a placeholder trigger and action. Zapier editor with empty trigger and action steps Click the Trigger card to open the app picker, search Carousify, and select the result tagged Invite Only. Zapier trigger panel with Carousify selected as the app In the Trigger event dropdown, pick the event you want — for the Google Sheets demo, choose Post Published. Zapier trigger event picker showing Post Published, Post Scheduled, and Post Publishing Failed

Step 4 — Sign in with your Carousify API key

Click Sign in to Carousify (or Connect Carousify). A popup appears asking for your API Key. Zapier API Key popup for Carousify Paste the key from Step 1 and click Yes, Continue to Carousify. The popup closes and Zapier shows your Carousify workspace as the connected account. Click Continue.

Step 5 — Pull a sample event

Click Test trigger. Zapier asks Carousify for a recent event so you can see exactly what data the trigger emits. Zapier trigger sample showing Carousify post fields including Data Posting Time, Data Account Id, and Data Content You should see the field list from the Trigger payload reference above. If you don’t have any published posts yet, Zapier returns a stub example — that still works for mapping fields. Click Continue with selected record.

Step 6 — Add a Google Sheets action

Click the Action card. Search Google Sheets and pick it. For Action event, choose Create Spreadsheet Row and click Continue. Zapier action with Google Sheets and Create Spreadsheet Row selected Sign in to your Google account if you haven’t already. Then under Configure:
  • Spreadsheet — pick the sheet you want to log into (e.g. Carousify x Zapier).
  • Worksheet — pick the tab. Zapier reads the header row to populate the column inputs below.
Zapier Configure tab showing Spreadsheet and Worksheet pickers

Step 7 — Map Carousify fields to your sheet columns

Each column in your sheet appears as an input. Click Add a field mapping next to each and pick the matching Carousify field from the previous step. For a sheet with columns Published At / Topic / Account / Post URL, the natural mapping is:
Sheet columnCarousify field
Published AtData Posting Time
TopicData Title (or Data Content if you’d rather log the body)
AccountData Account Id
Post URLData Post Urn
Zapier action fields mapped to Carousify trigger fields Click Continue.

Step 8 — Test and publish

Zapier shows a preview of the exact payload it’ll send to Google Sheets. Zapier preview of the data that will be written to Google Sheets Click Test step. Zapier writes a real row to your sheet and reports back with the row number. Zapier test step success showing a row was sent to Google Sheets Open your Google Sheet — you should see a fresh row with the sample data. If everything looks right, click Publish in the top-right. Zapier confirmation that the Zap is live The Zap is now live. Every time Carousify publishes a post under this workspace, Zapier appends a new row to your sheet within a few seconds.

Filtering by account or status

A common follow-up is restricting a Zap to a specific LinkedIn account or only failed posts. Add a Filter by Zapier step between the trigger and the action:
  • Field: Data Account Id  Condition: (Text) Exactly matches  Value: your vanity, e.g. carousify
  • Field: Data Status  Condition: (Text) Exactly matches  Value: failed
The Zap will only proceed past the filter when both conditions match.

Disconnect or rotate the key

To rotate the API key (recommended every 90 days, or whenever someone leaves the team):
  1. In Carousify, open Manage Workspace › Integrations and click Disconnect on the Zapier card. The current key stops working immediately.
  2. Click Connect again, generate a new key.
  3. In Zapier, open App connections and click Reconnect on the Carousify entry. Paste the new key.
Disconnecting in Carousify also invalidates any in-flight Zaps — they’ll show an auth error until you reconnect on the Zapier side.

Troubleshooting

  • “API Key Unrecognized” during sign-in. The key was disconnected on the Carousify side, or you copied it with extra whitespace. Generate a fresh key and try again.
  • No sample data when testing the trigger. You don’t have any matching events in your account yet — schedule or publish a real post in Carousify and click Test trigger again.
  • Published At lands as a number in Sheets. Toggle Use Timezone set up on the spreadsheet to format date values? to True in the Google Sheets action — Zapier will then format Data Posting Time as a readable timestamp.
  • Zap stops firing. Check Zap history in Zapier for the failure reason. Most common causes: the Carousify API key was rotated without updating Zapier, or the underlying LinkedIn account got disconnected.

What’s next

Slack notifications

Same three events delivered straight into a Slack channel without going through Zapier.

Notion scheduling

Schedule posts from a Notion database — no Zapier needed.

Schedule a post

Trigger your first Post Scheduled event and watch the Zap run.

MCP server

For developers who’d rather drive Carousify from Claude or VS Code.