Fabl’s Zapier integration lets you connect your production workflows to virtually any tool your organization uses, without writing a single line of code. Using Zapier’s visual automation builder, you can trigger actions in other apps whenever something happens in Fabl — a new rundown is created, a script is approved, or a show is published — or you can use events from other apps to create or update content inside Fabl. Once you connect Fabl to Zapier, your team can build, manage, and iterate on automations entirely within the Zapier interface.Documentation Index
Fetch the complete documentation index at: https://docs.fabl.studio/llms.txt
Use this file to discover all available pages before exploring further.
What you can do with Fabl + Zapier
Fabl exposes a set of triggers (events in Fabl that start a Zap) and actions (things Zapier can do inside Fabl on behalf of another trigger). Together, these let you automate repetitive handoffs between your production stack and the rest of your business.Fabl triggers — events that start a Zap
Fabl triggers — events that start a Zap
Use any of the following Fabl events as the starting point for a Zap:
| Trigger | Description |
|---|---|
| New Rundown | Fires when a new rundown is created in your workspace. |
| Rundown Published | Fires when a rundown is published or exported for distribution. |
| Script Approved | Fires when a script segment is marked as approved by a team member. |
| Segment Updated | Fires when any field in a rundown segment is changed and saved. |
| Show Created | Fires when a new show is added to your workspace. |
| Asset Attached | Fires when a video asset or Frame.io link is attached to a segment. |
| Comment Added | Fires when a comment is posted on a rundown or segment. |
| Status Changed | Fires when a rundown’s production status changes (e.g., Draft → In Review). |
Fabl actions — things Zapier can do in Fabl
Fabl actions — things Zapier can do in Fabl
Use the following actions to update Fabl as part of a multi-step Zap:
| Action | Description |
|---|---|
| Create Rundown | Creates a new rundown in a specified show, with optional template and metadata. |
| Update Rundown Status | Changes the production status of an existing rundown. |
| Add Segment | Appends a new segment to an existing rundown with the fields you specify. |
| Update Segment | Modifies one or more fields on an existing rundown segment. |
| Add Comment | Posts a comment on a rundown or specific segment. |
| Find Rundown | Searches for a rundown by name or ID — useful as an intermediate step in multi-step Zaps. |
Connect Fabl to Zapier
Open your Zapier account
Log in to zapier.com and click + Create Zap to open the Zap editor.
Search for Fabl
In the trigger or action search box, type Fabl and select it from the results. If this is your first time using Fabl in Zapier, you are prompted to connect your account.
Authorize Fabl
Click Connect a new account. Zapier redirects you to Fabl, where you sign in and click Allow access. You are returned to the Zap editor with Fabl connected.
Select your trigger or action
Choose the Fabl trigger or action you want to use, configure any required fields (such as which workspace or show to watch), and click Continue.
Test the step
Click Test trigger (or Test action) to pull in sample data from Fabl and confirm the connection is working. Review the sample payload to make sure the right fields are coming through.
You connect Fabl to Zapier using an API key generated from your Fabl workspace. Find your API key under Settings → API & Integrations → Zapier. Each key is scoped to your workspace and should not be shared.
Example Zaps to get started
The following examples illustrate common ways production teams automate their workflows using Fabl + Zapier. Use them as starting points and adapt them to your own stack.New rundown → Create a Notion page
New rundown → Create a Notion page
Trigger: Fabl — New Rundown
Action: Notion — Create Database ItemEvery time a rundown is created in Fabl, Zapier automatically creates a matching page in your Notion production database. Map Fabl fields like rundown name, show, air date, and status to the corresponding Notion properties so your team always has an up-to-date view without manual copying.
Action: Notion — Create Database ItemEvery time a rundown is created in Fabl, Zapier automatically creates a matching page in your Notion production database. Map Fabl fields like rundown name, show, air date, and status to the corresponding Notion properties so your team always has an up-to-date view without manual copying.
Rundown published → Send an email summary
Rundown published → Send an email summary
Trigger: Fabl — Rundown Published
Action: Gmail (or any email app) — Send EmailWhen a rundown is published in Fabl, Zapier sends an email to your distribution list with the rundown title, air date, and a direct link. This is useful for keeping stakeholders who don’t use Fabl informed about what’s going to air.
Action: Gmail (or any email app) — Send EmailWhen a rundown is published in Fabl, Zapier sends an email to your distribution list with the rundown title, air date, and a direct link. This is useful for keeping stakeholders who don’t use Fabl informed about what’s going to air.
Script approved → Post a Slack message
Script approved → Post a Slack message
Trigger: Fabl — Script Approved
Action: Slack — Send Channel MessageNotify your production channel in Slack the moment a script segment gets approved. Include the segment title, the approver’s name, and a link back to the rundown so your director or producer can act immediately.
Action: Slack — Send Channel MessageNotify your production channel in Slack the moment a script segment gets approved. Include the segment title, the approver’s name, and a link back to the rundown so your director or producer can act immediately.
New Airtable row → Create a Fabl rundown
New Airtable row → Create a Fabl rundown
Trigger: Airtable — New Record
Action: Fabl — Create RundownIf your team plans shows in Airtable, use this Zap to automatically spin up a matching Fabl rundown whenever a new show record is added. Map the Airtable fields — show title, episode number, air date — to the Fabl rundown fields so nothing has to be entered twice.
Action: Fabl — Create RundownIf your team plans shows in Airtable, use this Zap to automatically spin up a matching Fabl rundown whenever a new show record is added. Map the Airtable fields — show title, episode number, air date — to the Fabl rundown fields so nothing has to be entered twice.
Rundown status changed → Update a Google Sheet
Rundown status changed → Update a Google Sheet
Trigger: Fabl — Status Changed
Action: Google Sheets — Update Spreadsheet RowKeep a master production tracker in Google Sheets synchronized with Fabl. Whenever a rundown moves from one status to another (e.g., In Review → Approved), Zapier updates the corresponding row in your tracker automatically.
Action: Google Sheets — Update Spreadsheet RowKeep a master production tracker in Google Sheets synchronized with Fabl. Whenever a rundown moves from one status to another (e.g., In Review → Approved), Zapier updates the corresponding row in your tracker automatically.
Troubleshooting
My Zap is not triggering
My Zap is not triggering
Check that your Fabl API key is still valid under Settings → API & Integrations → Zapier. If you recently changed your password or revoked API keys, you need to reconnect Fabl in Zapier. Also verify that the Zap is turned on — a grey toggle in Zapier means the Zap is paused.
Fabl data fields are missing in the Zap editor
Fabl data fields are missing in the Zap editor
Run the Test trigger step again to refresh the sample data. If fields are still missing, make sure the rundown or segment you are testing against actually has those fields populated in Fabl. Zapier can only surface fields that appear in the sample payload.
I hit the Zapier task limit
I hit the Zapier task limit
Each Zapier plan includes a monthly task limit. If your Zaps stop running mid-month, upgrade your Zapier plan or reduce the frequency of triggers by adding Filter steps to your Zaps.