Send Slack Reminder
This action send a reminder to Slack channels, users, and user groups.
This field is automatically set for you. You can rename this field to whatever best describes your action. The value in this field does not affect how the workflow action behaves.
Specify the Slack users you wish to send the custom Slack reminder to.
Specify which Slack user groups you wish to send the custom Slack reminder to. All users part of the specified user group will be sent the message. You can read more about Slack user groups here.
This field specifies which Slack channels to send the Slack reminder to.
Some common selections:
- Setting to {{ incident.slack_channel_id }} will send the reminder to the Slack channel of the triggering incident.
- The Liquid snytax {{ parent_incident.slack_channel_id }} can be used for sub incidents and it will send the reminder to the Slack channel of the parent incident.
- You can also send reminders to static channel (e.g. #gernal, #alerts)
Reminders and messages are essentially the same. The difference being reminders come pre-configured with the Snooze Reminder and Pause Reminder actions. Also, reminder workflows are configured to trigger on a recurring schedule.
Slack reminders can also be sent with buttons that are linked to actions. The current available actions are listed below.
Action | Description |
|---|---|
Update Summary | Surfaces a Slack modal that allows you to update the incident's summary. |
Manage Incident Roles | Surfaces a Slack modal that allows you to manage you incident's role assignments. |
Update Incident | Surfaces a Slack modal that allows you to edit you incident's attributes. |
All Commands | Surfaces the help toolbar. |
Leave Feedback | Surfaces a Slack modal for incident feedback. |
Manage Custom Fields | Surfaces a Slack modal for managing your custom fields. |
Mange Action Items | Surfaces a checklist for managing the incident's action items. |
View Tasks | Surfaces a checklist for managing action items assigned to your user. |
Add Pagerduty Responders | Escalation modal for adding Pagerduty responders. This action requires a that the Pagerduty integration is already setup for you team. |
Add Opsgenie Responders | Escalation modal for adding Opsgenie responders. This action requires a that the Opsgenie integration is already setup for you team. |
Add Victor Ops Responders | Escalation modal for adding Victor Ops responders. This action requires a that the Victor Ops integration is already setup for you team. |
This field contains sets content of the message you wish to send. Incident variables, Liquid syntax, and Slack markdown are all supported in this field.
If you want to thread the remidner under an existing block/message that Rootly has sent, you can do so by selecting a parent message to be threaded under.
This field is used to filter for the workflow contains the specific action responsible for sending the parent message. The value in this field will not persist once the workflow is saved, as the Select a Task field is what ultimately determines the parent message to thread under.
This field is used to select the specific action that's responsible for sending the parent message. This field determines which message is the parent message to thread under.
If this field is selected, the workflow will update the original parent message, instead of thready underneath it.
If this field is selected, the threaded message will also be broadcased as a new message in the specified channels.
If selected, your reminder will be sent as a hidden message visible only to the specified users.
A value must be set for the Slack Users or Slack User Groups and Channels when this field is selected. Additionally, the selected users need to be in the specified channels.
If selected, your reminder will pinned to the specified channels.
