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

Webhooks are a common way for web applications to notify users of important occurences. Use the Webhook agent 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 Agent 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 to generate and emit a new Event.
  • Specify a custom response and response headers when Event is successfully emitted.

Configuration Options

  • secret - A token that the host will provide for authentication.
  • verbs - (Optional) Comma-separated list of HTTP verbs your agent should accept.
  • response - (Optional) The response message to the request. Defaults to ‘Ok’.
  • response_headers - (Optional) An object with any custom response headers. (example: {"Access-Control-Allow-Origin": "*"})
  • expected_update_period_in_days: (Optional) Set this key to the maximum amount of time expected to pass between Events being created by this Agent. If this period passes without any Events being emitted, the Agent will be flagged as “Not Working”.

Emitted Events

The Webhook Agent 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",
  "expected_update_period_in_days": 1

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

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