You can now use the "kind":"mcp" tag to monitor queries sent by the Sigma MCP server. This can be helpful to monitor costs or usage associated with the MCP server.
See Monitor MCP queries for more information.
You can now create and use AI columns on Databricks connections.
AI columns allow you to construct dynamic prompts that reference specific table columns, which can be helpful for tasks like enriching, summarizing, and classifying data.
Build agentic solutions natively in Sigma with Sigma agents. Agents provide AI capabilities to a dashboard or application based on a predefined context of the data elements in a workbook. Instructions and data sources provide context to the agent, while actions, warehouse agents, warehouse search services, and MCP tools provide tools for an agent to take action or enrich insights.
You can now create AI columns to enrich your data using natural language prompts. AI columns allow you to construct dynamic prompts that reference specific table columns, and can be helpful for tasks like enriching, summarizing, and classifying data.
Amazon Bedrock is now a supported AI provider, letting you use Anthropic foundation models with Sigma AI-powered features.
For setup instructions, see Add Amazon Bedrock as an AI provider.
Sigma Public is now available as a free-to-use platform where you can create, share, and explore apps built in Sigma. Use sample data or upload your own datasets to build workflows in an embedded Sigma experience. You can also search apps created by other users to get inspiration for your next app in Sigma.
The List data model sources (GET /v2/data-models/{dataModelId}/sources), List workbook sources (GET /v2/workbooks/{workbookId}/sources), and List report sources (GET /v2/reports/{reportId}/sources) endpoints now include custom SQL elements in the response. Custom SQL elements are listed with a type of custom-sql and include a customSqlId field.
You can install agent skills for Sigma to help AI assistants authenticate to the Sigma REST API and create Sigma documents as code.
For more information, as well as access to the public skills repository, see Install skills for AI assistants.
Set up a specific OAuth configuration to authenticate to a Snowflake or Databricks connection without reusing the OAuth configuration used to authenticate to your Sigma organization.
For Snowflake or Databricks connections, you can configure connection-level OAuth to manage role-based access control and data permissions in your data platform without changing how users authenticate to Sigma.
API connectors now support the AWS signature V4 authentication method.
For more information, see Configure API credentials and connectors in Sigma.
Ask Sigma is now Sigma Assistant, and includes the following:
Input table audit history records versioned snapshots of input table row and schema changes over time. For each input table, Sigma automatically creates a warehouse-native view in your data platform that can help you understand the following:
If you use a warehouse-hosted AI provider with a Snowflake connection, and your Snowflake account is hosted on AWS, Sigma now uses claude-sonnet-4-5 as the LLM.
For more details, see Configure a warehouse-hosted model as AI provider.
Admins can now add an Azure Blob Storage integration to use customer-owned cloud storage with the following features:
email option for the List members endpointThe List members (GET /v2/members) endpoint includes a new option to filter the list of users by email address. Use this option instead of the search option.
CSV upload using a customer-owned cloud storage data flow is now generally available. This option offers an alternative to the default data flow through Sigma’s infrastructure.
When customer-owned cloud storage is enabled, raw and processed CSV files are staged in a customer-owned bucket (instead of a Sigma-owned bucket) before loading to the data platform. Your company controls the bucket region, access, TTL, etc., helping your organization meet security and compliance requirements.
Scheduled action sequences are workflows that run automatically on a schedule, without requiring a user to open or interact with the workbook. You can use scheduled action sequences to periodically send notifications, refresh data, write to input tables, and more.
You can create actions that call API endpoints in Sigma workbooks. This allows you to trigger workflows, enrich data, and interact with external systems without leaving Sigma. See Create actions that call API endpoints.
To support the Call API action, you can define API credentials and API connectors directly in Sigma, using diverse authentication methods, dynamic query and path parameters, request bodies with typed variables, and more. You can optionally create a connector from an existing OpenAPI specification. See Configure API credentials and connectors in Sigma.
You can add CC and BCC recipient lists for email notification actions in workbooks. For more information, see Create actions that send notifications and export data.
CSV upload can now use a customer-owned cloud storage data flow instead of the default data flow through Sigma’s infrastructure.
When customer-owned cloud storage is enabled, raw and processed CSV files are staged in a customer-owned bucket (instead of a Sigma-owned bucket) before loading to the data platform. Your company controls the bucket region, access, TTL, etc., helping your organization meet security and compliance requirements.