<turbo-stream action="update" target="wiki_card"><template>
<h1>Slack Notifications for Schedule Monitor</h1>
<p><a href="/wiki/schedule_monitor" data-turbo="true" data-turbo-stream="true" data-controller="wiki" data-action="wiki#updateUrl">Schedule Monitor</a> now supports Slack as a notification destination alongside email. You can add a Slack channel to your list of destinations, so schedule failure notifications go wherever your team will actually see them.<br><br></p><h3>What's new</h3><p>Previously, Schedule Monitor notifications could only be sent by email. Now you can add a Slack channel as an additional (or alternative) destination, so a single schedule failure can notify both a Slack channel and an email address at the same time.<br><br></p><blockquote><strong>Note:</strong> You need to have your <a href="/wiki/how_to_connect_rapidi_to_your_slack_workspace_admin_only" data-turbo="true" data-turbo-stream="true" data-controller="wiki" data-action="wiki#updateUrl">Slack Workspace connected to Rapidi</a> through a one-time authorization process done by the Account Admin.&nbsp;</blockquote><p><br></p><h3>How it works</h3><ul><li><strong>Uses your existing Slack connection.</strong> Schedule Monitor sends notifications through the same Slack workspace connection you already set up for your account. There is no separate Slack integration to configure specifically for Schedule Monitor - just add the channel and go.</li><li><strong>Instant confirmation.</strong> When you save a channel under Schedule Monitor, a confirmation message is posted to that channel right away, so you can immediately verify the connection is working correctly.</li><li><strong>One failure, one count.</strong> A single schedule failure counts only once against your daily notification limit, even if it's delivered to both a Slack channel and an email address.<br><br></li></ul><h3>Setting name update</h3><p>Because the daily limit now governs total notifications rather than emails alone, the setting previously called <strong>"Max Daily Emails"</strong> has been renamed to <strong>"Max Daily Messages."</strong> The behavior is the same - it caps how many notifications go out per day - but the name now reflects that it applies across both channels.<br><br></p><h3>Setting it up in myrapidi:</h3><ol><li>Go to <strong>Account Settings &gt; Schedule Monitor</strong>.</li><li>Add your Slack channel to the list of notification destinations.</li><li>Save - you'll see a confirmation message posted to the channel.</li><li>(Optional) Keep or add an email destination alongside it; both can receive notifications for the same failure without double-counting against your daily limit.</li></ol><p><br></p><p></p><figure class="attachment attachment--content attachment--jpg"><div class="trix-media-container size-medium">
        <img src="/rails/active_storage/blobs/proxy/eyJfcmFpbHMiOnsiZGF0YSI6MjQzMSwicHVyIjoiYmxvYl9pZCJ9fQ==--54947e3666bd65f61793303011059b41a3dbeb5e/Schedule_monitoring_slack_channel.jpg" width="2904" height="592" title="Adding Slack Channel to Schedule Monitoring" alt="Adding Slack Channel to Schedule Monitoring">
      </div><figcaption class="attachment__caption"></figcaption></figure><p></p><h3><strong><br></strong>What it looks like in Slack</h3><p>Once a Slack channel is added under <strong>Schedule Monitor</strong>, two types of messages appear in that channel:<br><br></p><p></p><figure class="attachment attachment--content attachment--png"><div class="trix-media-container size-medium">
        <img src="/rails/active_storage/blobs/proxy/eyJfcmFpbHMiOnsiZGF0YSI6MjQxOSwicHVyIjoiYmxvYl9pZCJ9fQ==--7cd602b66a6a0db31ba7e250621d7e7624c1a73e/image.png" width="1742" height="1036" title="Slack Notifications" alt="Slack Notifications">
      </div><figcaption class="attachment__caption"></figcaption></figure><p></p><p><strong>1. The confirmation message</strong></p><p>As soon as the channel is saved, MyRapidi posts a confirmation message to the channel, e.g.:<br><br></p><blockquote>RAPIDI schedule monitor notifications enabled for Service ANDREEA_TEST_SERVICE</blockquote><p>This confirms the channel is correctly wired up - no further setup needed.<br><br></p><p><strong>2. Error notifications</strong></p><p>From that point on, any schedule failures for that service are posted to the same channel. Each message includes:</p><ul><li>The service name</li><li>The schedule name</li><li>The last run time and the notify time (both in UTC)</li><li>The last error message found for that schedule.</li></ul><p><br></p><p><strong>Why it matters</strong></p><p>For teams that already live in Slack, this means schedule failures surface where the conversation already happens, without needing to check email separately or set up a custom webhook integration just for notifications.<br><br>Learn more about <a href="/wiki/schedule_monitor" data-turbo="true" data-turbo-stream="true" data-controller="wiki" data-action="wiki#updateUrl">Schedule Monitor</a><br>Learn more about <a href="/wiki/how_to_connect_rapidi_to_your_slack_workspace_admin_only" data-turbo="true" data-turbo-stream="true" data-controller="wiki" data-action="wiki#updateUrl">How to Connect Rapidi to Your Slack Workspace (Admin Only)</a><br><br></p>
</template></turbo-stream>

<turbo-stream action="replace" target="meta_description"><template><meta content='Slack Notifications for Schedule Monitor' id='meta_description' name='description'></template></turbo-stream>
<turbo-stream action="replace" target="meta_keywords"><template><meta content='Slack Notifications for Schedule Monitor Error Messages Notifications Schedules' id='meta_keywords' name='keywords'></template></turbo-stream>
<turbo-stream action="update" target="meta_title"><template>Slack Notifications for Schedule Monitor - MyRapidi Wiki</template></turbo-stream>
<turbo-stream action="prepend" target="flash"><template></template></turbo-stream>
