Module M13
DesignedIntegration and export
Signed webhooks out to your own systems, with a delivery log and replay, plus exports of the register, cases and costs.
Data, screens, notifications and settings are decided. No code is written.
What shapes this module
The same delivery model as the notifications: the event is queued inside the transaction and sent only once it has committed. An HTTP call to your endpoint from inside an open transaction holds a database connection for as long as your server takes, and that has cost us once already. Delivery is signed and happens at least once, with the event id as the key so a duplicate is recognisable at your end.
For the manager
- Endpoints with their own secret each
- A delivery log with replay
- Exports of the register, cases and costs
What you configure yourselves
- Endpoints and which event types each one subscribes to
Not built
Not built. There is no finished integration with any external system today, and we never write otherwise. What makes an integration a reasonable piece of work rather than a project is that the business logic already sits apart from the delivery mechanism — but that is a precondition, not a delivered connection.
Contact
Tell us how a repair report is handled with you today.
Write a few lines about the portfolio you manage and where the time goes today. We will reply with how that looks in the system, and book a call if it seems worthwhile.