Search a connected agentic account's available actions to enable (Zapier)
For a Zapier AGENTIC (dynamic-discovery) MCP server, search the connected account’s AVAILABLE actions (by app/action free text — empty ⇒ the server’s default set) so the picker can offer them to enable. This is the escape hatch that keeps a fresh/empty agentic server from being a dead-end picker: discover → enable → resolve → freeze. Each returned action carries the identity the enable call needs (selectedApi + action) plus display text. 0-task authoring read; never surfaces the credential/endpoint. Zapier-only (400 tools_not_supported for a non-MCP kind); 409 integration_not_connected if not connected. Scope integrations:read.
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
Free-text app/action search (empty ⇒ the server's default set).
Response
The discovered actions an operator can enable, plus any server hint.