About billable usage events

With Sigma's usage-based pricing model, your organization incurs costs through credit usage when specific types of events (or user activity) occur, including data inputs, integration actions, and report exports.

This document describes categories of billable usage events, explains how specific event types use credits, and identifies the account type permissions required to trigger these events.

💡
For information about credit pricing and billing, contact your Account Executive.

Billable usage event categories

Your organization can incur costs through credit usage when the following types of events occur.


Input	Collaborative data entry (or input table data updates in the published version of a workbook)
Integration action	Actions that call API endpoints or stored procedures
Report export	Exports generated from reports (not from workbooks)

Summary of billable usage events

The following table explains the types of events that use credits, the types that don't use credits, and how Sigma tracks credit usage for qualified events.

Event category	What does use credits	What doesn't use credits	How Sigma tracks credit usage
Input	Direct input table data updates in the published version of a workbook Input table data updates via actions executed in the published version of a workbook¹	Direct input table data updates in a workbook draft Input table data updates via actions executed in a workbook draft New input table creation² Input table duplication or copy/paste² CSV uploads to input tables²	1 input credit per row (up to 100 credits per action) Each row created, updated, or deleted in an input table is tracked as an individual event that uses a credit. However, if a single user interaction (e.g., an update row(s) action) creates, updates, or deletes more than 100 rows, the event uses a maximum of 100 credits.
Integration action	Sigma actions that call API endpoints Sigma actions that call stored procedures	Direct Sigma REST API calls that aren't triggered by actions Non-Sigma API calls (customer or third‑party endpoints) outside of Sigma that aren't triggered by actions Stored procedure calls that aren't triggered by actions (e.g., stored procedures called in table formulas)	1 integration credit per call Each API endpoint or stored procedure call triggered by an action is tracked as an individual event that uses a credit.
Report export	Reports exported to supported destinations and formats using any of the following methods: Scheduled exports sent on a schedule Scheduled exports sent on demand ("Send now") Direct download Exports initiated by actions	Exports generated from workbooks	1 export credit per unique file Each unique file generated is tracked as an individual event that uses a credit. If a report is exported as an email burst, each unique file generated for an individual email is tracked as a separate event that incurs cost. Alternatively, if an export generates a single file such that multiple email recipients receive an identical report, the export is tracked as one event.

Event category

What does use credits

What doesn't use credits

How Sigma tracks credit usage

Input

Direct input table data updates in the published version of a workbook
Input table data updates via actions executed in the published version of a workbook¹

Direct input table data updates in a workbook draft
Input table data updates via actions executed in a workbook draft
New input table creation²
Input table duplication or copy/paste²
CSV uploads to input tables²

1 input credit per row (up to 100 credits per action)

Each row created, updated, or deleted in an input table is tracked as an individual event that uses a credit. However, if a single user interaction (e.g., an update row(s) action) creates, updates, or deletes more than 100 rows, the event uses a maximum of 100 credits.

Integration action

Sigma actions that call API endpoints
Sigma actions that call stored procedures

Direct Sigma REST API calls that aren't triggered by actions
Non-Sigma API calls (customer or third‑party endpoints) outside of Sigma that aren't triggered by actions
Stored procedure calls that aren't triggered by actions (e.g., stored procedures called in table formulas)

1 integration credit per call

Each API endpoint or stored procedure call triggered by an action is tracked as an individual event that uses a credit.

Report export

Reports exported to supported destinations and formats using any of the following methods:

Exports generated from workbooks

1 export credit per unique file

Each unique file generated is tracked as an individual event that uses a credit.

If a report is exported as an email burst, each unique file generated for an individual email is tracked as a separate event that incurs cost. Alternatively, if an export generates a single file such that multiple email recipients receive an identical report, the export is tracked as one event.

Usage event permissions

The following table lists the account type permissions required for a user to trigger specific types of billable usage events.

Event type	Required account type permissions
Input	Edit input tables: Enables a user who's viewing the published version of a workbook to perform direct input table data entry and trigger actions that modify input table data. Notes: The Edit input tables* permission enables a user to enter data in an existing input table when the data entry permission is set to allow edits in the published version.* The Edit input tables permission does not enable a user to create new input tables. For information about account type permissions and workbook access required to create input tables, see Create new input tables.
Integration action	Call stored procedure actions: Enables a user to trigger an action that calls a stored procedure. Trigger API actions: Enables a user to trigger an action that calls an external API endpoint.
Report export	Create, edit, and publish reports: Enables a user to access export features, including the ability to create export schedules, send scheduled exports on demand ("Send now"), and export via direct download. Export to email: Enables a user to export reports to email recipients. Export as email burst: Enables a user to export reports as email bursts. Export to Google Sheets: Enables a user to export reports to Google Sheets spreadsheets. Export to Google Drive: Enables a user to export reports to Google Drive folders. Export to Slack: Enables a user to export reports to Slack channels. Export to Microsoft Teams and SharePoint: Enables a user to export reports to Microsoft Teams channels and SharePoint folders. Export to cloud: Enables a user to export reports to Google Cloud Storage (GCS) or Amazon S3. Export to webhook: Enables a user to export reports to webhook endpoints.

Event type

Required account type permissions

Input

Edit input tables: Enables a user who's viewing the published version of a workbook to perform direct input table data entry and trigger actions that modify input table data.

Notes:

The Edit input tables permission enables a user to enter data in an existing input table when the data entry permission is set to allow edits in the published version.
The Edit input tables permission does not enable a user to create new input tables. For information about account type permissions and workbook access required to create input tables, see Create new input tables.

Integration action

Call stored procedure actions: Enables a user to trigger an action that calls a stored procedure.

Trigger API actions: Enables a user to trigger an action that calls an external API endpoint.

Report export

Create, edit, and publish reports: Enables a user to access export features, including the ability to create export schedules, send scheduled exports on demand ("Send now"), and export via direct download.

Export to email: Enables a user to export reports to email recipients.

Export as email burst: Enables a user to export reports as email bursts.

Export to Google Sheets: Enables a user to export reports to Google Sheets spreadsheets.

Export to Google Drive: Enables a user to export reports to Google Drive folders.

Export to Slack: Enables a user to export reports to Slack channels.

Export to Microsoft Teams and SharePoint: Enables a user to export reports to Microsoft Teams channels and SharePoint folders.

Export to cloud: Enables a user to export reports to Google Cloud Storage (GCS) or Amazon S3.

Export to webhook: Enables a user to export reports to webhook endpoints.

Example usage scenarios and billable outcomes

The following table summarizes common usage scenarios and the total number of resulting billable events.

Example scenario	Credit usage tracked
A user opens the published version of a workbook and updates input table data across 10 columns in a single row.	1 credit (for the updated row)
A user opens the published version of a workbook and updates input table data in a single column across 10 rows.	10 credits (1 for each updated row)
You configure a form to trigger a condition action sequence that updates rows in an input table only when they meet the specified criteria. A user submits the form in the published version of a workbook, resulting in value updates across 20 rows.	20 credits (1 for each updated row)
While editing a workbook draft, a user uploads CSV data to an input table. The CSV file contains 1 million rows.	No credits (Input table data entry performed in a workbook draft doesn't use credits. Therefore, the number of rows uploaded from the CSV file and added to the input table is irrelevant.)
While viewing the published version of a workbook, a user submits a form. The interaction triggers an action sequence that adds a new row of data to an input table and calls a stored procedure.	2 credits (1 for the added row + 1 for the called stored procedure)
You configure a scheduled action sequence that updates 1 row in an input table at the end of each week.	1 credit per week (for the updated row)¹
You schedule a report export that sends an email burst to 125 recipients on the first day of every month. Each recipient receives an individualized report.	125 credits per month (1 for each unique file generated)
You initiate an on-demand report export that emails a report to 50 recipients. Each recipient receives the same file.	1 credit (for the single file generated)
A scheduled workbook export sends a daily Slack notification with 4 unique attachments.	No credits (Workbook exports don't use credits.)

Footnotes

Scheduled actions can only modify input tables that are editable in the published version of a workbook. If the target input table is updated to only allow edits in the workbook draft, the scheduled action sequence will be unsuccessful, and no credits will be consumed. If the input table is updated to once again allow edits in the published version, the scheduled action sequence will run successfully and credit consumption will resume. For more information, see Configure an action sequence to run on a schedule. ↩ ↩²
Functionality is supported in a workbook draft only. ↩ ↩² ↩³

Updated about 1 hour ago