SendBeam

Integrations · Apps you already use

SendBeam and HubSpot

Add new HubSpot contacts to SendBeam, so your CRM and your newsletter share one list of people.

Teams that keep their pipeline in HubSpot often send their newsletter somewhere simpler. Connecting HubSpot to SendBeam adds each new HubSpot contact to SendBeam, so the two stay in step without exports.

Native integration: no

SendBeam has no HubSpot app of its own. The routes below connect the two through n8n, Make or Zapier today, with the SendBeam node in n8n doing the SendBeam side for you.

How it works

  1. Pick your automation tool. n8n with the official SendBeam node, Make or Zapier. Each connects to HubSpot with its own trigger, shown below.
  2. Create an API key. Settings → API keys in SendBeam, with contacts:write, and lists:write if the workflow adds people to a list. The full key is shown once. To send SendBeam events out instead, add an endpoint under Settings → Webhooks.
  3. Map the fields and test. Map the fields between HubSpot and SendBeam, run the workflow once with your own address, and check the result before switching it on.

Code

In n8n: HubSpot to SendBeam

n8n workflow
1. HubSpot Trigger, with the contact created event
2. SendBeam → Contact → Create or update
     Email       the contact's email from step 1
     First name  the first name, if there is one
     Source      hubspot
3. SendBeam → Contact → Add to list
     Contact     By email, the same expression as step 2
     List        From list, then pick the list by name

Install the SendBeam node from Settings → Community nodes (n8n-nodes-sendbeam). Adding someone who is already a contact, or already on the list, succeeds, so the workflow is safe to re-run.

In Make: HubSpot to the REST API

Make scenario
Module 1: the HubSpot module that watches for new contacts
Module 2: HTTP → Make a request
URL:          https://sendbeam.io/api/v1/contacts
Method:       POST
Headers:      x-api-key = sb_live_XXXXXXXX_YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY
Body type:    Raw
Content type: JSON (application/json)
Request content:
{
  "email": "{{1.email}}",
  "first_name": "{{1.first_name}}",
  "source": "hubspot"
}

Replace {{1.email}} and {{1.first_name}} with the contact's email and the name, mapped from module 1. A 409 answer means the contact already exists; route it to GET /api/v1/contacts?q= with the same address if you need the contact's id.

In Zapier: HubSpot to the REST API

Zap
Trigger  HubSpot → New Contact
Action   Webhooks by Zapier → POST
URL           https://sendbeam.io/api/v1/contacts
Payload type  json
Data
  email       the contact's email
  first_name  the first name
  source      hubspot
Headers
  x-api-key   sb_live_XXXXXXXX_YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY

Webhooks by Zapier is available on Zapier's paid plans. The SendBeam app for Zapier will replace this step with a Create Contact action once it is listed in Zapier's directory.

Things to know

  • n8n's HubSpot Trigger needs a HubSpot developer app; Zapier and Make connect with an ordinary HubSpot login.
  • Map HubSpot's lifecycle stage into a SendBeam custom field or tag if you segment by it.
  • Only add people to a marketing list if they agreed to hear from you. Someone who only bought or booked can still get receipts and reminders through Send transactional.

Go further

Also: Astro, Next.js, Hugo, Eleventy, WordPress, Cloudflare Pages, Netlify, Vercel, Zapier, Make, n8n, Typeform, Tally, Jotform, Google Sheets, Notion, Shopify, Gumroad, Lemon Squeezy, Eventbrite, Webflow, Slack.