1
[Workflow] API keys variables
Source: twentyhq/twenty#13803 · opened by @StephanieJoly4
Scope & Context
Goal of this request is to offer an alternative instead of hard coding the different API keys needed in serverless functions.
Why?
• security perspective
• key rotation won't be easy
Idea
Could we have "secured" (tbc what this means) variables (where users put their API keys) somewhere, that could be used across the different serverless functions for ex?
@Bonapara feel free to turn this into a discussion based on the level of maturity vs our roadmap
Goal of this request is to offer an alternative instead of hard coding the different API keys needed in serverless functions.
Why?
• security perspective
• key rotation won't be easy
Idea
Could we have "secured" (tbc what this means) variables (where users put their API keys) somewhere, that could be used across the different serverless functions for ex?
@Bonapara feel free to turn this into a discussion based on the level of maturity vs our roadmap
No pledges yet. Be the first to back this.
Comments
Similar requests
Workflow step mutations are unreachable via workspace API keys (`Forbidden resource`); also hidden from GraphQL introspection
0 votes · 0 comments
Workflow action to run another workflow (RUN_WORKFLOW)
1 vote · 0 comments
Support workflow variable binding for the Send Email action's Attachments field
1 vote · 0 comments
Feature request: Discover workflow actions from MCP servers
4 votes · 0 comments
Save custom values in settings to be used anywhere
1 vote · 0 comments
No comments yet.