> ## Documentation Index > Fetch the complete documentation index at: https://help.leaf360.com/llms.txt > Use this file to discover all available pages before exploring further. # Connecting RETR > How to set up a Custom Webhook in Leaf360 so RETR can send records straight into your pipeline, then map the fields and choose who each lead lands on. This walks you through connecting **RETR** to Leaf360 with a webhook, so what RETR sends you lands in your pipeline without anyone retyping it. RETR doesn't have its own card yet. It comes in through the **Custom Webhook** card, at the bottom of the same Integrations page that has LendingTree. You'll need to be an admin or super admin to set it up. ## Connecting RETR Click your profile at the bottom left of your screen, then **Account Settings**. Profile menu open over the sidebar. Account Settings is the first item, boxed in red, above Notifications, Current Workspace, Organization Role and Log out. In the settings list, scroll down to **Data & Integrations** and select **Integrations**. Settings sidebar scrolled to the Data & Integrations group. Integrations sits between Tags and Import History; the group heading and Integrations are both boxed in red. Scroll to the bottom of the page until you reach the **Webhooks** section. Go ahead and select **Manage** on the **Custom Webhook** card, the one marked **Any Source**. Select **+ New Endpoint** at the top right. Custom Webhook Endpoints list. The New Endpoint button at the top right is boxed in red, above rows of existing webhooks that each show a record type, a status and a request count. Name the **Endpoint Name** something like RETR, so that way you can pick it out of the list later. Leave **Entity Type** on **Leads**, unless your RETR contact tells you they're sending something else. Set the **Integration Template** to **Custom (Field Mapping)**. Under **Source fallback**, pick or type **RETR**. That way every record that comes in without a source still shows up as RETR in your reports. Set the **Authentication Method** to **API Key (Authorization Header)**, then select **Create Endpoint**. Create Webhook Endpoint form. Endpoint Name, Entity Type set to Leads, Integration Template set to Custom (Field Mapping), optional source and campaign fallbacks, and Duplicate Handling set to Upsert. Authentication Method, set to API Key (Authorization Header), and the Create Endpoint button are boxed in red. Leaf360 gives you a **Webhook URL** and an **API Key**. Make sure you copy the API key now, because it isn't shown again. Confirmation screen after creating the webhook. The Webhook URL field is blurred, with a copy button beside it. The API Key field carries a note to copy it now, since it isn't shown again. Three next steps follow, then a Done button. Send the **Webhook URL** and the **API Key** to your RETR contact. RETR uses them on their side to post your records to that URL, with the API key in the Authorization header. Ask them to send one test record once it's set up. You'll need it for the next step. Once the test record arrives, go back to the RETR webhook and open the **Field Mapping** tab. Match each field RETR sends to the Leaf360 field it belongs in. Make sure you map **email**, **phone**, or both. With neither one mapped, Leaf360 has nothing to recognize a repeat lead by, so the same person comes in twice. ## Choosing who each lead lands on **Assignment mapping** decides which loan officer gets each lead from RETR. For example, let's say RETR sends the loan officer's email on every lead. Match that field to the LO's email, which is the match that holds up best. When nothing matches, the lead falls to a pond you pick. You can also send every RETR lead straight to a pond instead. You're going to want to run a **dry run** before you switch it on, so that way you see where records would land first. Each lead that comes in afterward keeps a note of who it went to. [Integration settings](/mortgage-crm/integration-settings) covers assignment mapping and list fields in more detail. ## Keep your webhook URL private Treat the webhook URL and API key like a password. Anyone who has them can send records into your workspace, so don't post them anywhere public. If you think they got out, go ahead and set up a fresh RETR webhook and send RETR the new URL and key. ## If leads stop arriving * Make sure the URL in RETR's system matches the one on your RETR webhook in Leaf360. * Check the request count on the **Custom Webhook Endpoints** screen. If it isn't going up, RETR isn't sending, so check with your RETR contact first. * If requests are coming in but leads look wrong, open **Field Mapping** and check what each field is matched to. Still stuck? [Contact support](/support/contact-us) and say it's your RETR webhook. ## Related * [Connecting LendingTree](/integrations/connecting-lendingtree) * [Integration settings](/mortgage-crm/integration-settings) * [Integrations overview](/integrations/overview) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.