WeGive connects to LettrLabs through Zapier. If you haven't set up the LettrLabs side of Zapier yet, start with Setup Guide: Zapier first; this guide picks up from there and focuses on the WeGive-specific pieces.
Before you start
A LettrLabs API key and an Integration Order created for Zapier (see Setup Guide: Zapier, Steps 1–2, if you haven't done this yet).
A WeGive user with access to Settings > API, to generate the API key Zapier will use to connect to WeGive.
Knowing which WeGive event should trigger the mailing — New Donor and New Transaction are the two most common starting points.
Step 1: Generate a WeGive API key for Zapier
In WeGive, go to Settings, then open the API tab.
Note your Organization ID, shown at the top left — some integrations ask for this alongside the API key.
Click Create New API Key, then copy the key immediately — WeGive only shows it once, and only supports one active API key at a time. If you lose it, you'll need to generate a new one.
Step 2: Connect WeGive inside Zapier
In Zapier, go to My Apps and click Add connection.
Search for WeGive and select it.
Paste in the API key (and Organization ID, if prompted) you copied in Step 1, and click through to authorize.
Once connected, this WeGive account is available to any future Zap.
You can also reach Zapier directly from inside WeGive: go to Data > Integrations > Zapier in the left menu, which links out to WeGive's Zapier app page.
Step 3: Choose your WeGive trigger
Pick the WeGive event that should kick off the mailing — most nonprofits start with a new donor or a new transaction event. The exact trigger names available depend on your WeGive plan and Zapier app version, so check the trigger list Zapier shows for your connected WeGive account before building the rest of the Zap.
Step 4: Add a LettrLabs action
Add Recipient to Integration Order — sends the donor's name and mailing address into your Integration Order. This is the right choice for donor-facing thank-you mail.
Mail Recipients Around an Address (Radius Mail) — sends a batch of neighbors around an address rather than mailing the donor directly. Less common for donor thank-yous, but useful for prospecting campaigns near an event or program site.
Add Recipient to Address Book — for building a reusable list rather than an immediate send.
Step 5: Map your WeGive fields
Map the donor's first and last name and their full mailing address onto LettrLabs' recipient fields. If you want to personalize the letter with gift details, also map transaction amount and date.
Step 6: Filter in Zapier, not in WeGive (for most cases)
Keep the WeGive trigger itself broad, and add a Filter by Zapier step right after the trigger to gate exactly when the mailing should continue — for example, only continue if gift amount is above a threshold, or frequency equals a specific value.
The one exception is a numeric comparison on transaction amount: some Zapier filter conditions compare values as text depending on how WeGive's trigger exposes the field, so if a "greater than" filter on amount behaves unexpectedly, check whether WeGive's trigger sends amount as a number or as text, and adjust your filter step (or, if needed, use a Formatter by Zapier step to convert it to a number first).
Step 7: Test, then go live
Run Zapier's test step and confirm the sample recipient shows up correctly in LettrLabs.
Publish the Zap.
In LettrLabs, switch the Integration Order to Active.
Want help picking your first WeGive trigger, or deciding between Zapier and a native webhook? Reach out to our team.