API keys, tokens, and passwords give access to your accounts at other services. If one is stored as plain text in a table, a column, a workflow step, or a screen, anyone who can edit your app can see it, and in many cases it is also sent to your users' devices along with the rest of your app's data.
This guide shows you where credentials usually end up in a Glide app and how to check each place.
What to look for
Credentials don't always have obvious names. Look for these words in table names, column names, and values:
Names: api, key, api_key, apikey, token, access token, refresh token, secret, client secret, client ID, password, pass, pwd, auth, authorization, bearer, credential, private key, webhook
Values that look like credentials: long strings of random letters and numbers (usually 30 characters or more), and values that start with
Bearer,Basic,sk-,sk_live_,AIza,xoxb-,ghp_, oreyJWebhook URLs: links such as
hooks.slack.com/services/…,hook.make.com/…, orhooks.zapier.com/…. Anyone who has one of these links can send data to it, so treat them like keys.
1. Check your tables
Credentials often live in a table that holds app-wide settings. Common names for these tables include:
Config, Configuration, Settings, App Settings, Setup
Admin, System, Globals, Constants, Variables, Parameters
Env, Environment, Keys, Secrets, Credentials, API, Integrations
Also check your Users table. It sometimes holds per-user tokens or passwords in columns like token, access_token, or password.
For each table:
Open the Data Editor and select the table.
Click the search box in the toolbar (or press Cmd+K on Mac / Alt+K on Windows) and type one of the names above to find matching columns.
If your search box shows Data and Columns options, switch to Data to search the values in the table as well, for example for
sk-orBearer.Scroll through any small settings table row by row. These tables usually have only a few rows, and a key can sit in a column with an unrelated name.
If your table comes from Google Sheets, Excel, or Airtable, the credential is also stored in that file or base. Check it there too.
2. Check computed columns
A key can also be typed directly into a column's configuration, where it doesn't show up as a value in the table. Open the configuration of these column types and look for typed-in credentials:
Template: often used to build text like
Bearer sk-…or a URL that includes a keyConstruct URL: look at the query parameters, for example
key=ortoken=JavaScript and other code columns: look in the code itself
Call API columns: look at the Endpoint and Body, and at any header or query value that uses a column
3. Check your workflows and actions
Open the Workflows tab and go through each workflow, including App Interaction, Schedule, Webhook, and Manual workflows. Also check actions set directly on buttons and other components. In each one, look at:
Call API steps: the Endpoint (keys are often added to the URL, like
?api_key=…), the Body, and any Headers or Query string value that uses a column. Values typed directly into Headers and Query string are already saved as Secret values, so they are fine.Trigger webhook steps and other integration steps that send data to an outside service: the webhook URL and the data you send
Open link steps: URLs that include a key or token
Set column values and Add row steps: typed-in values that write a key into a table
4. Check your screens
Less often, credentials are typed into components. Check Web Embed URLs, Text and Rich Text components, and the code of any Custom components.
What to do when you find a key
Replace the key at the service. Create a new key in the service's dashboard and turn off the old one. A key that was stored as plain text may already have been seen, so moving it isn't enough.
Store the new key as a Secret value. In a Call API action, step, or column, put the key in Headers or Query string and choose Secret as the value. If a built-in integration has its own API key field, use that field instead. Both keep the key encrypted on Glide's servers and off your users' devices. For step-by-step instructions, see Store API Keys and Other Credentials Safely with Secret Values.
Remove the old copy. Delete the value or column from your table, and from your Google Sheet, Excel file, or Airtable base if your table comes from one. Remove it from any Template, Construct URL, code column, workflow step, or component where you found it.
Test. Run the action or workflow and make sure the service still responds as expected.
If each user has their own token (for example, in the Users table) and it can't be moved to a Secret value, add Row Owners to that table so each user's device only receives their own row.
