Skip to content

Developer tools integration

HTTP / Custom API integration for AI workflows.

Connect any REST API, even without a ready-made integration.

Live

In short

Fluxo Flow connects to HTTP / Custom API with an API key or credentials you provide; workflows can send a request, and start from incoming webhook and new item at an endpoint. The integration is live.

Live means tested end to end against real accounts. Found a problem? Tell us.

What you can do

Actions and triggers for HTTP / Custom API.

Actions

  • Send a request

    Sends a request to a path on the connection's API.

Triggers

  • Incoming webhook (instant webhook)

    Gives you a URL the other system posts events to. Each signed event starts one run.

  • New item at an endpoint (checked on your plan's schedule interval)

    Checks an endpoint on a schedule and starts a run for each new item in its list.

Use cases

What teams build with HTTP / Custom API.

  • Any form or backend into a workflow

    1. HTTP / Custom API: Incoming webhook (signed)
    2. AI Generate: classify and extract
    3. Router
    4. HTTP / Custom API: Send a request
  • Poll an API that has no webhooks

    1. HTTP / Custom API: New item at an endpoint
    2. Transformer: map fields
    3. Slack: Post a message
  • Call an app we don't connect to yet

    1. Scheduled trigger
    2. HTTP / Custom API: Send a request (vault credential)
    3. AI Generate
    4. Send Email

Step-by-step guides: How to secure a webhook: secrets, HMAC signatures, timestamps and IP allowlists · Duplicate records, retries and failures: making automations safe to re-run

Integration guides

HTTP / Custom API with other apps.

How to connect

Connect HTTP / Custom API in a minute.

Connects with an API key or credentials, tested before they're saved and encrypted at rest.

  1. Open Settings → Integrations and click Connect on HTTP / Custom API.
  2. Enter the API's base URL and how it authenticates (bearer token, API key in a header or query parameter, or Basic).
  3. Use “Send a request” in a workflow, or start one from an incoming webhook or a polled endpoint.

What you need on the HTTP / Custom API side

  • The API's base URL and how it authenticates: a bearer token, an API key header or Basic auth.

Permissions & limits

What it can access, and how fast it runs.

Limits and timing

  • Polling triggers are checked on your plan's schedule interval: Basic every 15 minutes, Pro every 5 minutes, Business every 2 minutes, Elite every minute.
  • Instant triggers arrive by webhook within seconds of the event.
  • If HTTP / Custom API says to slow down (HTTP 429 or 503), requests wait as told and retry a limited number of times.
  • Requests to private, internal or loopback addresses are blocked, including through redirects.

FAQ

HTTP / Custom API questions, answered.

Can it call servers on my private network?

No. For security, requests to private, internal or loopback addresses are blocked, including through redirects.

Where are my API keys stored?

Encrypted in your workspace's vault. They're decrypted only on our servers when a request is sent, and never shown again or included in exports.

Is the HTTP / Custom API integration ready to use?

Yes. HTTP / Custom API is live: connect it in Settings → Integrations on any plan, including Free (on Free you can build with it and Dry Run; running it live needs a paid plan).

Can I test a workflow without touching my real data?

Yes. Dry Run walks through every step with simulated app calls, so nothing is sent until you run it for real or activate its trigger.

All integrations

Connect HTTP / Custom API to your first workflow.

Build and Dry Run on the Free plan, no credit card. Run live on a paid plan, on your own AI key at cost.

Free to explore · No credit card · 30-day money-back guarantee on paid plans