With webhooks you can automatically send a notification to an external application as soon as something happens in Oneteam. This lets you connect Oneteam to your own systems, dashboards or automations without transferring data manually.
A webhook sends an HTTP request to a URL that you set. That URL then receives information about the event, for example when something is created, changed or completed.
When do you use webhooks?
Webhooks are useful when you want to connect Oneteam to other tools. For example:
updating an internal system when there is a new employee or a change
sending notifications to your own workflow or integration platform
syncing data with a data warehouse or reporting tool
starting automatic follow-up after a specific action in Oneteam
Setting up a webhook
Go to organisationdashboard > settings.
Open the Webhooks section.
Click Add webhook.
Fill in the URL that Oneteam should send the webhook to.
Select the events you want to receive notifications for.
Save the webhook.
From that moment on, Oneteam automatically sends a request to the configured URL whenever a selected event takes place.
Webhook payload
Every webhook contains information about the event. The exact content can differ per event type, but the payload usually contains:
the event type
the time at which the event took place
the organisation the event applies to
the relevant data of the object that was created or changed
Example:
{ "event": "example.created", "createdAt": "2026-07-31T14:26:00Z", "data": { "id": "abc123", "name": "Example" } }Beveiliging
Security
Always use an HTTPS URL for your webhook endpoint. If Oneteam offers a signing secret or verification header, check it on your side before you process the payload. That way you know for sure the request really comes from Oneteam.
Do not share webhook URLs and secrets publicly, and store them securely in your own system.
Testing a webhook
After creating a webhook, you can test it by triggering an event the webhook is set up for. Then check in your own system whether the request was received and processed correctly.
Pay attention to the following:
does your endpoint accept POST requests?
does your endpoint return a successful 2xx response?
is the URL publicly reachable?
is a firewall or authentication layer blocking the request?
Feel free to reach out via chat if we can advise or help you with anything.