From d59fe7195511bf942d486e09bed23eff198a0bf9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Adnan=20Hajdarevi=C4=87?= Date: Tue, 17 Mar 2015 19:37:39 +0100 Subject: [PATCH] added response-message --- Hook-Definition.md | 1 + 1 file changed, 1 insertion(+) diff --git a/Hook-Definition.md b/Hook-Definition.md index 537d34b..79f6851 100644 --- a/Hook-Definition.md +++ b/Hook-Definition.md @@ -6,6 +6,7 @@ Hooks are defined as JSON objects. Please note that in order to be considered va * `id` - specifies the ID of your hook. This value is used to create the HTTP endpoint (http://yourserver:port/hooks/your-hook-id) * `execute-command` - specifies the command that should be executed when the hook is triggered * `command-working-directory` - specifies the working directory that will be used for the script when it's executed + * `response-message` - specifies the string that will be returned to the hook initiator * `pass-arguments-to-command` - specifies the list of arguments that will be passed to the command. Check [Referencing request values page](Referencing-Request-Values) to see how to reference the values from the request. * `trigger-rule` - specifies the rule that will be evaluated in order to determine should the hook be triggered. Check [Hook rules page](Hook-Rules) to see the list of valid rules and their usage