Engagements
      Back to home
      1. Help Center
      2. Engagements

      What is a Webhook?

      Using Webhooks to Send Information in Journeys

      What Is a Webhook (and Why Should You Care)?

      A webhook is like an automatic notification that WeGive can send to another system (like Salesforce, Zapier, Google Sheets, or a mailing service) when something important happens — like when someone makes a donation.

      Think of it like this:

      "When this happens in WeGive, tell that other tool about it, instantly."

      You don't need to be a developer to use webhooks. If you're trying to get donor info into another system automatically, webhooks can save tons of time and reduce manual work.

      Real-World Examples

      • Send new donation details to a spreadsheet

      • Create a lead in Salesforce when someone donates

      • Trigger a thank-you letter in Lob or another mail service

      Step-by-Step: How to Use Webhooks in a WeGive Journey

      Step 1: Identify What You Want to Happen

      Ask yourself:

      • What action do I want to respond to? (e.g., a donation, a form submission, a ticket purchase)

      • What system do I want to send the data to? (e.g., Salesforce, Zapier, a mail service like Lob)

      Step 2: Go to the Journey Builder

      • Navigate to Journeys in WeGive

      • Choose an existing journey or create a new one

      Step 3: Add a Trigger

      Choose a trigger like:

      • "Donation Completed"

      • "Form Submitted"

      • "Recurring Gift Started"

      Step 4: Add an Action: Webhook

      • Click + Add Action after your trigger

      • Select Send Webhook

      Step 5: Fill in the Webhook Details

      Here’s what you’ll see and what to put in each section:

      1. URL Destination

      • This is the web address where the data should go

      • Example for Zapier: https://hooks.zapier.com/hooks/catch/123456/abcde

      • If you're using a service like Lob or Salesforce, they may provide you with a custom URL

      2. Headers (optional)

      • Use this if the receiving system requires authentication (like an API key)

      • Example:

        • Key: Authorization

        • Value: Bearer YOUR_API_KEY (or Basic ENCODED_KEY, depending on the system)

      3. Content Type

      • Leave it as JSON unless told otherwise

      4. Body

      • This is the actual data being sent. You can use WeGive tokens (like mail merge fields) here.

      • Example:

      {
        "full_name": "donor_full_name",
        "email": "{{donor_preferrred_email}}",
        "amount": "{{last_donated_amount}}",
        "date": "{{donor_last_donated_date}"
      }

      These tokens will be automatically replaced with real information when the webhook is triggered.

      Step 6: Test the Webhook (Recommended)

      • If you’re using a test tool like Webhook.site, you can paste the test URL to see what the data looks like when it’s sent

      • Great way to confirm it's working before sending real donor data

      Step 7: Save and Activate Your Journey

      • Once you're happy with how it’s set up, turn your journey ON

      • WeGive will now automatically send webhook data when the trigger happens

      Tips for Success

      • Use Zapier if you're not sure where to send data — it's beginner-friendly and connects with thousands of tools

      • Make sure any sensitive data is being sent securely (use headers and HTTPS URLs)

      • Test before going live!