This guide shows how to connect Lemlist and Scribeless with Zapier so your sales team can add handwritten follow-up to the outreach moments already happening in Lemlist. The example below uses Zapier, but the same structure works in Make, Pipedream, n8n, or a direct API workflow if your team prefers another automation layer.

Before you build the Zap, create the campaign in Scribeless first. Scribeless is campaign-first: the automation should add a recipient to an existing campaign, not create a one-off send from scratch. Set the handwritten template, sender, envelope, landing page, QR code, and fulfilment rules in Scribeless, then use Zapier to decide who should enter that campaign and when.

The most common Lemlist to Scribeless workflow is:

This keeps handwritten mail tied to real sales intent. Instead of sending generic gifts or manual cards, you can use direct mail after moments such as meeting booked -> handwritten follow-up, opportunity stage change -> executive note, positive reply -> gift-like card, or sequence completed -> handwritten nudge.

You will need an active Lemlist workspace, an active Scribeless account, access to Zapier, and a Scribeless campaign that is ready to receive recipients. In Scribeless, confirm the campaign has the right region, handwriting style, message template, QR destination, and sender identity.

You should also decide what field in Lemlist represents the recipient's postal address. If your Lemlist records do not contain address data, add an enrichment step before Scribeless or use a CRM step to retrieve the mailing address from the contact or account record.

Start with a narrow trigger, add qualification logic, then send the recipient to Scribeless:

For B2B teams, the filter step matters. A handwritten note has more impact when it is reserved for accounts your sales motion values most: target accounts, active opportunities, high-fit buyers, expansion accounts, or prospects showing clear intent.

Create a new Zap and choose Lemlist as the trigger app. Pick the event that matches the sales moment you want to use. For most teams, campaign reply is the cleanest starting point because it turns a digital conversation into a physical follow-up.

Connect your Lemlist account, choose the campaign or lead event, then pull in a recent sample record. Review the sample carefully. You need at least the recipient name, company, email, and a mailing address or a reliable key that lets you look up the mailing address in another system.

Add a Zapier Filter step before Scribeless if only some Lemlist events should trigger direct mail. Common B2B filters include ABM campaign name, positive reply sentiment, meeting booked stage, minimum company size, or target account tier.

If timing matters, add a delay step. For example, send one business day after a meeting is booked, three days after a positive reply, or immediately after an opportunity moves into a high-value stage.

Zapier's own guides on filters and delays are useful if you want different paths for different reply types.

Add Scribeless as the action app and choose Add Recipients. Connect your Scribeless account and select the campaign you prepared earlier. This is where the campaign-first setup becomes important: the Zap should add the Lemlist lead to a named campaign that already controls the creative, sender, QR destination, and mailing settings.

Use one campaign per motion when possible: booked-meeting thank-you notes, opportunity-stage executive notes, or re-engagement after a sequence completes. That keeps reporting cleaner and makes message changes easier.

Map the Lemlist fields into Scribeless recipient fields. At minimum, include first name, last name, company, address line 1, city, state or region, postal code, country, and email. If your Scribeless template uses personalization variables, map those too.

Useful variables include company name, rep name, meeting date, campaign name, pain point, or account tier. Keep the handwritten message short and specific.

For example, after a positive reply you might map a variable such as reply_topic into the Scribeless template. After a meeting is booked, map meeting_date and rep_name. After a stage change, map the opportunity owner and account name. Zapier's guide to mapping fields between steps explains how dynamic fields are passed into later actions.

If your Scribeless campaign uses QR codes or tracked landing pages, decide how the sales team should respond when someone engages. A QR scan can be a strong buying signal because the recipient moved from physical mail into a digital journey.

There are two common follow-up patterns: pause the Lemlist campaign when a high-value recipient scans the QR code, or tag the lead in Lemlist so the account appears in a rep's priority workflow.

If Zapier supports the needed Scribeless trigger, create a second Zap from Scribeless engagement to Lemlist. Otherwise, use the Scribeless API or your CRM as the return path. The goal is the same: make offline engagement visible to the team running the sales motion.

Before turning on the Zap, test with an internal contact or a non-customer test record. Confirm the right Scribeless campaign is selected, address fields are complete, variables render correctly, and the recipient does not already exist in the campaign.

Then check the live Scribeless campaign queue before enabling the Zap for all Lemlist activity. For the first week, review a few sends to confirm the trigger and filters are producing the right audience. Once stable, the automation can keep handwritten follow-up running while reps focus on accounts showing real intent.