Build the Cargo tool
The HubSpot action does not map fields. Cargo always sends a fixed payload from the enrolled record. The tool’s start node must includeid (the HubSpot record id). The other keys below are sent when present and may be declared on the start node, but they are not required for the tool to appear in the dropdown.
Contact workflows send:
Company workflows send:
Use a contact-shaped start node for contact workflows and a company-shaped start node for company workflows. Extra HubSpot properties are not included. Only deployed tools whose start node includes
id appear in the HubSpot dropdown.
Run a Cargo tool from a HubSpot workflow
- Deploy the tool in Cargo with the start-node fields above.
- In HubSpot, create a contact or company workflow.
- Add the Run Cargo tool action and pick the tool.
runUuid, status, and a string output for later workflow steps.
Reconnect the HubSpot connector in Cargo so Professional and Enterprise portals can grant the optional automation scope. Without that scope, HubSpot waits until the action times out instead of receiving the run results. Free and Starter portals can still connect HubSpot; they cannot complete that callback.
