trigger_cloud_flow
Triggers a published CloudFlow with a webhook trigger by flow ID or trigger URL. Executes real actions immediately and returns executionLink. Drafts fail with 403, flows without a webhook trigger with 400, and already-running flows with 409. Manual or scheduled flows use trigger_cloudflow_flow in...
This record as markdown: /tools/doit/trigger-cloud-flow.md
What trigger_cloud_flow does on Doit
AI agents invoke trigger_cloud_flow to trigger actions in Doit. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
flowID | string | Yes | The ID or CloudFlow trigger URL of a published flow with a webhook trigger. |
requestBodyJson | object | — | Webhook payload passed to the flow. Defaults to an empty object. |
Parameters from the server's own tool schema.
Why trigger_cloud_flow is rated High
trigger_cloud_flow triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
The rule that runs trigger_cloud_flow safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Doit, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For trigger_cloud_flow, this is the rule to start with:
trigger_cloud_flow stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Doit, apply this rule, and every trigger_cloud_flow call is checked against it from then on.
Questions about trigger_cloud_flow
Triggers a published CloudFlow with a webhook trigger by flow ID or trigger URL. Executes real actions immediately and returns executionLink. Drafts fail with 403, flows without a webhook trigger with 400, and already-running flows with 409. Manual or scheduled flows use trigger_cloudflow_flow instead. This may modify external cloud resources. It is categorised as a Execute tool in the Doit MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
trigger_cloud_flow accepts 2 parameters: flowID, requestBodyJson. Required: flowID. The full parameter table on this page comes from the server's own tool schema.
Register the Doit MCP server in PolicyLayer and add a rule for trigger_cloud_flow: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Doit. Nothing to install.
trigger_cloud_flow is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the trigger_cloud_flow rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for trigger_cloud_flow. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
trigger_cloud_flow is provided by the Doit MCP server (@doitintl/doit-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Doit, and thousands of servers like it.
This server
Across the catalogue