This article will provide you with an overview of how the address fields are treated once workflows are converted to records.
This functionality will be live on July 10th. To learn more about the features included in our July release, refer to What's New in Ironclad: July 2025.
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
| Question | Answer |
|---|---|
| Does this format support international addresses? | We do not currently support dynamic international address formats. If a country's format doesn't align with the defined structure, use address lines 1–4 as needed. |
| Will AI suggestions (including Smart Import) detect addresses in the multi-line format? | No. AI suggestions currently detect addresses as a string. |
| 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 mult-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. |