Weik.io

Webhooks

Receive and process HTTP webhooks from external systems

Webhooks let external systems push data to your Weik.io platform as soon as an event occurs, without polling.

What are webhooks

Instead of running a job that polls an API for changes on a schedule, a webhook gives that API a URL to call. The external system sends an HTTP POST request to the URL as soon as an update occurs.

Features

  • Custom endpoints - Create URLs for external services to call.
  • Immediate processing - Your integration flows start as soon as the payload arrives.
  • Built-in security - Weik.io supports API keys, HMAC signatures, and IP allowlisting, so endpoints are not left open to the internet.
  • Validation - Reject invalid data before it reaches your integrations.

How it works

  1. Create a webhook endpoint in Weik.io.
  2. Provide the URL to the external service, such as Stripe or GitHub.
  3. The external service POSTs data to the endpoint.
  4. Weik.io validates the request and passes it to your integration flow.
  5. The flow processes the data, and Weik.io returns a 200 OK response to the external service.

When to use webhooks

Use webhooks whenever a system supports them:

  • Payment notifications (Stripe, PayPal)
  • Repository events (GitHub, GitLab)
  • Form submissions
  • Order status updates

Security

Do not leave webhook endpoints unsecured. The available options are:

  • API key authentication
  • HMAC signature verification
  • IP allowlisting (if the service publishes its IP ranges)

Webhook management

The Webhooks dashboard shows your configured endpoints and whether they are receiving traffic, and lets you test them without waiting for a real event.

Integration with flows

Webhooks trigger integration flows. When the data arrives, your flow handles the rest:

  • Parsing the payload
  • Transforming it into a format your internal systems understand
  • Pushing it to a database, an event channel, or an API

Next steps