Now that we have our template loaded and our first Workflow Group created, we can start customizing it to our needs.

Clicking on the Flow name brings up the list of all Flows in the Workflow Group. 

We can use the edit button to change the name to better describe the purpose of the workflow.

Set your name and description then select update.

Now let's work on our Flow logic.

Let's click on a the Branch on Event Types Step.

Clicking on each step brings up the step inputs and options.

By default, this template comes with branches for each Canopy webhook type.

For our use case, we only want to send the borrower an email reminder when we receive the payment due webhook, so let's delete the other options for clarity.

Great, now our branch step is much easier to read.

Let's verify that it works by clicking on "Save & Run Test".

This will bring up our Test Runner.

You'll notice we're prompted to first configure the test before we can run. 
Click on "Save & Reconfigure Test Instance" to do that.

This brings up the Configuration Wizard where we can set all of the variable options for our Flow.

This page is completely customizable, but so far all we need to do is authenticate with the Canopy API. 

Clicking Connect to authenticate. This will open a new tab to verify the authentication was successful. You can close that tab once complete.

Since our Flow is started based on receiving a webhook, we need to give the Test Runner an example payload to know what to expect.

To do that, click n the Trigger tab in the Test Runner. 

Paste in an example payload body.

Example webhook payloads can be found here: [https://docs.canopyservicing.com/docs/event-types](https://docs.canopyservicing.com/docs/event-types)

IMPORTANT: You will need to change the example payload to use an Account ID that is available in your environment.

Here you'll see we used an example payment_due_date example response since that is the payload we expect to receive to kick off send our borrower a notification.

Note: You can copy example payloads from each webhook type from the Webhook section of the Canopy docs.

Now we can see that our test ran successfully.

We can also see the results of each step.

We'll go more in depth on testing in the next tutorial, but you will also see shortly how having the output of each step from Test Runs is helpful as we build out the rest of our Flow.

Focusing back on our Flow designer, so far we have a trigger to receive a webhook, then we branch to make sure it's the payment due date event that we care about.

Now we want to notify the borrower of that event so they remember to make their payment on time.  

To do that, we'll need to know their email address to send to.

We don't currently have that information from the webhook. We only know their Account ID.

So now let's add a few steps to get the information we need.

Clicking on the "Add Step" icon will bring up the component selector.

We can enter "Canopy" in the search bar to select the Canopy Connector.

We want to be able to get the borrower's email address based off of having their account ID.

The email address is part of the customer entity, so first we need to know what customer to get.

Connect Canopy data with the other systems that power your lending program.

Let's use the "Get Account" action to retrieve the customer ID.

Tip: Notice there is an action for every endpoint in the Canopy API.

Once you select the action you want to you, the action editor will appear again.

We can click on the Account ID field to let it know which account to get.

We received the account ID as part of the payment_due_date webhook payload, so let's click "Reference" to use it.

Canopyservicing

Gist

Userlist

For this tutorial, we'll use the case of wanting to send borrowers upcoming payment reminders to help increase repayment rates. We'll walk through how to automate this with Canopy Connect.

Connect Canopy Getting Started Part 2: Setting Workflow Steps & Logic