Docs - sync vercel env vars

docs/config/config-file.mdx

@@ -471,7 +471,7 @@ These environment variables are only used during the build process and are not e
 
 #### syncEnvVars
 
-The `syncEnvVars` build extension replaces the deprecated `resolveEnvVars` export. Check out our [syncEnvVars documentation](/deploy-environment-variables#sync-env-vars-from-another-service) for more information.
+The `syncEnvVars` build extension replaces the deprecated `resolveEnvVars` export. Check out our [syncEnvVars documentation](/deploy-environment-variables#sync-env-vars-from-another-service) for more information and example usage (including syncing environment variables from Infisical and Vercel).
 
 #### audioWaveform
 

docs/deploy-environment-variables.mdx

@@ -123,6 +123,10 @@ export default defineConfig({
 });
 ```
 
+#### Syncing environment variables from Vercel
+
+To sync environment variables from your Vercel projects to Trigger.dev, check out our [syncing environment variables from Vercel example](/guides/examples/vercel-sync-env-vars).
+
 #### Deploy
 
 When you run the [CLI deploy command](/cli-deploy) directly or using [GitHub Actions](/github-actions) it will sync the environment variables from [Infisical](https://infisical.com) to Trigger.dev. This means they'll appear on the Environment Variables page so you can confirm that it's worked.

docs/guides/examples/vercel-sync-env-vars.mdx

@@ -0,0 +1,83 @@
+---
+title: "Syncing environment variables from your Vercel projects"
+sidebarTitle: "Syncing Vercel env vars"
+description: "This example demonstrates how to sync environment variables from your Vercel project to Trigger.dev."
+---
+
+## Overview
+
+This example shows how to automatically sync environment variables from your Vercel project to Trigger.dev.
+
+## Build configuration
+
+To sync environment variables from your Vercel project to Trigger.dev, you'll first need to add this build configuration to your `trigger.config.ts` file. This extension will then automatically run every time you deploy your project.
+
+This code syncs encrypted environment variables, filtering them based on the current environment (production, preview, or development).
+
+```ts trigger.config.ts
+import { defineConfig } from "@trigger.dev/sdk/v3";
+import { vercelSyncEnvVars } from "@trigger.dev/build/extensions/vercelSyncEnvVars";
+
+export default defineConfig({
+  build: {
+    extensions:
+     extensions: [
+      syncVercelEnvVars(),
+      syncEnvVars(async (ctx) => {
+        const environmentMap = {
+          // Account for the different environment names used by Vercel
+          prod: "production",
+          staging: "preview",
+          dev: "development",
+        } as const;
+
+        const vercelEnvironment =
+          environmentMap[ctx.environment as keyof typeof environmentMap];
+
+        const vercelApiUrl =
+          `https://api.vercel.com/v8/projects/${process.env.VERCEL_PROJECT_ID}/env?decrypt=true`;
+
+        const response = await fetch(vercelApiUrl, {
+          headers: {
+            Authorization: `Bearer ${process.env.VERCEL_ACCESS_TOKEN}`,
+          },
+        });
+
+        if (!response.ok) {
+          throw new Error(`HTTP error! status: ${response.status}`);
+        }
+
+        const data = await response.json();
+
+        const filteredEnvs = data.envs
+          .filter(
+            (env: { type: string; value: string; target: string[] }) =>
+              env.type === "encrypted" &&
+              env.value &&
+              env.target.includes(vercelEnvironment),
+          )
+          .map((env: { key: string; value: string }) => ({
+            name: env.key,
+            value: env.value,
+          }));
+
+        return filteredEnvs;
+      }),
+    ],,
+  },
+});
+```
+
+<Note>
+  [Build extensions](/config/config-file#extensions) allow you to hook into the build system and
+  customize the build process or the resulting bundle and container image (in the case of
+  deploying). You can use pre-built extensions or create your own.
+</Note>
+
+## Running the sync operation
+
+To run the sync operation, simply run the `deploy` command. You should see some output in the console indicating that the environment variables have been synced, and they should now be available in the Trigger.dev dashboard.
+
+```bash
+npx trigger.dev@latest deploy
+```

docs/mint.json

@@ -316,7 +316,8 @@
         "guides/examples/supabase-storage-upload",
         "guides/examples/react-pdf",
         "guides/examples/resend-email-sequence",
-        "guides/examples/vercel-ai-sdk"
+        "guides/examples/vercel-ai-sdk",
+        "guides/examples/vercel-sync-env-vars"
       ]
     },
     {