This document shows an example of what needs to be done in Hubspot to make it integration-ready with ONEiO. Note also, that the number of fields used in integrations might vary. The document also describes what ONEiO needs to be able to send messages to the Hubspot instance.
Currently, rule robot helps self-service integration for;
Additionally, ONEiO application can provide support for:
Access from ONEiO to Hubspot
ONEiO accesses by Hubspot REST API and works with a polling mechanism.
General settings for Hubspot Endpoint Type on ONEiO
Note: The base URL for Hubspot is always "https://api.hubapi.com"
File Folder to Attachment: Source folder for attachments on Hubspot.
On Hubspot attachments can be added in 2 ways:
- Upload new → Automatically set file restricted with private access. It is not possible to edit access after the file is uploaded.
- Choose existing → Access can be set for public access, which makes it accessible via Hubspot APIs. In order to make a file accessible via APIs and send through ONEiO integration, firstly a folder should be created then the file should be uploaded into this folder.
ONEiO to Hubspot
- To be able to interact with Hubspot ONEiO needs to use an access token. As per the current recommendation, the same can be generated after creating a private app with sufficient scope permissions. Once you have the token simply insert it into the corresponding field of a ONEiO endpoint
After completing settings on Hubspot and ONEiO, you can use ONEiO Rule Robot for integrating Hubspot with set on Endpoint Types on ONEiO.