ActionHubSpot workflow action

Call any REST API
from a workflow.

POST, GET, PUT, PATCH, or DELETE to any REST API inside a HubSpot workflow. Use personalization tokens in the URL, headers, and body — then map the response back to a property and branch on the result. No code.

Install on HubSpot Marketplace See workflow examples

Free trial · Works on every HubSpot tier with workflows · Built by a HubSpot Solutions Partner

Score & route demo requestsLive example

Trigger · enrolls contacts

When this happens

Form submission: Demo Request

any number of times anytime

Action 1

API Webhook Connector

POST to /leads/score, save lead_score & account_id

Hide configuration

MethodPOST

URLapi.acme.io/leads/score

HeaderAuthorization: Bearer •••

Body{ email, domain }

Saveresponse.lead_score → lead_score

Action 2

Branch

Check branches in order, route on score

Score ≥ 80Score 40–79None met

End

Three things that matter

Built for the work HubSpot workflows already do.

RevOps and admins increasingly need to call external APIs from inside a workflow — to score a lead, enrich a contact, push to Clay or n8n, or open a Zendesk ticket.

Workflow-native, not bolted on

Configured inside HubSpot's workflow editor. Optional Toolbox dashboard for testing, replay, and debugging. No separate platform, no JavaScript to maintain.

Response data flows back

Map any path in the response JSON to a HubSpot property, then branch the workflow on what came back. Most webhook tools fire and forget.

Logged where you debug

Outputs land in HubSpot's standard workflow execution history. Full redacted request/response details in the Toolbox History tab.

Use case 01 · Lead routing

Route, score, and qualify through any API

Most teams have an internal service that knows things HubSpot doesn't — product usage, account tier, fraud signals, routing rules. Pipe the lead through it, save the response, and route the contact based on what came back. All in one workflow, in real time.

Lead scoring and qualification
Customer 360 lookups
Fraud and abuse signals

Score & route demo requestsEnrolls contacts

Trigger · enrolls contacts

When this happens

Form submission: Demo Request

any number of times anytime

Action 1

API Webhook Connector

POST to /leads/score, save score & tier

Click to see configuration

MethodPOST

URLinternal.api/leads/score

Saveresponse.score → lead_score

Action 2

Branch

Route AE / SDR / nurture

≥ 80 → AE40–79 → SDRNone met

End

Use case 02 · Zapier, Make, n8n

An instant trigger for Zapier, Make, or n8n

Zapier's native HubSpot trigger polls every 1–15 minutes. The API Webhook Connector pushes events to a Catch Hook in sub-second time, with a payload you control completely. Treat HubSpot as the source of truth and let middleware handle only the downstream side.

Sub-second event delivery
Custom payload shape — no oversized payloads
Lower middleware spend

Push on new customerEnrolls contacts

Trigger · enrolls contacts

When this happens

Lifecycle stage = Customer

any number of times anytime

Action 1

API Webhook Connector

POST to Zapier Catch Hook with payload

Click to see configuration

MethodPOST

URLhooks.zapier.com/•••

Body{ contact, deal, mrr }

End

Use case 03 · Clay enrichment

Send leads to Clay the moment they enter

Clay enrichment works best on fresh signal. Fire a POST to your Clay webhook the second a contact is created or a form is submitted. Enriched data flows back into HubSpot as a property update on the next step — no polling delay.

Real-time enrichment before the SDR sees the lead
Controlled payload — only the fields Clay needs
Branch on the enrichment result

Enrich in Clay before outreachEnrolls contacts

Trigger · enrolls contacts

When this happens

Form submission: Demo Request

any number of times anytime

Action 1

API Webhook Connector

POST to Clay webhook source

Click to see configuration

MethodPOST

URLapi.clay.com/•••

Body{ email, company }

End

Use case 04 · Zendesk tickets

Open Zendesk tickets directly from a workflow

Most teams route HubSpot signals to Zendesk through Zapier or Make. Hit Zendesk's Tickets API directly, with subject, body, requester, priority, and tags built from HubSpot tokens. The new ticket ID comes back and stores on the contact.

Priority support → ticket tagged for the right group
Closed-won → onboarding ticket for implementation
Health drop → ticket for the CSM

Open a Zendesk ticketEnrolls contacts

Trigger · enrolls contacts

When this happens

Form: Priority support request

any number of times anytime

Action 1

API Webhook Connector

POST to Zendesk Tickets API

Click to see configuration

MethodPOST

URLacme.zendesk.com/api/v2/tickets

AuthBasic / OAuth bearer

Action 2

Set property value

Save Zendesk ticket ID to the contact

End

Use case 05 · HubSpot → HubSpot

Call HubSpot APIs the editor doesn't expose

The workflow builder can update the enrolled record. It can't re-trigger form enrollments, modify related records, touch custom-object associations, or reach most User fields. Pass a Private App token and POST the resource you need.

Re-enroll in form-triggered workflows
Update parent company from a contact
Modify line items on closed-won deals
Touch custom objects and associations

Re-enroll via Forms APIEnrolls contacts

Trigger · enrolls contacts

When this happens

Lead source = Imported / external

any number of times anytime

Action 1

API Webhook Connector

POST to HubSpot Forms API to simulate a submission

Click to see configuration

MethodPOST

URLapi.hubapi.com/forms/•••

AuthPrivate App token (forms)

End

More patterns

Anything reachable over HTTP fits a workflow now.

Six more patterns teams ship in their first month with the API Webhook Connector.

AI and LLM APIs

Call OpenAI, Anthropic Claude, or your own gateway. Classify leads, generate emails, summarize notes, score intent.

Email & phone validation

Send submissions to NeverBounce, ZeroBounce, or Twilio Lookup. Branch on validity and block junk before it pollutes the CRM.

Sync to data warehouses

POST CRM events to Snowflake, BigQuery, Postgres, or Segment in real time. Skip the daily export job.

Cross-CRM sync

Push contact, deal, or ticket changes to Salesforce, Pipedrive, or Close the moment a HubSpot record changes.

Real-time notifications

Hit Slack, Teams, Discord, or Telegram with a custom message when high-value records change state.

Document & signing flows

Trigger DocuSign, PandaDoc, or HelloSign when a deal advances. Capture the document ID back on the deal.

Capabilities

Everything you'd build for production, in a workflow step.

Configured entirely through the standard HubSpot workflow editor. No script editor, no deploy step.

Five HTTP methods

POST, GET, PUT, PATCH, DELETE — for REST APIs, RPC endpoints, and webhook receivers.

Custom headers

Authorization bearer tokens, API keys, X-Signature, or custom routing. Content-Type is set automatically.

JSON body with tokens

Build the request body with HubSpot personalization tokens from the enrolled record and any associated object.

Response mapping

Map any path in the response JSON to a property. response.score, response.user.id all work.

Branching on result

Pipe HTTP status and result variables into HubSpot's branch action. Route success and error paths.

Audit log of every call

Every request and response is captured in workflow execution history for debugging and compliance.

FAQ

Common questions about HubSpot webhooks.

Quick answers to what teams ask before installing.

Does it require Operations Hub Pro?

No. The API Webhook Connector works on every HubSpot tier that includes workflows — Marketing, Sales, and Service Hub Professional, and any Enterprise tier. You don't need Operations Hub.

Which HTTP methods are supported?

POST, GET, PUT, PATCH, and DELETE. Each request accepts custom headers and a custom JSON body. HubSpot personalization tokens can be embedded anywhere in the URL, headers, or body.

Can the response update CRM properties?

Yes. Map any path in the response JSON to a HubSpot property using the Result variable fields — response.lead_score, response.user.account_id, and similar all work. Several paths can be saved per call.

Can I call HubSpot APIs from a HubSpot workflow?

Yes — and this unlocks updates the native editor can't perform: modifying associated records, line items, custom-object relationships, or ticket pipelines from contact context. Authenticate with a Private App access token.

What happens if the API call fails?

The action records the response status and body in workflow history. Downstream branches can route on success or failure status codes, or on the content of the response variable.

Is there a free trial?

Yes. The free 0CodeTools trial includes the API Webhook Connector with a monthly call quota generous enough for most teams to evaluate. Paid plans extend the quota.

Built for the work HubSpot workflows already do.

Workflow-native, not bolted on

Response data flows back

Logged where you debug

Route, score, and qualify through any API

An instant trigger for Zapier, Make, or n8n

Send leads to Clay the moment they enter

Open Zendesk tickets directly from a workflow

Call HubSpot APIs the editor doesn't expose

Anything reachable over HTTP fits a workflow now.

AI and LLM APIs

Email & phone validation

Sync to data warehouses

Cross-CRM sync

Real-time notifications

Document & signing flows

Everything you'd build for production, in a workflow step.

Five HTTP methods

Custom headers

JSON body with tokens

Response mapping

Branching on result

Audit log of every call

Common questions about HubSpot webhooks.

Add it to your workflows in 60 seconds.