Using the Webhook Action in Automations

Using the Webhook Action in Automations

We’ve added a new Webhook action to the Automation engine, allowing workflows to send HTTP requests to external endpoints with customizable payloads, headers, and authentication methods.

Using the Webhook Action in Automations

What’s a Webhook?

Think of a webhook as a digital messenger. When something happens in Lendware (like a new loan created or a contact updated), the webhook can instantly send that information to another system — no exporting, no waiting.

This lets you:

  • Share data automatically → Push borrower or contact info to another platform.

  • Kick off other processes → Trigger tasks in tools like Zapier or Slack.

  • Feed your reporting tools → Send real-time updates into dashboards or custom apps.

⚡ Note: Webhooks can only be used inside Workflows (Contact-based or Transaction-based).

Why This Matters

Webhooks connect Lendware to the rest of your tech stack in real time. Instead of re-typing or syncing data by hand, they do the heavy lifting for you — saving time, cutting down on mistakes, and keeping your systems in sync.

Before You Start

While setting up a webhook is pretty simple, you might need help from your technical team if:

  • The system you’re connecting to needs special logins (API keys, OAuth, etc.).

  • You’re sending data in a very specific format (JSON).

  • You see errors like 400 or 422 when testing.

  • You’re working with an internal or custom-built app.

💡 Tip: Share this article with your IT or dev team — they’ll know exactly what endpoint, headers, and format are required.

How to Set Up a Webhook

1. Open Your Workflow

  • Go to Automations → Workflows.

  • Create a new workflow or edit an existing one.

2. Add the Webhook Action

  • Select Webhook from the list of available actions.

  • Every time the workflow runs, this webhook will fire.

3. Configure Your Webhook

  • Webhook URL: The system you want to send data to (example: https://api.example.com/webhook).

  • HTTP Method: How you send the data. Most often this is POST.

  • Headers: Extra info some systems need, like an API key. Example:

     
    Header name: Authorization
    Header value: Bearer your_api_key

  • Body (JSON Payload): The actual data you’re sending. You can insert merge fields to include live Lendware values. Example:

     
    {
    "contactName": " ",
    "email": "",
    "loanId": ""
    }

  • Timeout: Default is 30 seconds. Increase if your endpoint needs longer to respond.

4. Test Your Webhook

  • Click Test Webhook to send a sample.

  • Check that your endpoint receives it.

  • Once it looks good, click Save.

Common Pitfalls (and How to Avoid Them)

  • ✅ Always put a space after the colon
    "firstName": ""
    ❌ Don’t do → "firstName":""

  • ✅ Wrap merge fields in quotes
    "email": ""
    ❌ Don’t do → "email":

  • ✅ No trailing commas

     
    {
    "firstName": "",
    "lastName": ""
    }

  • ✅ Test with real data
    Empty fields may cause errors if the receiving system requires them.

  • ✅ Special note for Zapier users:

    • Use POST as the method.

    • No headers required (optional: Content-Type: application/json).

    • Data shows up in the Zap editor under “Test Trigger.”

Tips for Success

  • Make sure your receiving system is ready to accept data.

  • Use free tools like Webhook.site or Postman to test before going live.

  • Keep your JSON payloads neat and properly formatted.

Wrap-Up

That’s it! Once set up, your webhook runs automatically whenever the workflow conditions are met — pushing data out of Lendware and into the tools that matter most to you.

Need more help? Check out: Intro to Automations


    • Related Articles

    • Intro to Automations

      Automations is your one area to create and manage all things automatically created or managed. From Transaction (loan) communications to Drip (nurture) campaigns to New Lead workflows, tasks and comms - Automations manage your best intentions. ...

    • Contact-Based Automations

      Contact-based automations are designed to support your lead management, contact engagement, education, reminders, and more. These automations help you act on your best intentions without manual follow-up. What is a contact based automation Create new ...

    • Using Tags and Status Changes to Chain Automations

      Automation chaining allows one automation to trigger another by updating a tag, contact status, or field value. This technique helps create a structured workflow where contacts move through different stages automatically. For example: A lead ...

    • Managing Multiple Automations on the Same Contact

      In Lendware, contacts and transactions can be enrolled in multiple automations at the same time. While this flexibility allows teams to create powerful workflows, it can also lead to situations where contacts receive too many emails or SMS messages ...

    • Transaction-Based Automations in Lendware

      Transaction-based automations help streamline and enhance communication throughout the loan process. From loan milestone updates to assigning tasks and sending follow-ups, they play a key role in keeping your team and clients aligned. In this ...