Turn one discovered agentic action ON so it can be resolved and frozen (Zapier)
For a Zapier AGENTIC (dynamic-discovery) MCP server, turn ONE discovered action (see POST …/tools/discover) ON in the connected account so it appears in the enabled set and can be resolved + frozen — so a fresh/empty server isn’t a dead-end. Because it MUTATES the connected account’s enabled set, this is integrations:write (unlike the discover/resolve reads); it never surfaces the credential/endpoint and invalidates the org’s enabled-actions cache so the freshly-enabled action shows on the next GET …/tools. Zapier-only (400 tools_not_supported for a non-MCP kind); 409 integration_not_connected if not connected; 422 when action is missing.
Authorizations
Flowyte secret API key (Authorization: Bearer flowyte_sk_live_…). Scope-gated; is scoped to your organization — a key can never reach another tenant. The listed scopes in each operation's apiKey requirement are the scopes that key must hold. The tokenUrl is nominal: keys are minted in the dashboard.
Path Parameters
google_calendar, google_sheets, calendly, hubspot, square, opentable, shopify, postgres, mysql, zapier Body
Response
The freshly-enabled action's projection.