Docs

Webhooks

Send records to LettrLabs from your own systems, and act on each one.

Who can use this: Core plan or higher. Any role. Needs: A system that can send an HTTP POST request with a JSON body.

Overview

A webhook is a URL that your own system sends records to. LettrLabs then does an action with each record, for example it mails the person in the record.

You can use webhooks to:

  • Mail each new lead or sold job that your system sends.
  • Mail the homes near each address that your system sends.
  • Choose which records mail, with filters.
  • See each record that arrived, and what LettrLabs did with it.

A webhook has two parts, and you set them up in two places:

  1. The webhook receives the records. You create it in Integrations > Webhooks.
  2. The action tells LettrLabs what to do with each record. You choose it when you make an automated campaign in Send Mail. A webhook campaign needs the Premium plan to turn on.

One webhook can feed more than one campaign. Each campaign that uses the webhook reads each record.

The webhook pages

The table lists each part of the webhook setup, and where it is in the app.

PageWhat it doesWhere it is in the app
Set up a webhookCreates the URL, and protects it with an API key or a signature.Integrations > Webhooks
Mail to recipientsMails the person in each record.Send Mail > My Data and Integrations > My System Sends Them > Webhook
Radius MailMails the homes near the address in each record.Send Mail > Map-Based Search > Radius Mail > Addresses My System Sends > Webhook
Fields and filtersMatches the record to the mail fields, and chooses which records mail.The Audience step of Send Mail
Webhook historyShows each record that arrived, and each action run.Integrations > Webhooks > History, and Attribution Data
Attribution webhooksCounts a sale or a lead.Not available yet
CRM recipesSends the records of HubSpot, JobNimbus and other CRMs.The settings of your CRM

How a webhook works

  1. Your system sends a record to the webhook URL as JSON.
  2. LettrLabs checks the API key or the signature, when the webhook asks for one.
  3. LettrLabs keeps the record as an event. A webhook in Test mode stops here, and no mail goes out.
  4. Each active campaign that uses the webhook reads the record. A campaign skips the record when a filter does not match.
  5. The History tab shows each event, its status and the action runs.

Before you begin

  • Your system must send an HTTP POST request with a JSON body.
  • A person who can change that system must add the webhook URL to it.
  • Send one test record before you make the campaign. The field mapping reads the fields of the records that the webhook received.

FAQ

Steps checked 2026-11-16.

On this page