Call an API

Call an external API — either a saved integration (pick the integration, operation, and connection; credentials stay encrypted and never appear in flow JS…

What it does

Calls an external API. One node, two sources — pick with the Source (mode) toggle:

• Saved integration (mode: "integration") — call a typed, audited, credential-managed integration spec. Pick the integration slug, the operation, and the connection (the per-org credential bundle), then map inputs from {{vars.x}} and outputs back into vars. Inputs render against the regular template scope plus {{conn.*}} (the connection's public config — base URLs, account ids) and {{secret.*}} (decrypted at run time, scrubbed from logs). Credentials are stored encrypted and never appear in flow JSON or run history. The node pins (integrationSlug, integrationVersion, operationKey, connectionId) so a republished spec cannot silently re-route a live flow. After it runs it sets vars.integrationStatus (numeric HTTP status, 0 on pre-flight failure) and vars.integrationOk (boolean), and merges the operation's mapped output fields into vars.

• Ad-hoc HTTP request (mode: "http") — configure a one-off request right on the node: URL, method, JSON body, extra headers, and simple auth (basic / bearer / custom header). The response is saved to {{vars.httpResult}} (or whatever you set under Response variable), with the status in vars.httpStatus and a vars.httpOk boolean for easy branching. URL, body, and headers all support {{vars.x}} / {{event.from}} templates.

Both modes run through the platform's SSRF guard and a bounded timeout, and both support cases so you can route on the status / error class (2xx, 4xx, 5xx, timeout, network).

When to use it

• Look up a caller in your CRM at connect time and pop the record on the agent's screen (pair with screenPop).
• Centralize a third-party API across many flows so credentials live in one encrypted place (saved-integration mode).
• Post to a webhook / Slack / your own API, or hit a one-off endpoint you don't want to formalize as a spec (ad-hoc HTTP mode).

Notes

• Reach for saved integration when the credentials are sensitive or the API is reused across flows; reach for ad-hoc HTTP for quick, public, or one-off calls.
• Output mappings (integration mode) land in vars per the operation's defaultOutputMappings and any transform, so {{vars.<field>}} resolves downstream — e.g. a screen-pop card.
• This node replaces the former separate HTTP request and Integration call nodes; existing flows that still carry those types keep running.