Skip to main content
If HubSpot is your source of truth for customer data, this guide gets forms, emails, and site events from Hiveku flowing in — and HubSpot updates flowing back out.

Via Zapier

Easiest. No code. Uses the built-in HubSpot + webhook connectors.

Via HubSpot API

More control. Requires a HubSpot Private App token.
See Connect Zapier for the full setup. HubSpot is one of Zapier’s best-supported integrations — you can create contacts, update deals, log calls, and trigger HubSpot workflows in minutes.Use this path when:
  • You don’t want to manage API tokens
  • Volume is under a few thousand events per month
  • You need simple field mapping, not complex transforms

​
Reverse Direction: HubSpot → Hiveku

For keeping your site or app in sync when something changes in HubSpot:
1

Create a HubSpot workflow

In HubSpot, go to Automation > Workflows. Create a new workflow with whatever trigger matters (contact created, deal stage changed, etc.).
2

Add a Webhook action

Point it at a Hiveku workflow webhook URL.
3

Handle the payload in Hiveku

Your Hiveku workflow receives the HubSpot event and can update your database, send an email, or update the UI.

​
Sync Frequency

  • Real-time via webhooks — best for user-facing updates
  • Periodic batch — every 15 minutes via a scheduled workflow, good for backfills or bulk updates
Never write to HubSpot from a workflow that was triggered by HubSpot. That creates a feedback loop — contact updated in HubSpot → webhook → Hiveku workflow → API write back to HubSpot → webhook fires again → infinite loop. Add a flag to skip re-syncs on HubSpot-originated events.
If you already use HubSpot’s native Workflows for automation, keep them there. Use Hiveku Workflows only for things HubSpot can’t do — like updating your site content or triggering a deploy.

​
Common Patterns

See Webhook Patterns for standard integration recipes like retries, idempotency, and signature verification.

​
Verify It Worked

  1. Submit a test form on your site
  2. Check the Workflows > Runs tab — the run should show a 201 from HubSpot
  3. In HubSpot, search contacts for the test email — the contact should appear with the right properties

​
Troubleshooting

The token is wrong, expired, or missing scopes. In HubSpot, go to Settings > Integrations > Private Apps, open your app, confirm the token matches what’s in HUBSPOT_API_KEY. If unsure, regenerate the token and update the env var.
HubSpot deduplicates contacts by email automatically — a POST with an existing email updates rather than creates. If you’re seeing dupes, emails are probably different (trailing whitespace, mixed case). Normalize emails before the API call.
HubSpot uses camelCase internal names that don’t match the UI labels. “First Name” in the UI is firstname (all lowercase, no underscore) in the API. Check Settings > Properties in HubSpot for the exact internal name.
HubSpot standard tier limits you to 100 requests per 10 seconds. Batch writes with the /batch/create endpoint (up to 100 contacts per call), or add retry-with-backoff on 429s.
In HubSpot, open the workflow and check the History tab — is the trigger actually matching? HubSpot Workflows have strict entry criteria. If they’re not firing, test by manually enrolling a contact and watching the history.

​
What’s Next?

Webhook Patterns

Retries, idempotency, and signature verification

CRM Contacts

Manage contacts inside Hiveku alongside HubSpot