Automation library · Customer support

Convert Supabase support FAQs to audio with Google Cloud TTS

Started by another system calling it. It calls services over plain HTTP rather than through connectors. 16 steps, 1 loop or waits: a working afternoon to understand properly.

Medium

16 stepsMedium: a working afternoon
0Branches: places the flow splits
1Loop or waits
0Services by connector: it calls them over plain HTTP

The flow

Starts it 2Logic 8Service 6

The steps in the order they run, from what starts it.

  1. 1Webhook, Receive FAQ Audio Job RequestWebhookStarts it
  2. 2Code, Build Teams Card & Summary ObjectCodeLogic
  3. 3Supabase, Read Unprocessed FAQsHttp RequestService
  4. 4Microsoft Teams, Send FAQ Audio Summary CardHttp RequestService
  5. 5Code, Filter & Split FAQ RowsCodeLogic
  6. 6Respond to Webhook, Return JSON SummaryRespond To WebhookStarts it
  7. 7Item Lists, Deduplicate by FAQ IDItem ListsLogic
  8. 8Item Lists, Sort by Category then IDItem ListsLogic
  9. 9Code, Build SSML for Each FAQCodeLogic
  10. 10Loop Over Items, Process One FAQ at a TimeSplit In BatchesLogic
  11. 11Google Cloud TTS, Synthesize FAQ AudioHttp RequestService
  12. 12Code, Decode Base64 Audio to BinaryCodeLogic
  13. 13UploadToURL, Host FAQ MP3 on CDNHttp RequestService
  14. 14Code, Capture Audio URL + TimestampCodeLogic
  15. 15Webflow, Patch FAQ CMS Item with Audio URLHttp RequestService
  16. 16Supabase, Write Audio URL & Status BackHttp RequestService

How it's built

Starts on
Another system calling it
Steps
16, 1 loop or waits
Size
Medium: a working afternoon
Connects to
Nothing by connector; it calls services over plain HTTP
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account. 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. 16 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 it

Nothing 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 16 steps before you point it at anything that matters.