This article will provide you with an overview of how the address fields are treated once workflows are converted to records.
How are Addresses Stored on Records?
When a workflow is archived, Ironclad converts it into a record and stores it within the Repository tab on the Dashboard. During this process, any addresses in the workflow are converted into a multi-line, structured format. This enables seamless downstream integration for features such as entities that use the address fields as data.
FAQs
Does this format support international addresses?
Yes. The address object in the Repository has the same set of fields as the address object in workflows or launch forms:
Address Line 1 Address Line 2 Address Line 3 Address Line 4 Locality (City or Town) Region (State or Province) Postal Code (ZIP Code Country
Address lines 1-4 can be used to replace information meant for named address fields as needed.
Here's an example of what the new format will look like for addresses:
"counterpartyBillingAddress": {
"type": "address",
"value":
{
"lines": [
"4527 Mission Street",
"Unit B"
],
"locality": "San Francisco",
"country": "United States",
"region": "California",
"postcode": "94112"
}
}Will AI suggestions (including Smart Import) detect addresses in the multi-line format?
Yes. We support address formats from the following regions:
- US
- UK
- Canada
- China
- France
- Germany
- India
- Italy
- Japan
- Mexico
- Switzerland
If I have records that exist from prior to the format update on July 10th, 2025, what will happen to them?
Ironclad is not migrating existing records to this format. This will only apply to records created after the release on July 10th, 2025. If you would like to migrate the format of your existing records, you can use metadata export and import.
Can I use this multi-line format on my APIs as well?
Yes. You can opt-in to using the structured multi-line format in your APIs as well.
Will this work if I have an address column in a table?
No. Table data will still be saved as a single string in records.