Retool workflows webhook authorization

  1. My goal: Implement retool workflow calling in an external app, without having to have seperate API key for each workflow.
  2. Issue: I’am trying to implement a few workflows in my external app. What i would like to achieve is not having to have a seperate API key for each workflow. So lets say i have 3 workflows, is there a way to have universal API key to authenticate the webhook requests, instead of having to have Workflow 1 API key, Workflow 2 API key, Workflow 3 API key, …
  3. Additional info: Cloud hosted
1 Like

Hi @Anze_Savli,

Please create a single “Gateway” workflow that starts with a webhook. This will be the only API key exposed to the external application.

Within this gateway, add workflow blocks in sequence—one for each sub-workflow. These internal workflows do not require any external API keys.

Routing logic (based on startTrigger.data.target):

  • "workflow_1" → Trigger workflow_1 via a Workflow block
  • "workflow_2" → Trigger workflow_2 via a Workflow block
  • "workflow_3" → Trigger workflow_3 via a Workflow block

This approach ensures a clean API surface while centralizing access control through a single entry point.



When configuring each Workflow block, simply select the corresponding downstream workflow you want to trigger.


For reference, please see the documentation:
Run another workflow with the Workflow block | Retool Docs

Hi @Anze_Savli!

If you would like a workflow calling in an external app without separate API keys for each workflow you would need to use a self-hosted deployment.

Since you are using Cloud, I would give @WidleStudioLLP 's suggestion a try! Please keep in mind that doing this would increase the number of workflows you use (which may be important if you have a monthly workflow runs quota).

Let us know if you have any other questions!

-Jen

1 Like