Skip to main content

​
Overview

Pre-built credentials pre-fill the secret name and keys for built-in integrations. Pre-built credentials

​
How pre-built credentials work

Built-in integrations expect fixed secret names and keys. For example, Slack SDK actions use slack and SLACK_BOT_TOKEN. ${{ SECRETS.slack.SLACK_BOT_TOKEN }} resolves from the workflow default environment unless overridden in action control flow.

​
Use environments

Store the same credential name in different Workflow environments:
  • slack in default for one Slack app
  • slack in staging for a second Slack app
  • slack in customer_acme for a customer-specific Slack app
Then set the Workflow environment in Workflows or override it on a specific action in Actions: 
${{ SECRETS.slack.SLACK_BOT_TOKEN }}

​
Configure a credential

In /Credentials, click Configure for the credential. Tracecat pre-fills the keys. Configure Slack credential
  • See Secrets for the core secret model and secret expression syntax.
  • See OAuth for integrations that issue managed OAuth tokens instead of static keys.
  • See MCP servers for MCP-specific integration setup and secret-backed stdio configuration.