Slack notifications
Renta's Slack integration allows your team to stay informed about the health of your data pipelines in real-time. By configuring Slack alerts, you can receive immediate notifications when a pipeline fails, ensuring minimal downtime and faster troubleshooting.
Connecting Slack
To begin receiving alerts, you must first link your Slack workspace to Renta.
Go to Alerts in the sidebar and select the Notification channels tab.

Click the Connect Slack button in the Slack workspaces section.

You will be redirected to Slack's authorization page. Select the workspace you wish to connect and click Allow.

Configuring channels
After linking your workspace, you must specify the individual channels where Renta should post updates.
Renta supports both public and private Slack channels. For private channels, simply invite the bot to the channel before trying to find it in the dashboard.
For security reasons, Renta does not have access to your entire channel list by default. To make a channel available for selection in Renta, you must first manually invite the Renta bot to that specific channel.
Adding Slack channels
Invite the bot and activate specific channels for notifications.
Open the desired channel in Slack (public or private) and type /invite @renta.

In the Notification channels tab, click Connect Slack or Add channel. Select your channel from the list. After you click Save channel, Renta will automatically send a test message to verify the connection.

Ensure the channel appears in your list with an Active status and check Slack for the welcome notification.

Tip: We recommend creating a dedicated channel like #renta-alerts to keep your main communication channels clean.
After your channels are configured, you must enable specific rules to define when notifications should be sent.
For enterprise-level workflows, Renta provides granular customization for your notification strategy. You can route different types of events to separate Slack channels—for example, critical pipeline failures can go to a dedicated #incident-response channel, while daily sync summaries can be sent to #data-reports.
Practical use case: You can optimize team response times by routing specific errors to the people responsible. For instance, source access errors (such as an expired Facebook Ads token) can be sent to the Marketing channel, while pipeline failures are directed to the Data Engineering team.
Error deduplication
To prevent alert fatigue, Renta automatically groups identical errors. You will receive one notification per 24 hours for persistent issues, unless the status changes to Resolved. This ensures your team stays informed without being overwhelmed by duplicate alerts.
Setting up alerting rules
Define triggers and assign destinations for your alerts.
Navigate to the Alerts tab. Find the Pipeline failed rule.

Switch the rule to On and select the desired Slack channels in the Send to dropdown.

Confirm your selection. The channel will now appear in the Selected channels list for this rule.

Best practices
-
Use Private Channels for sensitive data. If your alerts contain sensitive table names or error messages, use a private Slack channel and invite the bot there.
-
Assign specific owners. Ensure the relevant engineers and analysts are members of the notification channel so they receive push notifications on their devices.
Ready to get started?
Build your data pipeline today or get a personalized demo. Start free!
Need help?
Get expert support to ensure your project succeeds. We're here to help!
Feature requests?
Help shape our product! Share your ideas for new features and integrations.