The library keeps app search, categories, navigation, and pagination visible while the results scroll. Browse recommended apps or the pinned Pipedream catalog, using the provider’s real logo to find the right service. Returning from an app restores your place in the results.

Connect once, then choose what to do#

  • Open Integrations and find the app. Inspect its available capabilities and account permissions.
  • Choose an existing account you own, or authorize a new one through the provider connection flow. The development configuration may ask you to sign in to Pipedream in the same browser.
  • Continue through Connection → Available tools → Ready. Search the supported actions and inspect their real input fields.
  • Choose Use in a Flow to open an unsaved Flow with that connection and action selected. Connecting alone does not run an action or start synchronization.

Build with the tools the connection exposes#

In a Flow, add Use an integration, select the account, and choose an action. Fill its native input fields, use supported account-backed dropdowns, or bind values from a previous step. Objects and arrays can use JSON. Unsupported input types or extra authentication requirements are explained by the picker.

Review before running is the default. Publish the Flow, run it manually, and review the exact inputs for a real test. A real test can change the external service. A graph preview never invokes the provider. Run automatically after publishing is a separate, explicit permission for that saved step.

Map result or exports properties into later steps. Pagination is explicit: use the provider’s cursor or page inputs if more results are needed. Combine lookup, conditions, create/update, and iteration steps to bring chosen records into a sheet. One action is not an automatic complete-table or two-way sync.

Understand the available data routes#

RouteWhat it means
Supported connected actionRun a provider action with its exact version, inputs, and owned account.
PostgreSQL source setupDiscover a table, preview bounded records, map/import, and activate through separate reviewed steps when the source adapter is available.
Authenticated API requestFor approved apps, call their verified static HTTPS API host with provider-managed credentials. It is not an arbitrary URL or raw-credential proxy.

Cloudflare D1 may be accessed through an available Cloudflare API-request tool when that connection permits the endpoint. There is no universal D1 sync adapter implied by the catalog. Updating a signup row alone does not grant access to Ralti; approval must use the supported access-grant process.

Keep connections understandable#

  • Open Connections to see the saved account verification, app, sources, and available actions.
  • Use Check connection for an explicit metadata check. It does not read source records or activate sync.
  • Use Connect again when an account needs authorization. Reconnecting does not silently reactivate paused sources.
  • Use Remove from Ralti to remove the workspace’s saved link. Resolve linked-source dependencies first. This does not revoke provider authorization or delete native sheet records.

Know when to review an outcome#

Execution checks current account ownership, workspace access, rollout eligibility, and the pinned tool version. Credentials stay out of graphs and model context. Connection-derived inputs and results remain private to their currently authorized owner; values deliberately written into a normal sheet follow that sheet’s visibility.

If a provider response is interrupted after dispatch, the run asks for outcome review rather than automatically sending the action again. Check the provider before reconciling it. Confirming delivery does not manufacture missing response data for later steps.

Agents and Apps reuse these connected capabilities with their own grants and reviews. A connection does not automatically authorize an agent, publish an app journey, subscribe to provider events, or enable universal background synchronization.