Inputs & Secrets

A task can use manual inputs, trigger data, earlier step outputs, table data, and reusable values provided by an administrator.

Inputs

Create clear inputs for values that change on every run, such as an owner, date range, or file. Add a useful name, description, and example so that another member can run the task safely.

When a fixed value is reused across many steps, use a reusable value if that feature is available. Its management location and editing permission depend on workspace settings.

Secrets

Do not paste API keys, passwords, or private keys into ordinary fields or task descriptions.

• Authenticate external apps through App integrations.
• Enter a key only in a field explicitly designed for a secret.
• Never paste secrets into chat, task names, comments, or normal run inputs.
• Check screenshots, recordings, and exports for confidential values before sharing.
• If exposure is possible, revoke and rotate the secret at its source immediately.

Masked display helps protect a stored value, but you must still confirm where it is entered and who can use it.