Skip to content

Commit 754d037

Browse files
D-K-PTrigger.dev RepoOps
authored andcommitted
docs: add chat-agent example projects and Infisical Secret Sync
docs: add the Ask Trigger and ElevenLabs Voice agent example projects, and document the native Infisical Secret Sync - Two new example-project pages under Guides & examples: **Ask Trigger chat agent** (a `chat.agent()` that teaches Trigger.dev by drawing interactive node-graphs, quizzes and cards with json-render, grounded on live docs via MCP) and **ElevenLabs Voice agent** (a spoken-conversation assistant with streaming ElevenLabs STT/TTS, server-side VAD, and Head Start for a fast first reply). - Documented the native **Infisical Secret Sync** on the environment-variables page, alongside the existing `syncEnvVars` build-extension pattern. Mono-RevId: 157f7fa58eb818c1105ddfe81863b1d9a9c0e6ee
1 parent 7fb8217 commit 754d037

6 files changed

Lines changed: 593 additions & 2 deletions

File tree

docs/config/extensions/syncEnvVars.mdx

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -63,6 +63,12 @@ export default defineConfig({
6363

6464
In this example we're using env vars from [Infisical](https://infisical.com).
6565

66+
<Tip>
67+
Infisical also offers a native [Secret Sync](/deploy-environment-variables#infisical-secret-sync)
68+
that pushes secrets to Trigger.dev without a build extension or a redeploy. Use `syncEnvVars` when
69+
you want to resolve secrets at deploy time in code, or for a service without a native sync.
70+
</Tip>
71+
6672
```ts trigger.config.ts
6773
import { defineConfig } from "@trigger.dev/sdk";
6874
import { syncEnvVars } from "@trigger.dev/build/extensions/core";

docs/deploy-environment-variables.mdx

Lines changed: 23 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -184,14 +184,35 @@ For more information about the context object, see the [Context documentation](/
184184

185185
### Sync env vars from another service
186186

187-
You could use the SDK functions above but it's much easier to use our `syncEnvVars` build extension in your `trigger.config` file.
187+
There are two ways to pull secrets from another service into Trigger.dev: a native **Secret Sync** (currently [Infisical](https://infisical.com)), or the `syncEnvVars` build extension for any other service.
188+
189+
#### Infisical Secret Sync
190+
191+
If your secrets live in [Infisical](https://infisical.com), sync them natively, without a build extension or a redeploy. You configure the sync in the Infisical dashboard, and it pushes secrets straight to your [Environment Variables page](#in-the-dashboard) in Trigger.dev. When a secret changes in Infisical the sync updates the matching variable, and your tasks pick up the new value on their next run.
192+
193+
Set it up in Infisical in two steps:
194+
195+
1. Add a **Trigger.dev App Connection** using a Trigger.dev Personal Access Token from your account settings. Self-hosted instances are supported.
196+
2. Create a **Secret Sync**: choose the connection, pick the target organization, project and environment (Production, Staging, Development, or Preview), and set the secret path to sync.
197+
198+
Follow the [Trigger.dev Secret Sync guide](https://infisical.com/docs/integrations/secret-syncs/trigger-dev) in the Infisical docs for the full walkthrough.
199+
200+
<Note>
201+
A Secret Sync only overwrites the keys it manages, leaving variables you set manually untouched.
202+
Synced variables are marked as [secret](#secret-environment-variables) by default, so they appear
203+
redacted on the Environment Variables page.
204+
</Note>
205+
206+
#### Using the `syncEnvVars` build extension
207+
208+
For any other service, use our `syncEnvVars` build extension in your `trigger.config` file to resolve secrets at deploy time.
188209

189210
<Note>
190211
To use the `syncEnvVars` build extension, you should first install the `@trigger.dev/build`
191212
package into your devDependencies.
192213
</Note>
193214

194-
In this example we're using env vars from [Infisical](https://infisical.com).
215+
In this example we're using env vars from [Infisical](https://infisical.com), but you can adapt it to any secrets manager.
195216

196217
```ts trigger.config.ts
197218
import { defineConfig } from "@trigger.dev/sdk";

docs/docs.json

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -538,12 +538,14 @@
538538
"group": "Example projects",
539539
"pages": [
540540
"guides/example-projects/anchor-browser-web-scraper",
541+
"guides/example-projects/ask-trigger-chat-agent",
541542
"guides/example-projects/batch-llm-evaluator",
542543
"guides/example-projects/claude-changelog-generator",
543544
"guides/example-projects/claude-github-wiki",
544545
"guides/example-projects/claude-thinking-chatbot",
545546
"guides/example-projects/clickhouse-chat-agent",
546547
"guides/example-projects/cursor-background-agent",
548+
"guides/example-projects/elevenlabs-voice-agent",
547549
"guides/example-projects/human-in-the-loop-workflow",
548550
"guides/example-projects/mastra-agents-with-memory",
549551
"guides/example-projects/meme-generator-human-in-the-loop",

0 commit comments

Comments
 (0)