The flow
Starts it 2Logic 8Service 7
The steps in the order they run, from what starts it.
- 1Webhook: FX Brief InputWebhookStarts it
- 2On Workflow ErrorError triggerStarts it
- 3Validate & Extract FX BriefCodeLogic
- 4Slack: Error AlertSlackService
- 5Fan-Out: 4 FX VariationsCodeLogic
- 6Build FX Request BodyCodeLogic
- 7Seedance: Generate FX ClipHttp RequestService
- 8Merge FX Job ID + MetadataCodeLogic
- 9Poll: Check FX Job StatusHttp RequestService
- 10FX Render Complete?IfLogic
- 11Build FX Asset MetadataCodeLogic
- 12Wait 20sWaitLogic
- 13Notion: Save FX Asset RecordNotionService
- 14Download FX VideoHttp RequestService
- 15Aggregate All FX VariationsCodeLogic
- 16Google Drive: Upload FX ClipGoogle DriveService
- 17Slack: Notify FX TeamSlackService
How it's built
- Starts on
- Another system calling it
- Steps
- 17, with 1 branch, 1 loop or waits
- Size
- Medium: a working afternoon
- Connects to
- Google Drive, Notion, Slack
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Google Drive, Notion and Slack accounts. You connect your own accounts after importing it; none are included.
What starts it?
It starts on another system calling it.
Does it use AI?
No. Every step is fixed logic or a call to a service, so it does the same thing every time.
How long does it take to set up?
Plan an afternoon. 17 steps is enough that you should read each one before running it.
How do I import it?
Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.
Before you run itNothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 17 steps before you point it at anything that matters.