Connect Foundry to HubSpot to import data and create, modify, and delete records in HubSpot.
Learn more about setting up a connector in Foundry.
The HubSpot source authenticates with a private app access token.
Create a private app in your HubSpot account and copy its access token. For the current steps, review the HubSpot private app documentation ↗.
The private app must meet the following requirements for this connector to work:
A private app with insufficient scopes still authenticates successfully. The source connects without an error and silently omits every table the token cannot reach, so tables missing from exploration usually indicate missing scopes rather than a connection problem. Two later changes in HubSpot produce the same result: a private app loses scopes when the HubSpot account subscription is downgraded, and rotating the access token with the Rotate and expire later option expires the previous token seven days afterward.
The table below lists the domains that the source must access to run.
For Foundry worker connections, add an egress policy for each domain.
If the domains are on another network and you use agent proxy egress policies (preferred) or an agent worker (not recommended), the agent must be able to reach them. The systems on those domains must also allow connections from the agent. Learn more about agent networking.
| Domain | Required |
|---|---|
api.hubapi.com | Always |
| Option | Required? | Description |
|---|---|---|
Private app token | Yes | The access token copied from the private app in HubSpot. |
HubSpot stopped allowing new API keys to be created on July 15, 2022 and sunset API key authentication on November 30, 2022. Review the HubSpot API key sunset changelog ↗ for details. Existing sources that use an API key must be migrated to a private app access token.