The Webhook Action will emit Events it receives through Webhooks (HTTP callbacks).

Webhooks are a common way for web applications to notify users of important occurrences. Use the Webhook action to receive alerts from SIEM; get notified when a developer performs a ‘git push’; when a user updates a Jira ticket; or when a user posts in Slack.


  • Each Webhook Action has a unique URL.
  • Specify a secret that must be included in the Webhook in order for an Event to be emitted.
  • Accepts Webhooks using a variety of HTTP methods, e.g.: POST and GET
  • Webhook parameters will be used to generate and emit a new Event.
  • Specify a custom response message, response code and response headers when Event is successfully emitted.
  • Include incoming headers from HTTP requests.

Configuration Options

  • secret - A token that the host will provide for authentication.
  • verbs - (Optional) Comma-separated list of HTTP verbs your action should accept.
  • response - (Optional) The response message to the request. Defaults to ‘Ok’.
  • response_code - (Optional) The HTTP response code to the request. Defaults to 201.
  • response_headers - (Optional) An object with any custom response headers. (example: {"Access-Control-Allow-Origin": "*"})
  • include_headers - True by default, include headers from the request in a headers key while the body of the request is nested under a body key.

Emitted Events

The Webhook Action will convert the Webhook payload into a Tines Event.

Example Configuration Options

Receive GET and POST requests when the correct secret is supplied

  "secret": "e0d8498269045506b80e2f7a99d041e7",
  "verbs": "get,post"

Receive POST requests and respond with a custom response and response_headers.

  "secret": "e0d8498269045506b80e2f7a99d041e7",
  "verbs": "post",
  "response": "Thank you!",
  "response_code": 200,
  "response_headers": {
    "X-Tines-Response": "Event emitted"