SendBeam

Integrations · Apps you already use

SendBeam and Notion

Add people from a Notion database to SendBeam: a new page with an email becomes a contact.

Notion databases are used as simple CRMs, waitlists and member directories. Connecting one to SendBeam adds each new entry as a contact, so a person added in Notion can get a welcome email without anyone copying the address across.

Native integration: no

SendBeam has no Notion 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 Notion 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 Notion and SendBeam, run the workflow once with your own address, and check the result before switching it on.

Code

In n8n: Notion to SendBeam

n8n workflow 
1. Notion Trigger, with the event Page Added to Database
2. SendBeam → Contact → Create or update
     Email       the email property from step 1
     First name  the first name, if there is one
     Source      notion
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: Notion to the REST API

Make scenario 
Module 1: the Notion module that watches a database for new items
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": "notion"
}

Replace {{1.email}} and {{1.first_name}} with the email property 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: Notion to the REST API

Zap 
Trigger  Notion → New Data Source Item
Action   Webhooks by Zapier → POST
URL           https://sendbeam.io/api/v1/contacts
Payload type  json
Data
  email       the email property
  first_name  the first name
  source      notion
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

  • Give the Notion integration access to the database first (Share → Connections in Notion), or the trigger sees nothing.
  • Use an Email property type for the address so it maps cleanly.
  • 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

  • Airtable — Keep SendBeam in step with an Airtable base: each new record with an email becomes a contact.
  • Google Sheets — Add each new row of a Google Sheet to SendBeam as a contact — handy for lists people still keep in a spreadsheet.
  • Tally — Send Tally form submissions to SendBeam as contacts, using Tally's own webhooks or an automation tool.

Also: Astro, Next.js, Hugo, Eleventy, WordPress, Cloudflare Pages, Netlify, Vercel, Zapier, Make, n8n, Typeform, Jotform, Stripe, Shopify, Gumroad, Lemon Squeezy, Calendly, Eventbrite, Webflow, HubSpot, Slack.