Write the right data to your CRM
Map fields from the payload into Client Data or your CRM — incident, component, status, or whatever your flow needs.
A dedicated inbound URL for your assistant — wired into your flow.
Every webhook interface gets its own URL. Point any system at it, then let the assistant use the payload in your workflow.
Four steps — we set it up with you.
You get a dedicated URL for this flow. Align on what should happen when a POST arrives.
Register the URL in a status page, helpdesk, or any tool that can send HTTP webhooks.
The JSON body and selected headers are available to decide what should happen next.
Write records, start a workflow, or hand over to your team.
Configure inbound webhook routing for this interface. In the agents flow, connect the webhook entry point to your first agent.
Inbound URL
https://api.dataspeak.nl/integrations/inbound-webhook/a1b2c3d4e5f6…Paste this URL into the system that should notify your assistant.
Payload in workflow
Starting a process from a webhook and connecting it to the rest of your workflows is straightforward.
Map fields from the payload into Client Data or your CRM — incident, component, status, or whatever your flow needs.
Classify events by type or payload and route them to the right workflow or agent.
Let an inbound POST start the same agent flow you already run from email, chat, or API.
No custom connector required — if it can POST JSON to a URL, it can talk to DataSpeak.
The JSON body and selected headers are passed through to your agents as state.inputWebhook.
Book a conversation and see how webhooks fit into your customer contact.