Glossary
Definitions of Retool terminology.
A
App IDE
The web-based interface for building web and mobile apps.
Asynchronous workflows
A workflow that does not have a webhook response block or a workflow that is triggered from a schedule, Retool Event, or workflow IDE.
B
Base64
Binary data that is encoded as an ASCII-formatted string. You can use Base64-encoded values anywhere in Retool that accepts strings. Use btoa() to encode a string of binary data as Base64 or atob() to decode a Base64-encoded string.
Beta
The feature is currently in active development and subject to change. Beta features are available for you to use but some functionality may not yet be complete or fully functional.
Blob
Raw data that is temporarily available. Blobs are strings that can be referenced anywhere in Retool apps and can be converted to Base64-encoded data using utils.getDataByObjectURL().
Block
A block of code, such as an SQL query or JavaScript statement, that runs within a workflow.
Bottom sheet
A modal for mobile apps that slides into view from the bottom of the viewport.
C
Canvas
The area of the IDE in which you build the user interface for your app. The canvas can contain distinct frames, such as the sidebar or header.
Cloud-hosted Retool
A Retool-hosted organization that is accessible over the internet.
Component
A prebuilt interface element to display data, and manipulate or interact with it based on user actions.
Configuration Variables
Environment-specific values and secrets that you can reference in Retool resource configurations, apps, workflows, and queries.
Control flow
The order of operation and flow of data between workflow blocks.
CORS
Cross Origin Resource Sharing. The method to determine which origins other than its own (e.g., Retool) are allowed access via a web browser.
CRUD
Create, read, update, and delete are the four main operations involved in data storage.
Current working version
The version that reflects the current state of the app or workflow.
D
Data source
Somewhere you store data. This could be a PostgreSQL database, a REST API, etc.
Dependency graph
The method with which Retool maintains all property values and where they're referenced. Whenever a property changes, all downstream references automatically update.
E
Embedding
A type of vector used by AI models to determine meaning and connections.
End user
An enabled user who did not build or edit an app or workflow during the billing cycle. End users are billed at a lower rate than standard users.
Event handler
A method to trigger queries, control components, and perform other actions in response to user interactions.
External user
Enabled users who are not part of your organization. External users do not build or edit apps or workflows. External users are typically billed using custom pricing.
I
Instance
A single deployment of Retool. Self-hosted organizations can deploy multiple instances of Retool, if necessary.
L
Live version
The published release of an app or deployed release of a workflow.
M
Media type
The media type that indicates the purpose and format of data (e.g., application/pdf for PDF files).
Modal
A content area that appears above other content, such as a dialog box.
Multitenancy
O
Organization
Organizations are how Retool group users, apps, resources, etc. Each Retool user is a member of an organization. Organization admins can add or remove users, manage access, and change its configuration.
P
Private beta
Organizations can sign up to the waitlist to request access to private beta functionality.
Private beta
Organizations can contact their Retool account manager to request access to private beta functionality.
Public beta
Admins can enable public beta features in their organization's Beta settings.
Q
Query
A block of code that interacts or manipulates data, such as an SQL query or API request.
R
Resource
A saved set of user-configured properties that determine how Retool connects to data source. You create a resource for each data source you want to use with Retool.
S
Scope
The level of access granted. If you crete a custom OAuth application with which to authenticate, you typically define scopes to give Retool access, such as calendars.read or users.add.
Screen
The primary content areas of a mobile app that contain components. Users navigate between screens using the tab bar or by interactions that trigger event handlers, such as pressing a button or selecting an item from a list.
Security hardening
A process intended to eliminate a means of attack by patching vulnerabilities and turning off nonessential services.
Self-hosted Retool
An instance of Retool that is deployed on-premise or in a virtual private cloud (VPC).
Standard user
An enabled user who built or edited an app or workflow during the billing cycle.
Synchronous workflows
A workflow that has a webhook response block and is triggered from an App, Workflow, or webhook
T
Toolscript
A JSX-style markup language built to serialize Retool apps which are protected using Source Control.
Topic
The scope for recipients for push notifications. Topics are similar in function to mailing lists—users subscribe to them based on what information they want to be notified about.
Transformer
Reusable blocks of JavaScript code to transform data that can be referenced anywhere in an app.
V
Vector
A mathematical representation of an object, such as a block of text.
Vector database
A data store for unstructured text to use with AI models.
W
Workflow IDE
The web-based interface for building workflows.