Skip to content

Commit dafb10e

Browse files
docs for environment variables in private components
1 parent ac89f9b commit dafb10e

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

docs-v2/pages/environment-variables.mdx

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -114,6 +114,10 @@ You can reference the value of environment variables using `{{process.env.YOUR_E
114114
src="https://res.cloudinary.com/pipedreamin/image/upload/v1708551738/env-vars-feb-2024/env-vars-object-explorer-v2_x9afzl.png"
115115
/>
116116

117+
<Callout type="info">
118+
Private components (actions or triggers) do not have direct access to the same environment execution variables as public components or custom code steps. To use environment variables in private components, add a prop specifically for the variable you need. For sensitive data like API keys, you can [configure the prop as a secret](https://pipedream.com/docs/components/api#props). In your prop configuration, set the value to `{{process.env.YOUR_ENV_VAR}}` to securely reference the environment variable.
119+
</Callout>
120+
117121
## Frequently Asked Questions
118122

119123
### What if I define the same variable key in my workspace env vars and project env vars?

0 commit comments

Comments
 (0)