Skip to main content

Now Available for All Customers who can use Scripting

We're excited to announce the general availability of Secrets for Automations! You can now securely store and use sensitive information like API keys, passwords, and tokens in your Automation scripts without exposing them in plain text.

Why Secrets Matter

When connecting to external services in Run Script Actions, you may need to include sensitive credentials directly in your script code. This created potential security risks, as anyone with Editor access to your base could view these credentials.

With Secrets, you can now:

  • Store sensitive information securely in Builder Hub
  • Share access selectively with specific user groups (for customers on Business and above)
  • Use the same secrets across multiple bases and automations
  • Prevent unauthorized viewing of secrets or editing of scripts containing secrets

How Secrets Work

Creating and Managing Secrets

 

AD_4nXfe2Ok32Tpld30AwTZbD2huEJX9DFxOW5LqmOrESgUWWTDIaTOQxfoVwd9Rwdfnhn2wtIZwehVN6kQ8ZR9QXLJOqj2jLNpDAYI4ap-hTiLvOTnrdrIeUUhI-2LhjABhND13nQ4n9A?key=liuDvzIN4eqb-NTNILhhji4V

Secrets are stored in your Builder Hub, accessible from your account menu or directly at airtable.com/create/secrets. From here, you can:

  • View all secrets you have access to
  • Create new secrets with secure values
  • Share secrets with specific user groups
  • Edit secrets you've created

Using Secrets in Automations

When building a Run Script action, you'll now see a "Secrets" tab in the script editor where you can:

  1. Add existing secrets to your script
  2. Create new secrets directly from the script editor
  3. Access secret values in your code using input.secret('your-secret-name')

Enhanced Security Controls

Scripts containing secrets have special protections:

  • Only users with access to all secrets in the script can edit it
  • Other editors can still run the automation but cannot view secret values
  • Secrets are automatically redacted from console outputs to prevent accidental exposure

Getting Started

To start using Secret Management:

  1. Navigate to any automation with a Run Script action
  2. Click on the "Secrets" tab in the script editor
  3. Add your first secret by clicking "Add new secret"

Alternatively, manage all your secrets centrally in the Builder Hub at airtable.com/create/secrets.

Looking Forward

We’re looking forward to seeing what you build with secrets! Over the next few weeks we will rollout further improvements to Builder Hub that will allow you to audit which scripts are using which secrets.


 

This is a great feature. It starts to tighten up the problem of hard-coded API keys - which is a necessity, really, when using Airtable with any external service. Will you guys be extending the functionality here to Scripting extensions?

For our use case, this would be huge. It’s already fairly easy to restrict access to Automation code - what’s much more difficult is granting a user (employee in our case) the ability to manually run a script, and simultaneously restrict access to that script’s code - code which might contain a hard-coded API key.

From our perspective, this single feature - the ability to secure API keys in Scripts - would extend the utility and lifespan of the entire Airtable platform for us immensely.

This is indeed a remarkable feature that significantly reduces the burden on script developers in managing credentials securely.

​@emily_houlihan Could you please provide further details regarding the maximum number of secrets that can be stored?

👍

Reply


Terms & Conditions