Skip to main content

Tell a task which secret to use

When a task can reach several secrets of the same kind, such as two Jira sites, say which one to use. A task asks for a secret by its runner path: where the secret lives, then its name, such as org/jira. Naming the path in the task's description is safe: it carries no value, only where to find it.

Who can do this: anyone, for the secrets they can see. The task can use the secret only if it may receive it; step 3 says how to check.

  1. In the sidebar, select Directory, then the Secrets tab.
  2. Find the secret. Type part of its name in the search box, or narrow the list with the filters.
  3. Check that the task will receive it:
    • a Personal secret of yours reaches the tasks you start;
    • an Organization secret reaches tasks that Org Owners and Admins start, and tasks on the projects it is attached to;
    • any other task needs the secret attached to its project. See Attach a secret to a project.
  4. Select ⋯ at the end of the secret's row, then Copy runner path. It copies the path, such as org/jira for an organization secret, projects/<project>/jira for one that belongs to a project, or me/jira for your own.
  5. If the menu offers Copy name instead, tasks can't ask for this secret: it is a System secret, which tasks never use, or another member's personal one. Pick another secret, or ask its owner to share it with the organization.
  6. Open the task, or create one, and paste the path into its description where you say what to do, for example: "File the bug in Jira with the secret org/jira."
  7. Start the task. Its runner asks for the secret by that path when it needs it.

An organization secret&#39;s row menu: Copy runner path, Owner: Organization, Edit and Delete

Never paste the secret's value into a task: anyone who can view the task could read it.

  • How secrets work — every way a secret reaches a task.
  • Add a secret — store the connection first, with a name that says what it's for.
  • Secrets — every item in a secret's row menu.