Integration
Call one of the integrations installed in the workspace from the flow.
The Integration node calls one of the ready-made connections already turned on in the workspace, using the tools it exposes.
It is the lower-configuration alternative to the HTTP request.
Integration or HTTP
The choice is straightforward:
- Integration, when the service is in the platform's catalog. It already knows how to talk to that system, and the access is stored outside the flow's design.
- HTTP request, when the service has no ready-made integration. You set up the method, URL, headers and body.
Prerequisites
The integration has to be registered in the organization and turned on in the workspace before it shows up here.
An empty list in the node means no integration was turned on in that workspace, and the fix is under Workspace › Integrations, accessible to the Owner.
Choose the tool
An integration exposes one or more tools, and the node calls one of them at a time. YouTube, for example, exposes five distinct tools.
The panel's fields change with the chosen tool, and all of them accept variables from earlier nodes.
The current catalog
The platform currently offers DuckDuckGo, GitHub and YouTube. The details of each, with its tools and fields, are in Integrations.
Next steps
- Turn on an integration in the workspace in Integrations.
- For internal systems, compare with MCPs.