Dynamic per-user Authorization header in Intercom Data Connectors | Community
Skip to main content
Question

Dynamic per-user Authorization header in Intercom Data Connectors

  • June 16, 2026
  • 0 replies
  • 2 views

Forum|alt.badge.img+1

Hi everyone,

We’re trying to build an Intercom Data Connector that retrieves customer-specific data from our backend.

Our backend API requires a user-specific access token. This token is generated only after the customer completes an OTP/authentication flow, and each customer receives a different token.

The flow we want to support is:

  1. The customer completes OTP authentication.

  2. The OTP/auth connector returns a response containing:

{
"data": {
"access_token": "..."
}
}
  1. A second connector should then call our recommendations API using that token in the Authorization header:

Authorization: Bearer <data.access_token>

The issue:

When we try to pass the token dynamically in the connector header, for example:

Authorization: Bearer {{accessToken}}

or by using a value returned from a previous connector/action, our backend does not receive the Authorization header/token.

The only setup that worked was using Intercom’s Authentication Token feature with a static Text token. However, this does not work for our production use case, because the token must be dynamic and customer-specific.

What we need to understand:

  1. Do Intercom Data Connectors support dynamic per-user values in the Authorization header?

  2. Can a Fin Procedure/Task take data.access_token from one connector response and pass it as Authorization: Bearer <token> in a later connector request?

  3. If this is supported, what is the recommended setup or correct syntax?

  4. If this is not supported, what is the recommended architecture for this use case?

In short:

  • OTP/auth connector returns: data.access_token

  • Recommendations connector needs to call our API with: Authorization: Bearer <data.access_token>

  • A static Authentication Token is not suitable because the token changes per user

  • Adding the token manually as a header input does not appear to pass it to our backend

Could you please confirm whether this flow is supported, and if so, how it should be configured?