<@U04SE163WC8> Access denied (403). The authentica...
# replication-ask-ai
s
@kapa.ai Access denied (403). The authenticated user does not have permissions to access the resource. Verify your scopes: crm.lists.read to access stream campaigns. See details: https://docs.airbyte.com/integrations/sources/hubspot#step-2-configure-the-scopes-for-your-streams-private-app-only
k
The error you're seeing means your HubSpot Private App API token is missing the
crm.lists.read
scope, which is required to sync the
campaigns
stream. To resolve this: 1. Go to your HubSpot account and navigate to your Private App settings. 2. Add the
crm.lists.read
scope to your Private App. 3. Regenerate/copy the updated access token. 4. Update your Airbyte HubSpot source connection with the new token. This is confirmed by the connector's test configuration, which maps the
campaigns
stream to the
crm.lists.read
scope at the endpoint
https://api.hubapi.com/email/public/v1/campaigns
. [scope mapping] For full details on which scopes are required for each stream, refer to the HubSpot setup guide. 👍 0 button 👎 0 button â„šī¸ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
s
do i have to use the updated token, will the old token not work @kapa.ai
k
Yes, you need to use the updated token. When you add new scopes to a HubSpot Private App, HubSpot generates a new access token that includes those scopes — the old token will not automatically gain the new permissions. This behavior is confirmed by the HubSpot connector documentation context: Private App tokens are static and cannot be refreshed automatically. The connector's error handler explicitly treats a 401 (invalid/expired token) for Private App credentials as a permanent config error, with the message "Please, update your Private App access token. Current token is invalid or expired." [components.py] So the steps remain: 1. Add
crm.lists.read
to your Private App in HubSpot. 2. Copy the new access token generated after saving the scope changes. 3. Update your Airbyte HubSpot source with the new token. The old token simply won't have the required scope and will continue to return 403 errors for the
campaigns
stream. 👍 0 button 👎 0 button â„šī¸ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.