Custom secrets

Custom secrets are any sensitive authentication/authorization data that you can use in a workflow. Some common examples of secrets include, but are not limited to: 

• Key
• Password
• User name
• API token/key
• SSH keys

How are custom secrets protected?

Torq uses Google KMS to store the secrets, providing strong, out-of-the-box encryption and compliance with FIPS 140-2 L3 validated HSM. The credentials are used strictly by the program and never displayed or saved in logs to maintain confidentiality. 

Create a custom secret

There are two ways to create a new custom secret. 

From the workflow

1. Add the step in which sensitive data is required to the workflow.
2.  In the step input field where you want to enter the sensitive data, type: $.secrets.. Autocomplete will show all the available secrets. 
3. Click Create new secret.
4. Enter a meaningful secret name, for example {vendor}_api_key.
5. Enter the secret value (information that you want to protect).
6.  Click Add.

Custom secrets integration

1. Go to Integrations > Steps and locate Custom Secrets.
2. Click Add.
3. Enter a meaningful Secret name, for example, {vendor}_api_key.
4. Enter the Secret value (information that you want to protect).
5. Click Add. 

Use a custom secret in a workflow

When you want to pass the secret value in a step, you access the secret from $.secrets