10 Signals

DOCUMENTATION / Team access

Team access required

Team Trigger credentials

Use the team-issued runtime key; keep deployment access with the team.

Runs on
The team's approved Trigger environment
Before you start
Team approval and the intended environment's runtime key

Which key do I need?

Request access from the team first. A customer account API key, OAuth token or deployment PAT is not a Trigger runtime key. The client uses api.trigger.dev; custom Trigger endpoints are not supported.
On this page
PurposeCredentialWho manages it
Run installed tasksTrigger environment secret keyTeam-issued; CLI configure or an approved agent secret store
Deploy task codeOperator login / TRIGGER_ACCESS_TOKENTeam administrators only; not needed by report users
Power Trigger researchOPENAI_API_KEY in the workerTeam administrators; not the user's local provider settings
Choose your terminal

  1. Request the approved runtime key

    Ask the team to authorize the intended project and environment and deliver its key through an approved secret-sharing channel. Treat it as broad trusted environment access, not a narrowly scoped customer key. Never publish it or give it to external customers.

    Request team access

  2. Verify and store after installation

    Install the client first, then enter the team-issued key at the hidden prompt. The OS credential store saves it. A verified key does not prove that tasks or provider configuration are ready; run doctor next.

    marketsignal-trigger.cmd configure

    You should see Trigger key verified and saved.

  3. Keep agent secrets separate

    For an approved agent, the team can inject TRIGGER_SECRET_KEY through its secret manager. It overrides the saved key, even after configure stores another one. Do not print it or pass it as a command argument. The CLI has one saved runtime credential, not named profiles. Linux interactive storage needs Secret Service; there is no plaintext fallback.

  4. Leave deployment and provider setup to the team

    Report users do not need Trigger operator login, a deployment PAT, a new project or provider credentials. Ask the team to deploy or promote missing tasks and configure the worker. Local Account → AI provider settings do not change Trigger.

  5. Remove or rotate access

    logout removes the local saved key only. It does not revoke the key at Trigger or unset TRIGGER_SECRET_KEY. Ask the team to revoke or rotate access, update authorized secret stores and close old agent processes.

    marketsignal-trigger.cmd logout

Troubleshooting

configure uses the wrong environment

Check whether TRIGGER_SECRET_KEY is set without displaying its value. It overrides the saved key. Ask the team to confirm the approved environment.

doctor remains PENDING_VERSION

Ask the team to inspect and promote the correct worker. Use a worker pin only when the team provides one. Reinstalling the client cannot deploy a task.

Missing tasks or provider configuration

Stop before submitting research and ask the team administrator to repair the existing project. Do not create another project or share a provider key.

Next steps

Connect the team Trigger CLI Team Trigger setup Which key do I need?
← All guides