All about HubSpot

HubSpot: Get sales orders from HubSpot

Get deals or invoices from HubSpot, with customer, contacts and order lines, and send them to accounting software or an ERP system.

Updated November 9, 2026

This flow gets deals or invoices from HubSpot and sends them as a sales order to another application, for example accounting software or an ERP system. APIcenter includes the customer, the contacts, the order lines and the discounts.

Deals or invoices

With the setting Do you want to retrieve Deals or Invoices?, you choose what APIcenter gets: Deals (default) or Invoices, the invoices of HubSpot. The default data mapping is based on deals. If you get invoices, check the Data mapping.

How it works

  • For deals, APIcenter filters on the pipeline, which is required, and on the deal stage.
  • APIcenter only gets deals or invoices that changed after the date you set, the oldest change first. In each run, APIcenter gets at most the amount you set, by default 10. After each run, APIcenter sets the date to the modification date of the last record.
  • For each deal, APIcenter gets the linked company, the contacts, the order lines (line items) and the discounts. With Add additional product details, APIcenter also gets the data of the linked product.
  • The order number is the HubSpot ID of the deal. The name of the deal becomes the order reference, the deal stage becomes the status and the currency comes from deal_currency_code.
  • If a deal has no company, APIcenter creates a company from the data of the first contact. If a deal has no contact, APIcenter creates a contact from the data of the company. APIcenter skips a deal that has no company and no contact.
  • APIcenter remembers which deals and invoices it already passed on and does not pass them on again, even if they changed later.
  • After getting the data, APIcenter can move the deals it got to another pipeline and deal stage. This way you can clean them up in HubSpot. You do this with the pipeline and the deal stage. In the same way, you can update the pipeline and stage of the companies and contacts. If you leave the fields empty, nothing is updated. Invoices are not updated.

What you need first

  • HubSpot is connected to APIcenter. See Connect HubSpot to APIcenter.
  • There are deals in the pipeline and deal stage that you filter on, with a linked company or contact.
  • The company property for the e-mail address exists in HubSpot. By default, this is company_email.
  • The other application in the integration can receive orders.

Tips

  • Is an order missing in the target system? Check the pipeline, the deal stage and the date. If the deal was already passed on earlier, APIcenter does not get it again.
  • If you use the deal stage as a filter, put the deals that are ready for APIcenter in that stage in HubSpot. With another stage after getting the data, you prevent seeing them again.
  • Do you need fields that are not sent by default, such as a custom property on the deal? Add them under Data mapping.

Below you find all settings of this flow, each with its own explanation.

Settings

The settings you see in the dashboard, with what each one does.

The name or label of the company property in HubSpot that holds the e-mail address of the company. Default: company_email. APIcenter uses this e-mail address to recognize a company and to identify the customer in the activities. If the property does not exist in HubSpot, the flow stops with an error message, unless Create missing properties in the target system is on: then APIcenter creates the property. This field is required. When sending, the e-mail address in the data mapping must go to the same property.

The lifecycle stage for companies, as the name or ID of the stage in HubSpot (uppercase and lowercase letters do not matter). Default: customer. For Send Customer and Send Sales Order, the companies that APIcenter sends get this stage; this is required, unless you only process contacts. For Get Customer and Get Sales Order, APIcenter updates the companies it got to this stage after getting them; if you leave the field empty, nothing is updated. According to HubSpot, the standard tools can only move the lifecycle stage forward; for an earlier stage, the value must be cleared first. Test this with an example.

The lifecycle stage for contacts, as the name or ID of the stage in HubSpot (uppercase and lowercase letters do not matter). Default: customer. For Send Customer and Send Sales Order, the contacts that APIcenter sends get this stage; this is required. For Get Customer and Get Sales Order, APIcenter updates the contacts it got to this stage after getting them; if you leave the field empty, nothing is updated. According to HubSpot, the standard tools can only move the lifecycle stage forward; for an earlier stage, the value must be cleared first. Test this with an example.

Pipeline to set for companies

Customer Settings

The pipeline for companies. Enter the name or ID of the pipeline in HubSpot; uppercase and lowercase letters do not matter. Default: companies-lifecycle-pipeline. For Send Customer and Send Sales Order, APIcenter sets this pipeline and the lifecycle stage for companies on the companies that it sends. This is required, unless you only process contacts (Only process contact information). For Get Customer and Get Sales Order, APIcenter updates the companies it got to this pipeline and stage after getting them; if you leave the fields empty, nothing is updated. Always fill in the pipeline and the stage together.

Pipeline to set for contacts

Customer Settings

The pipeline for contacts. Enter the name or ID of the pipeline in HubSpot; uppercase and lowercase letters do not matter. Default: contacts-lifecycle-pipeline. For Send Customer and Send Sales Order, APIcenter sets this pipeline and the lifecycle stage for contacts on the contacts that it sends. For Get Customer and Get Sales Order, APIcenter updates the contacts it got to this pipeline and stage after getting them; if you leave the fields empty, nothing is updated. Always fill in the pipeline and the stage together.

The pipeline that APIcenter filters on when getting data. Enter the name or ID of the pipeline in HubSpot; uppercase and lowercase letters do not matter. For Get Customer, APIcenter filters contacts on this pipeline; the default is contacts-lifecycle-pipeline, the lifecycle pipeline of contacts. For Get Sales Order, APIcenter only gets deals that are in this pipeline. If the pipeline or a stage cannot be found in HubSpot, the flow stops with an error message. This setting is required.

The deal stage that APIcenter filters on when getting data. Only deals in this stage are retrieved. Enter the name or ID of the stage in HubSpot; uppercase and lowercase letters do not matter. If you also set a pipeline in From what Pipeline do you want to retrieve deals, APIcenter searches for the stage in that pipeline. If you leave the pipeline empty, APIcenter searches for the stage in all pipelines and the flow stops with an error message if the stage exists in more than one pipeline. This setting is meant for deals.

This setting has no effect for HubSpot. For Get Sales Order, APIcenter only remembers which deals or invoices it already passed on, and skips them in a next run, even if the stage or status changed. You can leave it off (default).

Turns on URL encoding for values that APIcenter puts in the URL of a request to HubSpot. This prevents errors with special characters such as spaces, slashes or ampersands. In HubSpot, search values such as an e-mail address, SKU or deal name are in the content of the request and not in the URL; the URL only contains IDs and object types. So you rarely need this. This is the main switch: values are only encoded if you also turn on Enable URL Encoding of data in the endpoints of the source application (when getting) or Enable URL Encoding of data in the endpoints of the target application (when sending). Default: off.

Use administration mapping table

General flow setting

This setting has no effect for HubSpot. The data that APIcenter exchanges with HubSpot has no administration field, so there is nothing to map. Leave this setting off (default).

This setting has no effect for HubSpot, because the data that APIcenter exchanges with HubSpot has no administration field. Leave it as it is.

Notifications frequency

Notifications

Receive Notifications

Notifications

The pipeline for deals, as the name or ID of the pipeline in HubSpot (uppercase and lowercase letters do not matter). For Send Sales Order, this is the pipeline in which APIcenter creates the deal and in which it searches for an existing deal; default default. This is required. For Get Sales Order, APIcenter updates the deals it got to this pipeline and the related deal stage after getting them; if you leave the fields empty, nothing is updated. Always fill in the pipeline and the stage together.

The deal stage, as the name or ID of the stage in HubSpot (uppercase and lowercase letters do not matter). For Send Sales Order, this is the stage in which APIcenter creates the deal; default closedwon. This is required. For an existing deal, APIcenter updates the stage if Update order is on. For Get Sales Order, APIcenter updates the deals it got to this stage after getting them; if you leave the field empty, nothing is updated. This way you can give the deals you got another stage, so that they no longer match the filter on deal stage.

Decides if APIcenter also gets the data of the linked HubSpot product for each order line. For this, APIcenter gets the products of the order lines. If a line has no linked product, the line stays without product data and a note is added to the flow results. Default: on.

Decides if APIcenter creates a property or an option that does not exist in HubSpot. If this is off (default), the flow stops with an error message when a property or option is missing. If this is on, APIcenter creates the property or option in the group that you set. You can only add an option to a property that HubSpot has not locked; otherwise an error message follows.

Amount to process

Run behaviour

The maximum number of contacts, products or deals that APIcenter gets from HubSpot in each run. The default value is 10; you can choose a number from 1 up to and including 15. APIcenter gets the oldest changed records first. With a higher number, you clear a backlog faster, but each run takes longer.

Choose what APIcenter gets: Deals (default) or Invoices, the invoices of HubSpot. The default data mapping is based on deals, with dealname and dealstage among others. If you get invoices, check the Data mapping of the flow. For invoices, APIcenter uses the invoice number (hs_number) to identify the invoice in the activities.

The date and time from which APIcenter gets deals or invoices from HubSpot. APIcenter only gets records that changed after this moment, the oldest change first. After each run, APIcenter sets the date to the modification date of the last record it got. A deal or invoice that APIcenter already passed on is not passed on again. Default: 2025-01-01T00:00:00.

Last execution time

Run behaviour

In practice, this setting has no effect for HubSpot. The HubSpot flows ask for one list per run with their own limit (when getting data, this is Amount to process) and do not read extra pages. The default value is 20; you do not need to change it.

Offset

Run behaviour

This setting has no effect for HubSpot. Get Customer keeps track of where the flow stopped with the date from which contacts are retrieved, not with an offset. The default value is 0; you do not need to change it.

Run at specific times

Run behaviour

Use page size

Run behaviour

In practice, this setting has no effect for HubSpot. The HubSpot flows decide themselves how many records they ask for per request: when getting data, this is Amount to process. The default value is 50; you do not need to change it.

Still need help?

Ask the support assistant in your dashboard or create a support ticket.

Go to support