This week, we're excited to share several powerful updates that enhance security, streamline your workflow, and improve operational visibility. From environment-level credential management to quality-of-life improvements in pipeline building, these features are designed to make your Maia Foundation experience more efficient and secure. For a full list of recent changes, be sure to check our changelog updates.

🔐 Environment-level secrets and OAuths

We've released environment-level secrets and OAuths, delivering enhanced security and simplified credential management across your data pipelines. This major update provides several key benefits:

• Granular control over sensitive credentials: Secret mapping in the vault is now bound to specific environments. This reduces the risk of accidentally modifying production secrets or OAuths.
• Simplified cross-environment credentials: Secret definitions and OAuths automatically adjust based on environment.
• Ability to edit existing secrets and OAuths: You can now update all secrets or OAuths, making credential rotation much easier.
• Consolidated Public API: We've simplified credential management into a single connections endpoint, moving toward unified management of all credentials under one umbrella.

🎯 Copying and pasting components made smoother

We've ironed out a friction point in the pipeline building process to make your workflow even smoother. Previously, when copying and pasting multiple components, the newly pasted items were not automatically selected.

Now, all pasted components are automatically pre-selected, allowing for immediate movement the moment they hit the canvas. This small change reduces manual effort and keeps your momentum going while building complex pipelines, making the development process more intuitive and efficient.

🚀 Pipeline run history now includes artifact versions

We've shipped an update to the pipeline run history view that makes operational triage faster and more efficient for data teams.

Key improvements include:

• Artifact version is now visible - You can see exactly which version was executed. When you're debugging a failure, you'll immediately know whether it happened before or after a recent change, without having to cross-reference Git history.
• "Triggered by" replaces "Started by" - The column now shows what fired the run (a schedule, a manual run by a user, or the API).
• Time columns are cleaner - Started at, Ended at, and Duration are now separate columns.
• Full folder paths are included in the pipeline detail.

The combination of artifact version and schedule trigger means you can answer two of the most common questions — which version of the pipeline ran and what triggered it — directly from the run history list, without clicking into individual runs.

👀 Artifacts tab more detailed than ever

The Artifacts tab in your project now shows the name of the user who created each artifact and, if you have your own Git repository linked to the Maia Foiundation, the Git commit hash used to create it.

This update makes it easier to trace your artifacts and cross-reference them with your Git history for more context.

💬 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 bring you several powerful updates that enhance automation capabilities, improve pipeline building workflows, and keep you connected with Maia's intelligent assistance. For a full list of recent changes, be sure to check our changelog updates.

🔀 New Data Transfer component

We have rolled out a brand new native Data Transfer component, designed to deliver a smoother overall experience while using the component.

What's changed:

• Improved integration with Maia: Enhanced support for pipeline building
• New source added: Microsoft Exchange is now available as a source

Important to know:

• Any pipelines using the old Data Transfer component will continue to work. The new component is available in the new components panel.

This enhancement is included in Agent version 11.183.0. For detailed information on how to use the updated component, check out the documentation.

📣 Hybrid Kubernetes options globally available

You can now choose between Kubernetes deployment options (EKS or AKS) when setting up a hybrid agent in the Maia Foundation. This open-source container platform integration provides greater flexibility and control for organizations already invested in Kubernetes infrastructure.

Key benefits:

• Public repository access: New templates, guides, and pre-deployment check scripts
• Auto-scaling capabilities: Dynamic resource management
• Leverage existing expertise: Use your established Kubernetes infrastructure
• Enhanced control: Greater flexibility for future developments and customizations

Read our deployment guide to get started, and check out our public repository of templates, guides, and pre-deploy check scripts.

🚀 New API endpoint: Create Secret

We're excited to announce the new Create Secret endpoint is now live! This powerful API endpoint supports Full SaaS secret creation in the vault, eliminating the need to manually enter credentials through the UI when setting up new environments.

This enhancement is perfect if you want to fully automate the creation of Full SaaS environments without requiring cloud credentials for data ingestion. By streamlining the secret management process, you can now achieve complete automation in your environment setup workflows.

Check out the API Reference documentation to get started with this new endpoint.

🔔 Maia: Background notifications are here

We're happy to introduce background notifications for Maia in Designer — so you never miss a response or approval request while multitasking.

Previously, if you switched to another browser tab while Maia was working, you had no way of knowing when it finished or needed your input. Now, Maia comes to you with three helpful notification features:

• Tab title indicator: A dot (•) appears in the browser tab title when Maia finishes processing or needs your approval, so you can spot it at a glance.
• Audio chime: A subtle notification sound plays to get your attention without being intrusive.
• Browser notification popup: A system-level notification appears, letting you click straight back to the conversation.

To enable these notifications, simply open the settings menu in the top right of the Maia chat and toggle Notifications on. You'll be prompted to grant browser notification permission the first time.

🎯 Add tables and views to the Designer canvas

We are streamlining the way you build pipelines with an important update to our Add to Canvas functionality. For transformation pipelines, you can now select a table or view directly from your warehouse schema and have the corresponding component automatically added to your workspace.

This update creates a direct path from your data source to your design by solving the challenge of navigating the array of available components, which can be daunting, especially for new users.

What's new:

• Pre-load validation: Before committing to the canvas, you can now inspect metadata and request a data sample. This ensures you are selecting the exact data you need before you even start building.
• Streamlined workflow: By removing the guesswork of component selection, we've made the process of loading warehouse data faster and more accessible for everyone. By default, we select all the table columns so the component is ready to use.

To access this feature, clicking the + on the Designer canvas, then select the new Warehouse data tab. We've also introduced the ability to search by schema name making it easier to find the right data.

💬 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 share several powerful updates that will enhance your experience with Maia, expand your migration options, and provide better visibility into your pipeline operations.

🤖 Maia agents update: Automatic plan mode and dedicated pipeline validation

We're happy to introduce two improvements to how Maia works.

What's new?

• Automatic plan mode: Maia can now enter plan mode on its own when it determines a task is complex enough to warrant planning. It will explore your project, create a detailed plan, and present it for your review—approve it to proceed, or request changes.
• Dedicated pipeline validation: Pipeline validation is now a standalone action rather than just a side effect of editing. Maia can check your pipeline components against the warehouse at any time, making it better at understanding and diagnosing configuration errors, invalid options, and missing references—even when it isn't actively editing.

How do you use it? Both improvements activate automatically. Maia will ask your permission before entering plan mode, and can validate pipelines independently whenever it needs to investigate issues.

🔄 Expanded competitor support for Convert Workloads tool

The Convert Workloads tool now supports four additional competitor platforms: IBM DataStage, Oracle ODI, Wherescape, and Apache NiFi, all available in Public Preview. This expansion brings the total number of supported competitor products to 15, making it easier than ever to migrate your existing data workflows to Maia.

With this enhanced compatibility, you can seamlessly transition from a wider range of platforms while reducing manual work in the conversion process. The tool automatically translates your existing workloads, helping you speed up your migration and reduce implementation complexity.

Documentation on the conversion process can be found here.

🚀 Better visibility for pipeline runs

We know that searching for a specific failure in a sea of "Red" can feel like finding a needle in a haystack, especially when a single pipeline is failing multiple times a day.

To save you from the manual scroll and give you better insight into your schedules, we've shipped two updates to Pipeline Run History:

Search by execution ID: Stop "trawling" and start finding. If you already have the specific execution ID from a log or an alert, you no longer need to filter by pipeline name and guess the timestamp.

• The change: The search bar now accepts full pipeline execution IDs.
• The benefit: Instant access to the exact run you're investigating. No more manual sorting through dozens of identical-looking runs.

Visibility into skipped pipelines: Previously, if a schedule tried to trigger but was blocked by concurrency config, it vanished. Now, you have the paper trail.

When a schedule has Allow concurrent executions set to False, and a new run is requested while the previous one is still active, we now log and display that attempt as Skipped.

• The indicator: Look for the amber status tag in the Pipeline Runs screen.
• The why: We've added specific execution messages to pinpoint the blocker: "Skipped because allow concurrent execution is false and execution [ID] is still in progress."

🤖 Maia update: Smarter conversation titles

A small quality-of-life improvement—conversation titles now update as you chat, so they always reflect what you're actually discussing, not just your first message.

What's new?

• Dynamic titles: Titles regenerate using your recent message history, staying relevant as conversations evolve.

How do I use it? No action needed—this works automatically for all conversations.

💬 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 bring you several powerful updates that enhance AI-driven automation, expand data quality capabilities, and streamline your migration workflows. From smarter pipeline recovery to new data cleansing tools and expanded workload conversion support, check out the latest changelog updates to see how these features are designed to make your Maia Foundation experience more efficient and intuitive.

🧹 Data Cleanse Component Enabled for Public Preview

A new transformation component, Data Cleanse, can now be added to the Designer canvas. This native data quality solution removes the need for you to work around data quality challenges by using many different components.

Leveraging the component's data-centric view, you can profile and filter your data to quickly identify data quality issues. You can then apply rules to your dataset to improve data quality, with all actions reflected in real time in the data-centric table view. The component integrates with Maia, which can apply filters to the data sample through natural language and suggest rules that can be applied in one click.

The Data Cleanse component makes it much easier for you to assess and improve the quality of your data, while also serving as a stepping stone to leverage the Maia Foundation in a more data-centric manner, not just as the typical pipeline-centric view.

The component is now available for all Snowflake users as part of a Public Preview release.

Documentation can be found here.

🔧 Maia-assisted Intelligent Pipeline Recovery Improvements

We've enhanced Maia-assisted Intelligent Pipeline Recovery (IPR) to make fixing pipeline failures faster and smarter. The goal is to close the gap between identifying a failure and deploying a fix by reducing the manual work required for you.

What's new:

• Context-aware defaults: When Maia can identify the specific commit hash, it will automatically default to the correct branch and environment
• Suggested branch: In scenarios with multiple possible paths, Maia marks the most relevant options as "Suggested" based on your commit and publish history
• Reduced cognitive load: You can now safely resolve production workloads with less manual investigation into the code's current location

Control meets automation: While moving toward a fully autonomous "Auto-Fix" ecosystem, you retain full flexibility:

• Override anytime: The ability to manually choose a different branch or environment remains available
• Safety first: Maia guides you to the right spot, but you remain the final gatekeeper for your production code

🤖 Maia Update: Improved Tool Approval Experience

We've upgraded how Maia asks for your permission before taking actions, making it easier to stay in control when Maia is working through multi-step tasks.

Previously, when Maia needed to perform several actions in sequence, approval prompts could pile up and feel overwhelming. Now they're presented one at a time with a clear count, and you can decline individual actions with an optional reason—so Maia learns and adjusts.

What's new:

• Stacked approvals: When multiple actions need approval, they queue up neatly—you'll see one at a time with a count of how many remain
• Decline with reason: Tell Maia why you're declining an action so it can adjust its approach, or just decline without a reason—it's optional

How to use it: When Maia wants to perform an action, an approval card appears in the chat. Click Accept, Accept for session, or Decline—if you decline, you can optionally explain why to help Maia course-correct.

🔄 Enhanced Context Management for Workload Conversion Tool

The Convert Workloads tool now lets you add conversion-specific context directly within the conversion workflow. Previously, you had to provide context to Maia either before starting the conversion process or exit the tool midway through to add necessary information, creating a disjointed experience.

Now, after selecting the competitor product and uploading files, you can optionally create or update conversion-specific context to help Maia more accurately replicate business logic from original files. This context can include development standards, detailed schema information, or other relevant details that improve conversion accuracy.

This enhancement streamlines the conversion process by keeping context creation within the logical workflow, eliminating disruptions and maximizing the accuracy of workload migrations from competitor platforms to the Maia Foundation.

Documentation on the conversion process can be found here.

🔄 New Competitors Added to Convert Workloads Tool

In addition to enhanced context management, additional competitors are now supported by the Convert Workloads tool. These include Azure Data Factory (ADF) and AWS Glue, we’re supporting both of these in Public Preview as of this week.

This brings the total number of supported competitor products to 11. Documentation on the conversion process can be found here. This expanded support makes it easier for organizations to migrate their existing data pipelines from these platforms to the Maia Foundation, reducing the manual effort required for workload conversion and accelerating time-to-value for new users.

🤖 Maia Update: Maia Can Now Ask You Questions

Maia can now ask you targeted questions mid-conversation to better understand what you need before taking action.

Why is this helpful? When planning a pipeline or working from vague requirements, Maia sometimes needs more context to get things right. Instead of guessing or asking you to type out clarifications, Maia now presents clear, structured questions—helping it clarify ambiguous requests and narrow down your intent during planning mode.

What's new:

• Single and multi-select questions: Choose from predefined options, or provide your own answer with the "Other" option
• Multi-step forms: When Maia needs to ask several things, questions are presented one at a time with step-by-step navigation—no wall of text

How do I use it? When Maia needs more information during a conversation, a question card will appear directly in the chat.

💬 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.

Welcome back to the Matillion New Features Blog! This week, we're excited to introduce powerful new capabilities for Maia and significant enhancements to pipeline quality management. From AI-powered table mentions and specialized sub-agents to automated quality fixes and reusable skills, these updates are designed to make your data workflows more efficient and intelligent. For a full list of recent changes, be sure to check our changelog updates.

🧠 Maia Update: Skills Are Here

We're happy to introduce skills — a way to extend Maia with reusable, specialized knowledge for your projects. Skills give Maia step-by-step guidance for specific tasks, so it follows your team's best practices every time.

Complex or domain-specific tasks often need detailed, consistent instructions that go beyond what an AI assistant knows out of the box. Skills let you encode proven approaches once and have Maia apply them automatically whenever they're relevant.

What's new:

• Built-in skills: Maia ships with curated built-in skills for common tasks, such as Iterator Components guidance for building pipelines that loop over data, retry on failure, and more. We'll be adding more built-in skills over time.
• Project skills: Create your own custom skills by adding a SKILL.md file to your project's .matillion/maia/skills/ directory. Encode project-specific patterns, conventions, or step-by-step procedures that Maia will follow.
• Automatic activation: When a task matches a skill, Maia activates it automatically — no manual steps needed. You'll see which skill is being applied as Maia works.

How to use it: Built-in skills work automatically. To create your own, add a folder under .matillion/maia/skills/ in your project with a SKILL.md file containing a name, description, and instructions. Maia will discover and use it in future conversations. For more information, read the Skills documentation.

🤖 Maia Update: @ Mention Your Database Tables in Chat

We're happy to introduce a new way to work with your data in Maia — you can now reference specific tables directly in chat using @ mentions.

Why is this helpful? If you already know which tables you want to work with, @ mentions let you reference them precisely — no ambiguity. And if you're not sure exactly what you're looking for, Maia still has you covered — just describe what you need and it'll find the right tables for you.

What's new?

• Table mentions: Type @ in the chat to reference specific tables directly.
• Search-driven navigation: Results load as you search — drill down through databases and schemas to find the table you need.
• Full path support: Build precise references using dot notation (e.g. @DATABASE.SCHEMA.TABLE).
• Multi-platform: Works with Snowflake, Redshift, and Databricks.

How do I use it? Type @ in the Maia chat input to open the mentions picker. Search and drill down through your databases and schemas to select the table you want to reference.

🎉 Pipeline Quality Reviewer Improvements

Three new pipeline quality features are now available to help you maintain higher code quality and streamline your development workflow within the Data Productivity Cloud.

• Maia Autofix leverages AI to automatically detect and fix common pipeline quality issues. When Maia identifies fixable problems such as incorrect component naming, missing start/end components, or unused components, it will plan the necessary fixes and request your confirmation before applying changes. This allows you to resolve common issues in seconds rather than spending time manually editing components across multiple pipelines.
• Review All enables you to validate multiple pipelines simultaneously. You can now review all pipelines in your project against quality rules to efficiently identify issues across your entire codebase, saving significant time when managing large projects.
• Pre-commit Review helps prevent quality issues from reaching your main codebase. By enabling pre-commit review via a checkbox in the commit modal, the system will automatically check for pipeline quality rule violations. Any attempted commits with error-level violations will be blocked, ensuring your main branch stays clean and maintains high quality standards.

For more information about all our pipeline quality features, 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 share updates that will streamline your setup process and enhance your data integration capabilities.

Want a more detailed look at the latest new features and improvements in the Maia Foundation? Check out our most recent changelog updates.

🔗 Account-Level API Credentials

API credentials in the Maia Foundation just got more flexible than ever! We’ve removed the limit on the number of API credentials you can have in a Maia Foundation account, and you can now assign each set of API credentials a specific role at the account level.

This gives you more control over your API credentials, making integration safer and providing clearer separation between different tasks. For more details, read our API credentials documentation.

🤖 Export Hybrid Agent Logs

For customers using a Maia Foundation Hybrid agent, we’ve added a new Export logs agent parameter that automatically sends logs from your agent to Matillion. This means that if you need to contact Matillion Support, we’ll be able to respond more quickly as we’ll have relevant information to hand right away.

For more information, read the Export logs documentation.

🔐 Improved SSO Experience

We've made significant improvements to our Single Sign-On experience to make it quicker and simpler to set up SSO.

• Our SSO setup guide has been fully restructured, and we’ve added new step-by-step instructions with screenshots for Entra ID and Okta, our two most common SSO providers. In addition, we’ve added significantly more detail to our instructions for DNS record creation and testing.
• In the event that something isn’t quite right, we’ve reviewed and expanded the potential SSO-related error messages you could see. These now provide clear, detailed guidance to configure and troubleshoot SSO independently, enabling faster setup and reducing the need for assistance.

💬 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.