# Send your requests to your tool

This article explains how to send each request from a form to a web address, for example that of a Make scenario or a Zap. You will be able to connect that address, try it on Staging, read the content of a delivery and follow the delivery log.

## Before you start

- Each form can send its requests to a web address that you provide (a webhook). Your site sends each request to that address in JSON format within minutes of receiving it.
- Lovely Render does not offer a ready-made connector for customer management software. To bring your requests into it, go through Make, through Zapier or through the web address that your tool provides.
- The addresses are set in the **Forms** menu, reserved for the site administrators.

## Understand the two delivery addresses

Each form has two delivery addresses, one per environment. This way you try your connection on Staging without writing to your real tool.

| Address | Receives |
| --- | --- |
| **Production address** | The requests from your visitors, received on your live site. |
| **Staging address** | The submissions made on your Staging, your tests. |

An empty address sends nothing. An empty **Production address** never falls back to the staging address.

The addresses are set on Staging and go live with the publication of the site. A **Staging address** is used as soon as you save it. A **Production address** that you enter or correct is used by your live site only after your next publication. The screen reminds you under the field: **Production uses it from the next publication of the site.**

The **Publish now** link follows this sentence. It opens the publishing screen of the site, from which you start the publication. The link does not publish anything itself.

## Connect an address

1. In your tool, create the arrival point. In Make, it is a custom webhook at the start of a scenario. In Zapier, it is the **Catch Hook** trigger of Webhooks by Zapier.
2. Copy the address of the arrival point.
3. In the administration menu, open **Forms**, then click the name of the form.
4. Click the **Integrations** tab. The **Sending the requests** card appears.
5. Paste the address into **Staging address**.
6. Click **Save addresses**. The message **Addresses saved.** appears.
7. Next to the address, click **Test**. A sample is sent to your tool and the message gives its response, for example **The Staging address test succeeded (response 200).**
8. Send a real submission from your Staging and check that it arrives in your tool.
9. Enter the address of your real tool in **Production address**.
10. Click **Save addresses**.
11. Under **Production address**, click **Publish now**. The publishing screen of the site opens.
12. Publish your site.

![The Integrations tab of a form: the Sending requests card with the production address, the sentence Production uses it from the next publication of the site and the Publish now link under it, the staging address, a Test button next to each and the Save addresses button, then the Delivery log with its date, environment, status, attempts, HTTP code and duration.](https://static.lovelyrender.com/uploads/2026/10/216-formulaires-envoi.png)

An address must start with `https://` or `http://`. Any other value is saved empty. The **Test** button tries the saved address. Save a corrected address before testing it.

Each change of address is recorded in the history of the site with the name of its domain.

## Read the content of a delivery

Each request is sent in JSON format as soon as it counts as a received request: when the form is submitted or, on a multi-step form, at its conversion step.

The delivery contains the visitor’s answers, the name of the form, the origin of the request (source, medium and campaign) and the information notice the visitor had in front of them, with the uses they accepted.

Each field appears under its identifier, which does not change when you rename its label or the form. In Make or Zapier, map your columns to the field identifiers.

**Warning:** The value of an option comes from its text. Renaming an option changes the value your tool receives. Check your filters after such a change.

## Follow the deliveries

Under the addresses, the **Delivery log** lists the last fifty deliveries of the environment shown. The most recent is at the top. Each line gives the **Date**, the **Environment**, the **Status**, the **Attempts**, the **HTTP code**, the **Duration** and the **Error**.

| Status | Meaning |
| --- | --- |
| **Delivered** | Your tool accepted the delivery, with a response in the 200 family. |
| **Retrying** | The delivery failed. It is sent again several times over the following hours. |
| **Failed** | All attempts failed. The delivery will not be sent again. |
| **Refused by the tool** | Your tool responded with an error in the 400 family, other than 408 and 429. The delivery is not retried. |

With no delivery, the log shows **No deliveries yet.**

**Note:** A delivery that fails does not lose the request: it stays in the **Forms** menu. After an outage of your tool, find the missing requests in the list of submissions or export them.

## Fix a rejected delivery

1. In the **Delivery log**, note the **HTTP code** and the **Error** of the line.
2. With a code in the 400 family, check in your tool that the address still exists and accepts deliveries.
3. Correct the address if needed.
4. Click **Save addresses**.
5. Click **Test**.
6. If the corrected address is the production one, publish your site.

## See also

- [Export your requests](https://lovelyrender.com/documentation/export-requests/)
- [Read requests and where they come from](https://lovelyrender.com/documentation/read-requests/)
- [Publish your site](https://lovelyrender.com/documentation/publish-site/)
- [Create a form](https://lovelyrender.com/documentation/create-form/)