This week, we're excited to introduce a game-changing update that will streamline your notification workflow and keep your team connected like never before.

🚀 New Release: Platform Notifications via Slack

We're excited to announce that you can now receive pipeline failure alerts directly into Slack channels. Users no longer need to build notification logic into every single pipeline or rely on email alerts.

We've added Slack as a core platform notification delivery mechanism. This allows you to subscribe to notifications for specific projects or environments and route them exactly where they need to go.

Example Use Cases:

• Environment-specific routing: Send development failures to a sandbox channel and production alerts to your high-priority alerts channel.
• Noise reduction: Rather than building alerts into every pipeline, simply subscribe to a project or environment once.

Getting connected takes less than two minutes:

1. Create a Slack app: Follow the Slack Webhook Documentation to create a simple app in your workspace.
2. Generate a Webhook: Enable "Incoming Webhooks" and copy the unique URL for your desired channel.
3. Link to the Maia Foundation: Paste that URL into the Notification Settings within the Maia Foundation to activate the link.

For more information about setting up pipeline notifications, read our documentation.

💬 We'd Love to Hear From You!

Let us know how these new features are improving your workflows—we're all ears! Feel free to add any comments or questions below.

Want to get involved? Join the Matillion Community to stay up to date, share feedback, and help shape our product roadmap for future innovations.

‍

This week, we're excited to introduce a major advancement in pipeline observability with Maia's new intelligent recovery capabilities, taking you one step closer to autonomous data pipeline management.

🚀 Maia-Assisted Pipeline Recovery with Automated Fix Suggestions

We've just levelled up Maia's observability capabilities. Instead of just telling you what isn’t quite right, Maia can now help you fix it in a single, integrated workflow.

How does it work?

1. Ask Maia to fix a problem

The failure notification that includes the summary of the failure now includes a Fix with Maia button to begin the recovery process. Click this button to get started.

2. Configure details

To ensure safe recovery, Maia guides you through some quick configuration steps to confirm the branch name for the fix, the branch it’s based on, and your environment.

3. Sit back and watch Maia solve the problem

Maia automatically analyzes the failure type (e.g., schema drift, configuration error), and drafts a fix directly in the new branch for you to review. After you’re happy with Maia’s work, simply publish your changes.

Key Benefits

• Reduced operational burden: No more manual log debugging for common syntax or config errors.
• Safety first: You retain full control and visibility over what Maia changes before it hits production.
• Minimized downtime: Accelerates the path from "Failure Detected" to "Pipeline Recovered".

For more details, read our documentation.

💬 We'd Love to Hear From You!

Let us know how these new features are improving your workflows—we're all ears! Feel free to add any comments or questions below.

Want to get involved? Join the Matillion Community to stay up to date, share feedback, and help shape our product roadmap for future innovations.