Integration

Zembula + HubSpot

HubSpot gives each contact a lifecycle stage, and Zembula can show content for that stage when the email opens.

It's our business to grow yours

Book a demo

Zembula has built this integration.

What Zembula can read from HubSpot

HubSpot keeps one record for each contact, and Zembula reads that record once you connect your HubSpot account with OAuth. A contact carries an email address, a first and last name, a lifecycle stage, a phone number, a job title, a city and a country. Zembula can find the contact by Record ID, by email address or by a custom unique property. Zembula can also read the definitions of your contact properties, custom ones included.

Lifecycle stage can choose between a welcome block and a win-back block. City can show items from nearby stores. HubSpot limits the pace of API calls. An OAuth app from the marketplace gets 110 requests every 10 seconds for each account that installs it, and CRM Search is excluded.

A private app on a Professional or Enterprise account gets 190 requests every 10 seconds. HubSpot also supports webhooks, with up to 1,000 webhook subscriptions for each app. Your email service provider supplies the lookup value as a merge tag in the image URL.

DataDetailLooked up by
Name and emailThe first name, last name and email address of a contact.Record ID, email, or a custom unique property
Lifecycle stageThe lifecycle stage of one contact.Record ID, email, or a custom unique property
City and countryWhere a contact lives.Record ID, email, or a custom unique property
Job title and phoneThe job title and phone number of a contact.Record ID, email, or a custom unique property
Contact property definitionsField definitions for contacts, custom ones included.property name

How the data arrives

  • API: Zembula reads a contact’s profile from HubSpot once you connect your account with OAuth.

What you need

  • Your HubSpot account, connected to Zembula with OAuth.
  • A contact lookup value in your email service provider, sent as a merge tag in the image URL.

Limits to plan for

LimitWhat it means
Marketplace OAuth apps: 110 requests every 10 seconds per installing account, excluding CRM Search.Keep open-time reads under this rate for each account.
Private apps on Professional or Enterprise: 190 requests per 10 seconds per app.Plan your open-time reads against this rate.

Ideas for email

  • Use lifecycle stage to pick a welcome or win-back product block.
  • Use city to show nearby-store items in an email.
  • Use the contact’s email as the lookup key to render per-person blocks at open.

Last checked: 19 November 2026.

Performance marketing dials, inside email. For the first time.

See how we do it by booking a demo.