You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running a self-hosted twenty installation, and a user signs up we would like to trigger a script that would use the API to deploy our custom objects into the new workspace. For this we would need a system wide API key and a system wide webhook that would fire an event that a new workspace has been created, and then use the system wide API key to add the custom objects and configuration into the new workspace.
Current behavior
Currently you can only create an API key or webhook for a single user in an existing workspace.
Expected behavior
When a new workspace is created the webhook fires and our custom script would use the system API key to make changes to the newly created workspace.
Technical inputs
A system API key could be created with a yarn command or set from an environment variable
A webhook URL could be configured with a yarn command or set from an environment variable
The text was updated successfully, but these errors were encountered:
For webhooks, maybe there's something to hack with Postgres Triggers on a self-hosted instance to register a webhook automatically when a table called webhooks is created. It's not pretty but the hack could work. I don't have a better idea for now, I'll keep this open an see if something comes up
Scope & Context
When running a self-hosted twenty installation, and a user signs up we would like to trigger a script that would use the API to deploy our custom objects into the new workspace. For this we would need a system wide API key and a system wide webhook that would fire an event that a new workspace has been created, and then use the system wide API key to add the custom objects and configuration into the new workspace.
Current behavior
Currently you can only create an API key or webhook for a single user in an existing workspace.
Expected behavior
When a new workspace is created the webhook fires and our custom script would use the system API key to make changes to the newly created workspace.
Technical inputs
A system API key could be created with a yarn command or set from an environment variable
A webhook URL could be configured with a yarn command or set from an environment variable
The text was updated successfully, but these errors were encountered: