HubSpot Destination

Nexla's bi-directional connectors allow data to flow both to and from any location, making it simple to create a FlexFlow, DB-CDC, Spark ETL, or Replication data flow that sends data to a HubSpot location.

Hubspot

Create a HubSpot Destination

1. Click the + icon on the Nexset that will be sent to the HubSpot destination, and select the Send to Destination option from the menu.

2. Select the HubSpot connector from the list of available destination connectors. Then, select the credential that will be used to connect to the HubSpot organization, and click Next; or, create a new HubSpot credential for use in this flow.

3. In Nexla, HubSpot destinations can be created using pre-built endpoint templates, which expedite destination setup for common HubSpot endpoints. Each template is designed specifically for the corresponding HubSpot endpoint, making destination configuration easy and efficient.
   • To configure this destination using a template, follow the instructions in Configure Using a Template.

   HubSpot destinations can also be configured manually, allowing you to send data to HubSpot endpoints not included in the pre-built templates or apply further customizations to exactly suit your needs.
   • To configure this destination manually, follow the instructions in Configure Manually.

Configure Using a Template

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common HubSpot endpoints. Each template is designed specifically for the corresponding HubSpot endpoint, making destination setup easy and efficient.

• To configure this destination using a template, select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

  Create Contacts

  Create contacts in Hubspot. Each record of the dataset will result in a new contact. Check out the API documentation link for required dataset schema.

  • This endpoint automatically creates new contacts in your HubSpot account using data from your Nexset. No additional configuration is required beyond selecting this endpoint template.
  • The endpoint uses POST requests to https://api.hubapi.com/crm/v3/objects/contacts. The endpoint URL is automatically constructed based on the HubSpot API base URL.
  • The endpoint sends data from your Nexset as the request body in JSON format. The request body is automatically formatted according to the schema fields and data mapping you configure. Each record in your Nexset will be sent as a JSON object containing the contact data to create.
  • Batch mode is disabled by default for this endpoint. Each record in your Nexset will be sent as a separate API request to create a contact. If you need to create multiple contacts, you can send multiple records, but each will be processed as a separate request.
  • This endpoint does not automatically create a data source to track the responses received from the HubSpot API after each call.

  The request body must be properly formatted JSON that matches the HubSpot API specification for creating contacts. The endpoint requires OAuth2 authentication via the Authorization: Bearer {token} header, which is handled automatically by your credential configuration. The Content-Type: application/json header is automatically included in requests. Please check the API documentation link for the required dataset schema. Batch mode is disabled by default (batch.mode: false), so each record will be sent as a separate request. For detailed information about creating contacts, including required fields, field names, and request formats, see the HubSpot Contacts API documentation.

  Create Deals

  Create deals in Hubspot. Each record of the dataset will result in a new deal. Check out the API documentation link for required dataset schema.

  • This endpoint automatically creates new deals in your HubSpot account using data from your Nexset. No additional configuration is required beyond selecting this endpoint template.
  • The endpoint uses POST requests to https://api.hubapi.com/crm/v3/objects/deals. The endpoint URL is automatically constructed based on the HubSpot API base URL.
  • The endpoint sends data from your Nexset as the request body in JSON format. The request body is automatically formatted according to the schema fields and data mapping you configure. Each record in your Nexset will be sent as a JSON object containing the deal data to create.
  • Batch mode is disabled by default for this endpoint. Each record in your Nexset will be sent as a separate API request to create a deal. If you need to create multiple deals, you can send multiple records, but each will be processed as a separate request.
  • This endpoint does not automatically create a data source to track the responses received from the HubSpot API after each call.

  The request body must be properly formatted JSON that matches the HubSpot API specification for creating deals. The endpoint requires OAuth2 authentication via the Authorization: Bearer {token} header, which is handled automatically by your credential configuration. The Content-Type: application/json header is automatically included in requests. Please check the API documentation link for the required dataset schema. Batch mode is disabled by default (batch.mode: false), so each record will be sent as a separate request. For detailed information about creating deals, including required fields, field names, and request formats, see the HubSpot Deals API documentation.

Configure Manually

HubSpot destinations can be manually configured to send data to any valid HubSpot API endpoint. Manual configuration provides maximum flexibility for accessing endpoints not covered by pre-built templates or when you need custom API configurations.

With manual configuration, you can also create more complex HubSpot destinations, such as destinations that use custom request headers, different HTTP methods, or custom data formatting.

Content Format

1. Select the format in which the Nexset data will be sent to the HubSpot API from the Content Format pulldown menu. Nexla will automatically convert the data to the selected format for each API call. The HubSpot API typically uses JSON format for request bodies.

API Endpoint URL

2. Enter the URL of the HubSpot API endpoint to which you want to send the Nexset data in the URL field. This should be the complete URL including the protocol (https://) and any required path parameters. HubSpot API endpoints typically follow the pattern https://api.hubapi.com/{endpoint_path}.

Ensure the API endpoint URL is correct and accessible with your current credentials. You can test the endpoint using the Test button after configuring the URL. The endpoint requires OAuth2 authentication via the Authorization: Bearer {token} header, which is handled automatically by your credential configuration. For detailed information about HubSpot API endpoints and available APIs, see the HubSpot API documentation.