Integration

Zembula + Hootsuite

Hootsuite Amplify holds the posts that your employees share, and Zembula reads that content for your emails. Zembula gets its access token from Hootsuite with an account id that you store.

It's our business to grow yours

Book a demo

Zembula has built this integration.

What Zembula can read from Hootsuite

Hootsuite holds social publishing and employee advocacy data, and Zembula reads Amplify content, the posts that your employees share for your brand. It asks Hootsuite for an access token for the account id that you store. Then it reads the content from the Hootsuite platform API, so an email can show the current Amplify content when a person opens it. Zembula can also read the social profiles that a member has connected.

It can read the organizations that the member belongs to. Each profile and each organization has its own id. Hootsuite can also send message events by webhook. A message event reports the state of a scheduled social post, with the organization, the message and a timestamp.

Hootsuite holds social data, so the data here is brand and team content, not data about the person who opens the email. Your team signs in with OAuth2. Hootsuite limits calls to 20 requests each second and 100,000 calls each day.

DataDetailLooked up byHow fresh
Amplify contentEmployee advocacy content from Hootsuite Amplify.set at setupopen time
Social profileA social account that a member has connected.social profile idopen time
OrganizationAn organization that a member belongs to.organization idopen time
Message stateThe state of a scheduled social post, sent by webhook.message idset at setup

How the data arrives

  • API: Zembula requests an access token for your stored account id. It then reads Amplify content from the Hootsuite platform API.
  • Webhook: Hootsuite sends message events. Each event holds the state, the organization, the message and a timestamp.

What you need

  • A Hootsuite member and a Hootsuite Developer account.
  • OAuth2 access, with your Hootsuite account id stored in Zembula.
  • A lookup value in your email service provider, sent as a merge tag in the image URL.

Limits to plan for

LimitWhat it means
20 requests per second and 100,000 calls per day.Calls above these caps are rate limited.
Inbox CRM webhooks need an Advanced Plan.Without that plan, Inbox CRM webhooks are not available.

Ideas for email

  • Feature fresh Amplify content in an employee advocacy email.
  • Link a connected social profile in the footer of a brand email.
  • Show the state of a scheduled social post in a team status email.

Last checked: 19 November 2026.

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

See how we do it by booking a demo.