Skip to main content
Use HTTP API to connect an API that Flow does not publish as its own integration. An organization administrator creates it from Integrations. Flow builds automation actions from the API source you provide.

​
Automation imports

Use the HTTP namespace when you author an automation:
Replace example_api with your connector key. Existing published automations keep running with the compatibility namespace. Before you edit, test, or publish one again, ask Flow to migrate its imports and save a draft. Migration does not publish the draft. Import HTTP request and result types from @flow/integrations/http. Import common integration types from @flow/integrations:

​
Who can create it

Only an organization administrator can create a custom integration. Anyone else sees Organization administrator required, and Connect stays unavailable. Ask an administrator to set it up from this page.

​
Connect in Flow

1

Find HTTP API

  1. Open Integrations.
  2. Choose Add connection.
  3. In Add connection, search for HTTP API.
  4. Select the HTTP API card.
The wizard is titled Connect an HTTP API.Open Flow
2

Choose who can use the connection

On Teams, Connection available to starts at All teams. All teams includes every current team and teams created later. That choice makes the connection available to all teams in the organization.Clear All teams and select teams when only those teams should use the connection. That choice makes the connection available only to the teams you select.Select Continue.
3

Review permissions

Permissions shows Automations: run provider actions from your automations. How it’s granted reads Follows the API credentials you provide.Select Continue. Flow builds the actions from the API source on Connect.
4

Enter the API and connect

Complete the fields in the tables below, then choose Connect.No authentication creates the connection without a credential window. API key opens a window where you enter the key. If Flow skips part of the API source, it shows Connected with setup warnings.

​
Connection fields

​
API source

​
API key fields

These fields appear when Authentication is API key.

​
After you connect

Flow opens the integration you named. On the Automations tab, an organization administrator selects Enable. For All teams, the tab says Automations is not yet enabled on this connection. An organization administrator selects Enable. Anyone else sees Ask an organization admin to enable Automation. For a selected team, the tab says that team hasn’t enabled Automation on this connection. An organization administrator, or that team’s manager, selects Enable. Anyone else sees Ask an organization admin or this team’s manager to enable Automation. Once enabled, automations can use this connection’s actions, subject to your action policies. A No authentication connection shows its endpoint on the connection details. Reauthorize stays unavailable and explains This connection does not use authentication. The integrations list labels that connection No Auth.

​
Uncertain requests

An API can accept a request before its response times out. If Flow cannot safely repeat a POST or PATCH request, it stops automatic retries and reports an uncertain outcome. Adding an arbitrary idempotency header does not make the request safe to repeat. An API can also change data before returning HTTP 408, 429, or 503. A Retry-After header suggests when to retry; it does not prove that the request had no effect. Flow keeps these unprotected requests uncertain, even when the response includes that header. For example, an API might create an onboarding ticket while Flow is waiting for a response. Check that API for the ticket before you rerun the automation. A rerun can create another ticket. See Run history and debugging for recovery guidance.