DocsIntegrationsHTTP auth

HTTP auth

A credential for an API that the Call a URL node uses. The credential is tied to one address, so a workflow can never send it anywhere else.

CategoryHTTP
Used byCall a URL node
Secret fields3
TestYes

Set it up

  1. Get an API key or token from the service you want to call.
  2. Add an HTTP auth integration with the service's base URL and how it wants the credential.
  3. Press Test.
  4. In a Call a URL node, pick it under Authentication and write the URL as a path, like /v1/rows.

Fields

FieldRequiredWhat it is
Base URLbaseUrlYesWhere the credential may go, like https://api.example.com. Must be HTTPS. A node's URL is a path under it, or a full URL with the same origin.
ModemodeYesBearer (Authorization: Bearer …), Basic (a user name and password) or Header (any header you name).
TokentokensecretNoFor Bearer.
User name and passworduserName, passwordsecretNoFor Basic. Only the password is secret.
Header name and valueheaderName, headerValuesecretNoFor Header, like X-Api-Key. Only the value is secret. Headers the HTTP stack owns, like Host or Cookie, can't be used.

Secret fields are encrypted as soon as you save them and never shown again: the console shows their last four characters so you can tell which one is saved. Replace one to rotate it; workflows pick up the new one on their next step.

Test it

Makes a GET to the base URL with the credential and reports what came back.

Home networksWBSKT calls from the internet and refuses private addresses like 192.168.x.x. The service has to be reachable from outside.

Problems you might see

CodeMeans
INTEGRATION_CONFIG_INVALIDThe base URL isn't HTTPS, or a setting doesn't fit the mode.
INTEGRATION_AUTH_FAILEDThe service refused the credential.
WEBHOOK_ORIGIN_MISMATCHAt send time: the node's URL points away from the base URL.

Codes starting INTEGRATION_ come from saving or testing. Every other integration code is on the error codes page.