How it works
Each outgoing webhook endpoint has its URL, subscribed events (for example agreement.* or entity.created) and status. Formality retries failed deliveries, and an endpoint is automatically disabled after repeated consecutive failures, with a notification to administrators.
The deliveries list shows the event, the record, the HTTP code, the number of attempts and the status (pending, success, failed, exhausted). The detail view shows the payload and the last response.
Charts show deliveries sent, successes, failures and latency over time. Failures can be replayed one by one or all at once.
What you get
- Webhook endpoints and their status
- Deliveries with HTTP code and attempts
- Success and failure charts
- Replay of failed deliveries
Why teams use it
No more guessing whether a change reached the ERP.
Replay failed deliveries once the receiving system is back.
Administrators are notified when an endpoint is disabled.
Payload and response are visible for each delivery.
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 →