Connector name:
Concord

Table name:
agreement_property (new child table of agreement, parent key agreement_uuid)

API documentation link:
https://api.doc.concordnow.com/#tag/Agreement/operation/ListAgreements

Additional details:
The documented endpoint GET /user/me/organizations/{organizationId}/agreements returns a "properties" array on every agreement (AgreementListItemPropertyDto: propertyId, propertyName, propertySource, visibility, content). These are the custom properties shown in Concord under Document summary > Properties. Concord Support confirmed this is the supported way to retrieve them.

The connector already uses this response for the agreement table and already unpacks the "tags" array into agreement_tag, but the "properties" array is not synced. Teams using properties for contract and revenue reporting currently have to maintain this data manually outside the warehouse.

Requested:
1. A child table agreement_property with columns such as agreement_uuid, property_id, property_name, property_source, visibility, content_type and content_value (JSON/variant, plus a flattened text value).
2. Optionally, a setting to sync only user-defined properties (propertySource = USER), since system properties can contain personal data such as user names and email addresses.
3. Include this table in a periodic full re-sync. According to Concord, changing a property value does not update the agreement's modifiedAt, so incremental syncs will not pick up property changes.

Value structure: content.value is either a scalar (text, number, boolean, date, ISO-8601 period) or an array of objects for SINGLE_SELECT / MULTI_SELECT properties.