Skip to content

Keys

Who can do this

Anyone with Create and change automations can add, change and delete keys. Everyone else can see which keys exist and where they're used, but never a key's value.

A key is an API key, token or password that one of your workflows needs to call another service: an AI model, an OpenAI or Anthropic account, a Shopify store, an internal API.

Save it here once instead of pasting it into a task. Then type {{key:name}} wherever the key goes in a Code or Webhook Out task, exactly as the other service's documentation shows it. BaseCloud fills the key in when the task runs. The key itself never appears in a task, in a workflow copy, in a run's output, or on any screen, and the AI assistant can build workflows that use it without ever seeing it.

Open Settings → App Connections & Keys, then the Keys tab.

You can also ask an AI app connected to BaseCloud to save a key, or to move a key typed into your tasks into Keys.

Add a key

  1. Click Add Key.
  2. Give it a Name you'll recognise, such as Anthropic. BaseCloud turns the name into what your tasks type, such as {{key:anthropic}}. The form shows it as you type.
  3. Paste the Key.
  4. Click Add Key.

The key is never shown again

BaseCloud stores the key encrypted and never displays it, not even to you. Keep your own copy somewhere safe if you'll need it outside BaseCloud.

Use a key in a task

Type {{key:name}} where the key goes. Everything else stays the way the service's own documentation writes it.

In a Python Code task:

res = requests.post(
    'https://api.anthropic.com/v1/messages',
    headers={'x-api-key': '{{key:anthropic}}', 'anthropic-version': '2023-06-01'},
    json={'model': 'claude-sonnet-4-6', 'max_tokens': 1024, 'messages': [{'role': 'user', 'content': 'Hello'}]},
)
return res.json()

In a JavaScript Code task:

const res = await fetch('https://api.openai.com/v1/responses', {
  method: 'POST',
  headers: { Authorization: 'Bearer {{key:openai}}', 'Content-Type': 'application/json' },
  body: JSON.stringify({ model: 'gpt-4.1-mini', input: 'Hello' }),
});
return await res.json();

In a Webhook Out task, put it in a header value (such as Authorization set to Bearer {{key:openai}}), in the URL (?api_key={{key:maps}}) or in the body.

Under Input, a Code or Webhook Out task lists your keys. Click one to copy it, or drag it to where it goes.

Keys are filled in first

A key is filled in before any other variable. If a form answer, an email or another task's output happens to contain {{key:…}}, it stays as plain text and is never replaced with a key.

How your keys are protected

  • Hidden in everything a run keeps. If a key turns up in what a run produces — something your code prints or returns, a service's answer, an error message — BaseCloud replaces it with [withheld] before the run's output or any log stores it. This includes encoded copies. The run's output says how many were withheld.
  • Never saved in a task. Tasks hold only {{key:name}}. The value is added as the task runs and isn't kept.
  • Encrypted at rest. The key is stored encrypted, and only decrypted for a run that uses it.
  • Only Code and Webhook Out. No other task can use a key, so it can't be put into an email, a text message or an AI prompt.
  • Webhook Out keeps it on its way. A Webhook Out request that carries a key doesn't follow redirects, so the key can't be passed on to another address, and is never sent to a private or internal network address.

Anyone who can change your automations can use your keys

A task that uses a key can send it anywhere it sends requests. Give Create and change automations only to people you'd trust with the keys themselves, and check a task you didn't write before you switch it on.

Where a key is used

Each key in the list shows what tasks type for it, how many tasks use it and when it was last used. Click the number of tasks to see which workflows, and click one to open it.

A task counts as using a key when one of its settings, or its code, contains {{key:name}}. Only workflows that are switched on are counted.

Each run that used a key also records it in its output, under keys: which keys, and anything withheld. If a task types a name that isn't one of your keys, the output says so. A Code task keeps the text as written; Webhook Out leaves it out, like any variable it can't fill.

Change a key

Click the Edit icon to rename it.

  • To replace the key itself, paste the new one under Replace the key. Leave it empty to keep the saved one. Tasks pick up the new key on their next run.
  • What tasks type for the key can't change while a task uses it, because those tasks would stop working. Add a new key instead, and change the tasks to use it.

Delete a key

Click the Delete icon. If tasks use it, BaseCloud says how many first. After it's deleted, those tasks no longer get the key and their requests will fail.

Troubleshooting

What you see What to do
No key is called "…" in the run's output Check the name in the task against the Keys list, or add the key. Names use lowercase letters, digits and _.
The service says the key is wrong, and the run's output has no keys The task doesn't contain {{key:name}}. Type it where the key goes instead of the key's name on its own.
Keys are not set up on this server yet. Contact BaseCloud support.

Keys saved before 7 November 2026

Older keys may also have web addresses saved with them. Those still work with bc.fetch(url, { key: 'name' }) in Code. Typing {{key:name}} works for every key and is the simpler way.