Skip to main content
Integration actions let you query provider records and perform supported operations without writing a provider client. Search the actions available in your selected organization, then pass an action’s app, key, and input to the runner.

CLI

For larger inputs, use --input-file ./input.json instead of --input. Both accept a JSON object. Search accepts --limit from 1 to 100 and defaults to 40 results. Omit --app to search all available integrations. Each search result includes the action’s input schema, description, approval_required, and metered. metered describes Pipedream action execution charges; it does not describe a provider’s own pricing. Native provider operations can also incur charges under your provider account.

REST API

Use the same authentication and organization selection as other REST endpoints.
The optional organization_slug body field selects a client’s own connected integration for a read action. You must be a member of the client organization or an admin or owner of an organization that manages it. Omit it, or pass your selected organization’s slug, to use your current connections as usual. Scoped credentials and guests cannot cross organizations. Client reads use the client’s account selection and permissions, and their result includes organization_slug. Writes to a client’s integration are refused before execution: propose the change and approve it in the client’s organization. The CLI has no client-slug option on action calls; select the client with --org to search or run there.

MCP

Call erdo_search_integration_actions with optional query, app, and limit. Then call erdo_run_integration_action with app, key, and input. Pass optional organization_slug to run a read through a client’s connection. MCP/REST action search uses the selected organization; select the client to discover its actions. In chat and scheduled runs, both search_integration_actions and run_integration_action accept organization_slug. Dynamic-option lookup and pipedream_proxy remain in the current organization’s scope. Search belongs to the core toolset; execution belongs to account. With curated tools enabled, request ?toolsets=account or invoke the runner through erdo_call_tool. Use the app returned on the action itself: related actions can belong to a different app from the one you searched.

Results and approvals

Run responses have a status:
  • succeeded: the action returned successfully; its output is in result.
  • pending_approval: a reviewed action filed an approval. Decide the returned approval_request_id with erdo approvals decide; Erdo executes it after approval.
  • in_progress: the returned approval already authorized an execution that is still in flight. No new approval or provider call was made.
  • declined: a recent decline still covers this proposal; no new ask was filed.
  • approval_required: the action did not execute. The response names the action and describes it. Ask an Erdo agent to perform it through the approval flow. Actions outside the reviewed run-less executor require an agent-run approval. The endpoint never accepts an approval bypass.
  • failed: execution failed. Read error and any structured provider details in result before deciding whether to retry.
The CLI prints the response as JSON. succeeded, pending_approval and in_progress exit successfully; a refusal, decline or provider failure exits nonzero. Authentication, malformed requests, and unavailable discovery can also return HTTP errors. The runner uses the agent execution path, including caller permissions, approval gates, provider error handling, and Pipedream spend reservations. An empty action search means no matching operation was found in the catalogue; it says nothing about whether provider records exist.