All about HubSpot
HubSpot: Send payments to HubSpot
Put payment data, such as a payment status, on an existing deal or invoice in HubSpot.
Updated November 9, 2026
This flow puts payment data from another application on an existing deal or invoice in HubSpot, for example a payment status. The flow does not create a deal or invoice itself.
How it works
- With Do you want to update a payment property on the Deal or Invoice, you choose the HubSpot object: the Deal (default) or the Invoice.
- For a deal, APIcenter searches for the deal by the combination of pipeline, deal stage and deal name. The data must contain all three: the HubSpot properties
pipeline,dealstageanddealname. The pipeline and stage are their internal IDs, for exampledefaultandclosedwon. If one of the three is missing, or the deal is not found, the flow stops with an error message. - For an invoice, APIcenter searches for the invoice by the invoice number (
hs_number). - APIcenter writes the other fields from the data to the deal or invoice it found. You decide which HubSpot property this is under Data mapping.
- The default data mapping only links the reference to
dealname. Link the propertiespipelineanddealstageyourself, and the property that you want to update. - If a field cannot be mapped, Stop flow when mapping of fields fails decides if the flow stops or skips the field.
What you need first
- HubSpot is connected to APIcenter. See Connect HubSpot to APIcenter.
- The deal or invoice already exists in HubSpot, for example because Send sales orders to HubSpot created it.
- The property that you want to update exists in HubSpot and you linked it under Data mapping.
Tips
- Does APIcenter not find the deal? Check if the pipeline and the deal stage in the data are the internal IDs, and not the labels. Also check if the deal stage is still correct: APIcenter searches for the deal in the stage that is in the data.
- According to HubSpot, it can take a moment before new records appear in search results. A deal that you just created may therefore not be found for a short time.
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.
Stop flow when mapping of fields fails
Datamapper SettingsDecides what happens if a field in the data mapping cannot be mapped, for example because the value has the wrong type or format. If this is on (default), the flow stops with an error message in the activity log, so that nothing incomplete is passed on. If this is off, the flow continues and the field that could not be mapped is skipped; a note is added to the flow results. For HubSpot, this setting is available in the flow Send Payment.
Enable URL Encoding of data in the endpoints of the target application
General flow settingEnable URL encoding of data in endpoints
General flow settingTurns 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 settingThis 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).
What to do with a value that cannot be mapped using the mapping table
General flow settingThis setting has no effect for HubSpot, because the data that APIcenter exchanges with HubSpot has no administration field. Leave it as it is.
Notifications Email address
NotificationsNotifications frequency
NotificationsReceive Notifications
NotificationsChoose on which HubSpot object APIcenter puts the payment data: on the Deal (default) or on the Invoice. For a deal, APIcenter searches for the deal by the combination of pipeline, deal stage and deal name; so the data must contain all three, and the stage and pipeline are their internal IDs, for example closedwon and default. For an invoice, APIcenter searches for the invoice by the invoice number (hs_number). APIcenter writes the other fields from the Data mapping to the object it found. If the object is not found, the flow stops with an error message.