Skip to main content

Workflow usage and billing

Learn about usage and billing for Retool Workflows.

Retool calculates the total number of runs for your organization and charges for billable run usage on a monthly basis. Retool also applies some limits to workflows to ensure they remain performant and prevent runaway errors.

Refer to Retool's pricing page to learn more about pricing for Retool Workflows. If you exceed the number of allotted runs for your plan, Retool notifies you with in-app notifications as well as emails. Make sure to add workflows-billing@email.retool.com as a safe or recognized email address so that emails aren't added to your spam folder.

How billing works

A run is an iteration of a workflow that is executed by Retool. There are two types of run: billable and non-billable. Your organization is only charged for billable run usage.

Billable runs

A run is considered billable if it successfully completed and was automatically triggered by one of the following:

Billable run examples
  • A webhook-triggered workflow that runs whenever a payment is received using Stripe.
  • A schedule-triggered workflow that runs daily at 9am to generate a report using Salesforce data.
  • A workflow that is run from within another workflow.
  • A workflow that is run from a Retool web or mobile app.

Non-billable runs

A run is considered non-billable if a workflow either:

  • Fails to run successfully (e.g., an error occurred).
  • Is manually run from the Workflow IDE.
  • Is triggered by a Retool event.

Retool does not charge for non-billable run usage.

Non-billable run examples
  • A workflow that failed because a query timed out and did not retrieve data.
  • A workflow currently in development that is manually run from the Workflow IDE for testing purposes.
  • A workflow that runs whenever a new user is invited to your Retool organization.

Usage monitoring

You can monitor workflow bandwidth, runs, and total number of active workflows for the current period in the Workflows section of your Retool organization.

Workflows usage example