HubSpot workflows are powerful, but they stop at your HubSpot data. The Custom API Workflow Action bridges that gap by letting you send HTTP requests to any external API directly from a workflow step, no code, no middleware, no Zapier required.

⭐ What it does

Add a Custom API Call step to any HubSpot workflow. When the workflow runs, it sends an HTTP request to the endpoint you configure, and returns the response back into the workflow as output fields you can use in subsequent steps.

Supports all standard HTTP methods: GET, POST, PUT, PATCH, DELETE.

⭐ Flexible authentication

Configure per-action authentication without storing credentials in HubSpot properties:

- Bearer token — for APIs using OAuth or JWT

- API key header — for APIs using a custom header like `X-Api-Key`

- HTTP Basic auth — for APIs requiring username and password

- None — for open or IP-whitelisted endpoints

⭐ Dynamic requests

Use HubSpot workflow tokens in the URL, request body, headers, and query parameters to build requests that include live contact, deal, or company data at the time the workflow runs.

⭐ Act on the response

Every API call returns four output fields: 'status_code ', 'response_body ', 'success ', and 'error_message ' that you can use in downstream workflow steps. Branch your workflow on success or failure, store the response to a property, or pass it into another API call.

⭐ Who it's for

Any HubSpot user who wants to connect their workflows to external systems without building a custom integration. Ideal for developers, RevOps teams, and agencies managing complex automation stacks.