Skip to main content
A notifier tells you, outside piloop, that an inbox item needs you. To post to a Slack channel, create an incoming webhook, store its URL as a secret, and name slack in config.toml:
Then run piloop restart. The next escalation posts this to the channel:

​
What is sent

  • An item is sent when it is an escalation or has priority 0, nobody has acknowledged it, and a person did not write it.
  • Each pass of the daemon sends one message with every new item.
  • An item that still waits a day later is sent again as a reminder. piloop inbox ack ends the reminders.
  • piloop records each send as a notification.sent event on the item, so a restart sends nothing twice.

​
When a send fails

piloop records a notification.failed event with the error, and tries again after 1 minute, then 2, 4 and so on, up to an hour. Slack’s Retry-After wins. The first failure also puts a note in your inbox, under the item that was not sent.

​
A channel of your own

Name an instance to change its keys. A notifier that use does not name is an error.
template sets how the message shows each item, from a fixed set of placeholders: an unknown one is an error when the file loads. On a shared server, mentions pings the person who added the campaign, by the name that the server gives them. The configuration reference lists every key of slack. To write a notifier for another service, see Infrastructure.