Create actions that send notifications and export data

You can create workbook actions that initiate direct downloads as well as exports to email, Slack channels, Microsoft Teams Channels, Microsoft SharePoint, webhooks, and cloud storage.

For email and Slack, you can create actions that send notifications to users and channels. These notifications can be configured independently of an export, and support both static and dynamic lists of users.

This document explains how to create actions that export workbook content to specific destinations or notify users by Slack and email. For more information about configuring these actions in Sigma, see Intro to actions. For more information on exporting data, see Export data.

User requirements

Send notifications by email (Beta)

Create an action that emails selected recipients, without sending an attachment or export.

📘

This action can only be configured and triggered by users assigned an account type with the Export to email permission enabled.

Send notifications by Slack (Beta)

Create an action that sends a Slack message to selected recipients, without sending an attachment or export.

To create a Slack notification action, the Slack integration must be enabled for your organization. If you want to send notifications to a private channel, you must also add Sigma to the private channel. See Adding Sigma to a private Slack channel.

📘

This action can only be configured and triggered by users assigned an account type with the Export to Slack permission enabled.

💡

When sending to Slack channels, Sigma recommends using channel ids rather than channel names. For more information, see Format a slack message.

Download a file

Create an action that downloads an entire workbook, a specific page, or an individual element directly to the interacting user’s device.

📘

This action can only be configured and triggered by users assigned an account type with the Download permission enabled.

• Action	Select Notify and export.
  Destination	Select Download.
  Attachment	Select the workbook content to download, then choose a file format.

Export to email

Create an action that emails an entire workbook, a specific page, or an individual element to selected recipients.

To configure a standard export to email that is not managed by a workbook action, see Export to email.

📘

This action can only be configured and triggered by users assigned an account type with the Export to email permission enabled.

Export to Slack

Create an action that exports an entire workbook, a specific page, or an individual element to Slack.

To create a Slack export action, the Slack integration must be enabled for your organization. If you want to send notifications to a private channel, you must also add Sigma to the private channel. See Adding Sigma to a private Slack channel.

📘

This action can only be configured and triggered by users assigned an account type with the Export to Slack permission enabled.

💡

When sending to Slack channels, Sigma recommends using channel ids rather than channel names. For more information, see Format a slack message.

Export to Microsoft Teams (Beta)

Create an action that exports an entire workbook, a specific page, or an individual element to Microsoft Teams.

To create a Teams export action, the Microsoft integration must be enabled for your organization. To send notifications to a channel, you must also add Sigma to the channel. See Add the Sigma Notifications app to Teams.

📘

This action can only be configured and triggered by users assigned an account type with the Export to Microsoft Teams and SharePoint permission enabled.

Export to SharePoint (Beta)

Create an action that exports an entire workbook, a specific page, or an individual element to Microsoft SharePoint.

To create a SharePoint export action, the Microsoft integration must be enabled for your organization.

📘

This action can only be configured and triggered by users assigned an account type with the Export to Microsoft Teams and SharePoint permission enabled.

Export to a webhook

Create an action that exports an individual element’s data to another application with a webhook.

📘

This action can only be configured and triggered by users assigned an account type with the Export to webhook permission enabled.

• Action	Select Notify and export.
  Destination	Select Webhook.
  Endpoint	Enter the receiving application’s endpoint.
  Attachment	Select an element to export, then choose a data format.

Export to cloud storage

Create an action that exports an individual element’s data to cloud storage.

📘

This action can only be configured and triggered by users assigned an account type with the Export to cloud permission enabled.

• Action	Select Notify and export.
  Destination	Select Cloud Storage.
  Storage integration	Enter an integration name.
  Cloud Storage URI	Enter a file path for the export destination.
  Element	Select an element to export, then choose a file format.
  More options	[optional] Select the Prefix file name with current date and time checkbox to include the export date and time (in ISO format) in the file name.

Example: Slack notification workflow for new project tasks

You can configure workbook actions that send notifications to users about changes to a workbook, such as new data entry or changes to existing data.

In this example, imagine you're interacting with a project tracker data app. Users can add new projects, tasks, and statuses.

You decide to configure a workbook action to send a notification whenever a user assigns a new task. Currently, users add tasks by selecting Add Task, entering information into the provided modal, and clicking the Create Task button to add the task to an input table.

Using the Notify and export action, you can send a notification by Slack whenever someone clicks the Create Task button, so that users are always up to date when a task is assigned to them.

1. Navigate to the Create Task modal, and open the Actions panel.
2. Add an action to the On click - primary action sequence.
3. In the Action modal, configure the action:

4. [optional] Click More to add a condition to the Action sequence. In the example below, the condition IsNotNull([ct-Task-Name]) prevents tasks from being published with a blank name.