Webhooks you can watch, pause and replay
Axon Suite posts each new customer to your own middleware through your field map, signed so you know it came from you. Failures are retried, kept for replay, and a kill switch stops sending while you fix the other end.
- Event
- New customer C-1042
- Call
- Timed out
- Retries
- Automatic, then stopped
- Now in
- Dead-letter queue
Held · Kept for you to replay once the other end is back
How a webhook connection is set up
Add the connection
One webhook connection per subsidiary, with its address, token and optional signing secret stored encrypted.
Test it
Run a test call and see whether it passed, and why not if it failed.
Map the fields
Pair each field with the other system’s name, and translate values such as payment terms through a lookup table.
Watch it work
The health view shows the last 24 hours of calls, success rate, latency and what is waiting in the dead-letter queue.
Details that matter
Signed both ways
Outgoing calls carry the token and a signature. Incoming calls need the token, the signature when a secret is set, and a timestamp within five minutes.
Token rotation without downtime
Rotate the token and the old one keeps working for 24 hours while your middleware switches over.
Kill switches
Stop one kind of connection or all of a subsidiary’s, with a reason others can see. Nothing goes out until it is cleared.
Questions buyers ask
What does Axon Suite send today?
New customers: code, name, tax number, email, phone, payment term, currency and billing address. Sending invoices and payments is not there yet.
Can our system send changes in?
Your middleware can post item changes to the connection’s address, where each call is checked, mapped and logged. Saving them into your item records is not there yet.
Can we replay many failures at once?
Yes. Pick dead-letter entries and replay or cancel them together. Any outgoing delivery in the log can also be retried on its own.