Appearance
HubSpot Connection
The HubSpot Connection authorizes supported HubSpot CRM operations. It can work with contacts and engagements through Connection commands, server methods, the $io.hubspot API, and a supported authenticated SDK object.
Capabilities
| Capability | Availability |
|---|---|
| Connection service identifier | hubspot |
| Page Flow command | API Request |
| Cloud Flow command | API Request |
| Connection methods | Supported |
| Server API | $io.hubspot |
| Authenticated SDK object | Supported through service name hubspot |
| AI Agent Connection support | Supported |
Authentication Modes
The HubSpot Profile supports:
| Mode | Use |
|---|---|
| Custom Access Token | Supply a private or other supported access token directly. |
| OAuth2 | Authorize through the ioLoop-provided HubSpot OAuth application. |
| Custom OAuth2 | Authorize through your own HubSpot application. |
Custom OAuth2 requires the application's client ID and client secret. Optional custom scopes can be entered as a space-separated list.
The Connection has no additional service settings beyond its name and selected Profile.
API Request Command
The API Request command supports client and server contexts. It accepts a HubSpot API path, HTTP method, request data, query parameters, and supported optional request properties.
When called from Page Flow, the request is executed by the server. Do not allow untrusted browser input to choose arbitrary paths, methods, or payloads. Use Cloud Flow when the application must constrain which HubSpot records and operations are available to the caller.
Server Methods
The HubSpot Server API provides documented operations for:
- Listing, creating, updating, retrieving, searching, and deleting contacts.
- Looking up contacts by identifier or email.
- Creating notes, calls, tasks, email records, and other engagements for contacts.
- Retrieving and listing engagements.
- Listing contacts and engagements by date.
- Executing a supported authenticated API request.
Use the Connection Function Call block or $io.hubspot for exact inputs and return values.
Choosing an Interface
Use the API Request command only when its generic path-and-method model is appropriate. Prefer the named $io.hubspot method when it directly represents the operation, because its documented parameters make the workflow easier to understand and validate.
Use the Connection-backed SDK object for supported provider functionality not covered by the named Server API. Keep all SDK access in Cloud Flow.
Testing
Use a controlled HubSpot account or test records. Confirm the granted scopes before testing create, update, delete, or engagement operations.
Verify pagination, duplicate-contact behavior, required properties, provider validation errors, and rate-limit handling. Page Flow and Cloud Flow tests can change real CRM data.