How it works
The External systems section of a record lists its identifiers in other tools, such as a contract number in your ERP and a reference in your procurement portal. Users add them by hand, or integrations write them through the API.
Through the API and MCP, a record can be addressed by external:{system}:{id} instead of its Formality id. An update on an external reference that does not exist yet can create the record, which simplifies synchronisation.
Webhooks sent by Formality carry the external identifiers, so the receiving system knows which of its records changed.
What you get
- Several system identifiers per record
- Set in the interface or by API
- Records addressed as external:{system}:{id}
- Included in webhook payloads
Why teams use it
Your systems and Formality refer to the same record.
No mapping table of Formality ids to maintain.
Retried imports update the existing record.
See at a glance which ERP record a contract matches.
More in Integrations & API
MCP server and API for AI agents
Connect Claude, ChatGPT or Copilot to your contracts, within your rules.
Learn more →REST API
Create and update contracts, entities and documents from your tools.
Learn more →Outgoing webhooks
Formality notifies your systems when something changes.
Learn more →Microsoft Teams
Notifications and reminders in Teams.
Learn more →