Webhooks and connecting other systems
Send an event out of IDup the moment it happens, and find the other ways to connect an outside system.
A webhook is the cheapest integration there is. IDup calls your web address when something happens, and you do what you like with it.
Where to find itAPI → API Management → Webhooks and Automation / Workflows → WebHooks
Which webhook tool to use
- API Management → Webhooks signs every delivery, lets you choose the events per endpoint, repeats failed deliveries and keeps a log. Use this one. See Send events to your own system with webhooks.
- Automation / Workflows → WebHooks is the older tool. You define the request yourself: address, method, format, headers and fields.
The older WebHooks tool
- Open Automation / Workflows → WebHooks → WebHooks and add a new webhook.
- Enter the request address and choose what it is for, for example a new lead, invoice, ticket or quote.
- Trigger the event once and open Log history. It shows the request and the response code.
- Webhook schedule holds the timing side.
Technical interface
Automation / Workflows → Technical interface → Token issues a token for the GraphQL interface. Documentation opens the reference. Use it when a caller needs exactly the fields it asks for.
Other ways to connect
- Online Store → Integrations — online shops and the domain. See Connect an external shop.
- API in the sidebar — see API keys and the API.
When something does not arriveRead the log first. A 4xx code means your address refused the request. A timeout means it answered too slowly.
Was this article helpful?
Nothing is tracked — the buttons only open a message so you can tell us what was missing.
