Environment Variables

An environment variable in Node.js is accessed in your code using process.env.MY_ENV_VAR.

We deploy your tasks and scale them up and down when they are triggered. So any environment variables you use in your tasks need to accessible to us so your code will run successfully.

​

In the dashboard

​

Setting environment variables

​

Editing environment variables

You can edit an environment variable’s values. You cannot edit the key name, you must delete and create a new one.

​

Deleting environment variables

​

In your code

You can use our SDK to get and manipulate environment variables. You can also easily sync environment variables from another service into Trigger.dev.

​

Directly manipulating environment variables

We have a complete set of SDK functions (and REST API) you can use to directly manipulate environment variables.

​

Sync env vars from another service

You could use the SDK functions above but it’s much easier to use our syncEnvVars build extension in your trigger.config file.

In this example we’re using env vars from Infisical.

import { defineConfig } from "@trigger.dev/sdk/v3";
import { syncEnvVars } from "@trigger.dev/build/extensions/core";
import { InfisicalClient } from "@infisical/sdk";

export default defineConfig({
  build: {
    extensions: [
      syncEnvVars(async (ctx) => {
        const client = new InfisicalClient({
          clientId: process.env.INFISICAL_CLIENT_ID,
          clientSecret: process.env.INFISICAL_CLIENT_SECRET,
        });

        const secrets = await client.listSecrets({
          environment: ctx.environment,
          projectId: process.env.INFISICAL_PROJECT_ID!,
        });

        return secrets.map((secret) => ({
          name: secret.secretKey,
          value: secret.secretValue,
        }));
      }),
    ],
  },
});

​

Syncing environment variables from Vercel

To sync environment variables from your Vercel projects to Trigger.dev, you can use our build extension. Check out our syncing environment variables from Vercel guide.

​

Deploy

When you run the CLI deploy command directly or using GitHub Actions it will sync the environment variables from Infisical to Trigger.dev. This means they’ll appear on the Environment Variables page so you can confirm that it’s worked.

This means that you need to redeploy your Trigger.dev tasks if you change the environment variables in Infisical.

​

Dev

syncEnvVars does not have any effect when running the dev command locally. If you want to inject environment variables from another service into your local environment you can do so via a .env file or just supplying them as environment variables in your terminal. Most services will have a CLI tool that allows you to run a command with environment variables set:

infisical run -- npx trigger.dev@latest dev

Any environment variables set in the CLI command will be available to your local Trigger.dev tasks.

​

The syncEnvVars callback return type

You can return env vars as an object with string keys and values, or an array of names + values.

return {
  MY_ENV_VAR: "my value",
  MY_OTHER_ENV_VAR: "my other value",
};

or

return [
  {
    name: "MY_ENV_VAR",
    value: "my value",
  },
  {
    name: "MY_OTHER_ENV_VAR",
    value: "my other value",
  },
];

This should mean that for most secret services you won’t need to convert the data into a different format.

​

Using Google credential JSON files

Securely pass a Google credential JSON file to your Trigger.dev task using environment variables.

base64 path/to/your/service-account-file.json

GOOGLE_CREDENTIALS_BASE64="<your base64 string>"

import { google } from "googleapis";

const credentials = JSON.parse(
  Buffer.from(process.env.GOOGLE_CREDENTIALS_BASE64, "base64").toString("utf8")
);

const auth = new google.auth.GoogleAuth({
  credentials,
  scopes: ["https://www.googleapis.com/auth/cloud-platform"],
});

const client = await auth.getClient();