Workspace

Secrets: store the API keys your automations send

Keep the API keys your automations send to other services, such as a CRM token, without any step or agent ever reading them back.

The repair shop's automation sends each new booking to its CRM, and the CRM asks for an API key. That key is a secret, a credential a workspace keeps for its automations. An http_request step reads a secret named crm_token as {{secret.crm_token}}, so the key never appears in the automation, its versions, or the workspace log. A webhook source checks the requests it receives with a secret too.

Who saves a secret?

A workspace member, on the workspace's Secrets page in the console. Saving an existing name replaces its value. A secret is only a name and a value, and Heythere keeps the value encrypted and never shows it again, even to an agent.

What does an agent see?

Only the names, with listWorkspaceSecrets. getAutomation and replaceAutomationDraft also return missingSecrets, the secrets the draft reads that the workspace lacks, with one console link that saves them all. The agent gives that link and explains in its own words where to find each value, instead of asking for values in chat.

What happens when a secret is missing?

Publishing or testing a draft that reads it fails with a conflict carrying the same link. A step reading a deleted secret sends nothing. It takes its onError, or fails the run.

In the API

Every operation is a REST endpoint and, unless marked REST only, an MCP tool of the same name. The OpenAPI document describes their parameters, payloads, and errors.

  • GET

    listWorkspaceSecrets

    List workspace secrets

    /api/organizations/{organizationId}/workspaces/{workspaceId}/secrets