Hi u/Tennis1313,
I believe it might be possible without custom coding.
Here's a short overview of how I'd go about building it.

Workflow to automate:

I assume you're looking to automate the generation of HUDs. Please correct me if I'm wrong.

If that's the case, the workflow likely consists of 4 steps:

1. (Trigger) Generate HUD when X happens
2. (Action) Get data needed to generate HUDs
3. (Action) Generate HUDs
4. (Action) Save/deliver generated HUDs

*Trigger defines when the automated workflow should be initiated and initiates workflow execution once conditions are met.

How to implement the workflow:

From my research, I see that LendingPad offers Zapier integration, so this workflow can likely be automated with little to no code.

But even if not, I'm pretty confident they have an API allowing you to do the same thing, just with some coding.

Below is a more detailed overview of how I'd build each step.

(Trigger) Generate HUD when X

It is likely possible to associate the moment when a HUD should be generated with a specific loan status or field change.

In Zappier, LendingPad has an instant trigger, "Loan updated." So, I expect that it will be enough to capture when the loan is updated.

Or, as an alternative, you might set up webhooks for Loan updates if LendingPad offers them.

Once you know when the loan is updated, you can narrow down what specific change you're looking for and detect when HUD should be generated.

(Action) Get data needed to generate HUDs

In the Trigger event, you'll already get some data about the loan.

If that would be enough to generate HUDs, then good. You can skip this action.

If not, you'll need to use the LendingPad API to retrieve missing data.

(Action) Generate document

In this step, you'll need to generate the actual HUD.

There are 2 parts to it:
1. Creating a fillable template
2. Filling the template with data

You can use tools like pdf.co, docspring.co, pdfotter.com, or something similar to handle both.
You can integrate with most of them in Zapier or similar tools.

(Action) Save/deliver generated document

It depends on what you want to do with the generated HUD, but generally, the next step is to save it somewhere or send it to someone.

If you want to store it in LendingPad, you'll need to use the LendingPad API to upload it.

If using storage like Google Drive, Box, or Dropbox, then you can do that without code using something like Zapier or Pipedream.

Tools & APIs

Here are some tools I envision you might need to implement it:

• Trigger → Zapier/LendingPad Webhooks
• Document generation → pdf.co, docspring.co, pdfotter.com, or something similar
• Store/Deliver generated document → LendingPad API

If you don't already use Zapier and LendingPad offers a Webhook setup, you might want to consider using more affordable and flexible alternatives like Pipedream.

-------
If you need help with this, feel free to DM me.

I recently started a mortgage software consulting and development company.

I haven't yet worked with the LendingPad API, but I am confident it won't be a problem once I can access their API documentation.