Templating
Wherever possible, you can use replacement tokens to customize your messages, for example duty messages or channel topics.
In certain areas, and wherever is supported by Slack (aka NOT in the channel topic!), you can also use Slack markdown to customize your messages. For more details, please refer to Slack guidelines.
To build a multiline message, just use return and make it multiline. Don't use \n.
If you are using the tokens to replace content where Slack markdown is not supported (for example, it doesn't work in topics), please use the "TEXTONLY" version of the token where available.
Tokens
The system supports the following tokens.
Rotation properties
| %NAME% | The rotation name (for example "Standup") |
| %DESCRIPTION% | The rotation description, if available |
| %DUTY_SIZE% | The size of the rotation duty (usually 1) |
User(s) on duty
| %USER% | The name of the user on duty (for example "Robert Redford") |
| %USERHANDLE% | The handle of the user on duty (for example "@robert") as a clickable Slack handle. |
| %USERHANDLE_TEXTONLY% | The handle of the user on duty (for example "@robert") written an PLAIN TEXT. |
| %USERID% | The SlackID of the user currently on duty |
User(s) next on duty
| %NEXT_USER% | The name of the user on duty which will be on duty after the current one (for example "Robert De Niro") |
| %NEXT_USERHANDLE% | The handle of the user which will be on duty after the current one (for example "@deniro") as a clickable Slack handle. |
| %NEXT_USERHANDLE_TEXTONLY% | The handle of the user which will be on duty after the current one (for example "@deniro") written an PLAIN TEXT. |
| %NEXT_USERID% | The SlackID of the user which will be on duty after the current one |
Rotation events
| %UNTIL% | The next rotation switch, expressed in the local time of the rotation (for example Mon, 24 Apr 2023 14:00:00) |
| %UNTIL_UTC% | The next rotation switch, expressed in UTC format (for example Mon, 24 Apr 2023 12:00:00 GMT) |
| %NEXT_UNTIL_UTC% | The rotation switch after the next, expressed in UTC format (for example Mon, 30 Apr 2023 12:00:00 GMT) |
| %NEXT_UNTIL% | The rotation switch after the next, expressed in the local time of the rotation (for example Mon, 30 Apr 2023 14:00:00) |
| %TIMEZONE% | The rotation schedule timezone identifier (for example Europe/Amsterdam, see here) |
| %TZ_OFFSET% | The rotation schedule timezone offset from UTC (for example +02:00) |
On-duty groups
| %DUTYHANDLE% | If the rotation use duty groups, the slack handle of the on-duty group (for example @standup-operator) as a clickable Slack handle. |
| %DUTYHANDLE_TEXTONLY% | If the rotation use duty groups, the slack handle of the on-duty group (for example @standup-operator) written an PLAIN TEXT. |
Special tokens
The special tokens listed below represent the user making the action and are available only during manual actions. For example, if you manually set user X on duty and you are user Y, the ME tokens will point to you, not to user X.
| %ME% | The name of the acting user. |
| %MY_HANDLE% | The handle of the acting user as a clickable Slack handle. |
| %MY_HANDLE_TEXTONLY% | The handle of the acting user written an PLAIN TEXT. |
| %MY_ID% | The SlackID of the acting user. |