Hi Airbyte Support team, I’m facing an issue with the Slack source connector (3.1.7) in Airbyte. The

users

stream includes the

profile

object (with

profile.fields

), but the

profile.fields

object is always empty in the data extracted via Airbyte. When I call the Slack API directly using the same token:

curl -i -H "Authorization: Bearer xoxb-XXXXXXX" \
  "<https://slack.com/api/users.profile.get?user=XXXXXXX>"

the response correctly includes populated

profile.fields

, for example:

"fields": {
  "XfQQTSFF38": {"value": "Sales Team", "alt": ""},
  "XfQEPSBBTK": {"value": "Senior Key Account Manager", "alt": ""}
}

I’ve confirmed: • The token has

users.profile:read

. Could you please help me here? Thank you!

I understand you're experiencing an issue with the Slack source connector where

profile.fields

is always empty, even though the Slack API returns populated data when called directly. Based on the knowledge sources provided, I can see that the Slack connector does include

profile.fields

in its schema. According to the [GitHub issue about full refresh sync](https://github.com/airbytehq/airbyte/issues/42888), the connector's schema for the

users

stream includes:

"fields": {   "description": "Custom fields associated with the user.",   "additionalProperties": true,   "type": ["null", "object"] }

This confirms that the connector is designed to capture custom profile fields. However, the knowledge sources do not contain specific information about why

profile.fields

might be empty in your case, despite the API returning data correctly. Here are a few things to verify based on the available documentation: 1. Connector Version: You're using version 3.1.7. According to the [Slack connector changelog](https://docs.airbyte.com/integrations/sources/slack#changelog), this is a recent version (released 2025-10-29) that includes dependency updates. 2. Required Scopes: The [setup guide](https://docs.airbyte.com/integrations/sources/slack) lists the required Bot Token Scopes, which includes

users.profile:read

- which you've confirmed you have. 3. Sync Mode: The knowledge sources mention a [known issue with full refresh sync](https://github.com/airbytehq/airbyte/issues/42888) that was closed, but this was related to subsequent syncs returning zero records, not empty fields. Unfortunately, the knowledge sources do not explicitly mention issues with

profile.fields

being empty or provide troubleshooting steps for this specific problem. I recommend: - Checking the [Airbyte Forum](https://github.com/airbytehq/airbyte/discussions) for similar issues, as suggested in the [troubleshooting section](https://docs.airbyte.com/integrations/sources/slack#troubleshooting) - Opening a GitHub issue if this appears to be a bug with the connector I'm sorry I couldn't provide a more definitive solution based on the available documentation.

@Henry Mattingly @John (Airbyte) can you help me here please? or tag someone that might be able to help me?

Can you check again with https://docs.slack.dev/reference/methods/users.list and see if it's giving you a different result? This connector uses that endpoint, not users.profile.get, so your comparison may not be 1:1 and the endpoints may not return the same data. If users.list is somehow giving you a different result than Airbyte though, please create an issue and the team can look into it.