# Override Delivery Details with Custom Component

Limio for Salesforce has a built in flow component for capturing delivery details.

Since the collected address is then passed to a flow variable, another custom component could be built, to replace this one.

When building a custom component, its output must be stored in a stringified json object that must have the following format.

```
{
"CompanyName": "Limio",
"FirstName": "giacomo",
"LastName": "test",
"MailingCity": "London",
"MailingCountry": "GB",
"MailingPostalCode": "SE1 3ER",
"MailingState": "London",
"MailingStreet": "Leathermarket St, Weston St 12",
"MailingBuildingNumber = "12",
"MailingStreetName = "Weston St"
}
```

```
{
"CompanyName": "Limio",
"FirstName": "giacomo",
"LastName": "test",
"MailingCity": "London",
"MailingCountry": "GB",
"MailingPostalCode": "SE1 3ER",
"MailingState": "London",
"MailingStreet": "Leathermarket St, Weston St 12",
"MailingBuildingNumber = "12",
"MailingStreetName = "Weston St"
}
```

Note: MailingStreet maps to an address1 standard address field in Limio (it may combine street name and building number), while it's also possible to map streetName and building number as standalone fields to MailingStreetName and MailingBuldingNumber respectively.

Once all of the above information are being collected, the content needs to be stringified and its value assigned to the " address" flow variable.

This is then used in the rest of the flow and in turn sent to Limio as part of the order.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.limio.com/integrations/using-limio-for-salesforce/address-mandatory-fields/override-delivery-details.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.