Skip to the operations

CRM

HubSpot in a decision flow.

2 HubSpot operations a decision flow can call directly, with the credentials your own contract issued. The response is data the rest of the flow reads, branches on, and keeps in the trace.

Category
CRM
Type
Integration
Authentication
API key
Test environment
Production host only

Who they are

CRM, marketing and sales software for growing companies.

HubSpot is a CRM platform: contacts, companies, deals and the marketing and support tooling around them. In a decision it is usually the destination rather than the source — the place a commercial team already works, and where an outcome has to appear before anyone acts on it.

What a flow can call

2 operations, each one a step you can place on the canvas.

  1. POST/crm/v3/objects/contacts

    Create or update a CRM contact

    Creates a HubSpot contact for an application workflow.

  2. GET/crm/v3/objects/contacts

    List CRM contacts

    Lists contacts visible to the token. Use limit, after and properties query parameters on the node to keep the response bounded.

Where it sits in the decision

CRM calls have a natural place in a flow.

Writing the outcome back closes the loop with the commercial team, so the record they work from carries the same verdict the customer received rather than a copy that drifts.

Whatever HubSpot returns is part of the run, so it is part of the record. When someone asks months later why an applicant was declined, the answer cites what came back at the time rather than re-fetching from a service whose answer has since changed.

  • 01Add HubSpot as a connection authenticating with an API key.
  • 02HubSpot has one host for both environments, so guard test runs with your own credentials and limits.
  • 03Place a Connection node and pick an operation — “Create or update a CRM contact” is usually the first one a flow needs.
  • 04Map the response into the fields your rules read, then test the whole path before it carries live traffic.

Common questions

Using HubSpot in a flow.

How do I connect HubSpot to a decision flow?

Add HubSpot as a connection in your workspace authenticating with an API key, with the credentials your own contract issued — ArboRule calls the provider as you, and never holds a contract on your behalf. Once the connection exists, any flow in the workspace can place a Connection node and choose one of its operations. The credentials live on the connection, not in the flow, so a policy owner can use HubSpot in a decision without ever seeing the secret.

Can I test HubSpot without touching production?

HubSpot exposes one host for both environments, so there is no separate sandbox to point at. Test runs still execute in Sandbox and are recorded separately in decision history, but the call goes to the same place as production — so guard it with your own test credentials, rate limits, or data.

What can a flow call on HubSpot?

2 operations: “Create or update a CRM contact”, “List CRM contacts”. Each one is a step you place on the canvas and map into the fields your rules read, and most flows start with “Create or update a CRM contact”. The list comes from the same manifest the engine uses to make the call, so this page cannot describe an operation the product does not have.

Where in a decision should HubSpot be called?

Writing the outcome back closes the loop with the commercial team, so the record they work from carries the same verdict the customer received rather than a copy that drifts.

Also in CRM

Ready when you are

Wire HubSpot into a real decision.

Build the flow in Sandbox, connect your account, and watch the decision pull what it needs before it answers.

Read the docs