[ Developer tools ]
AWS Secrets Manager integration for your workflows.
Connect AWS Secrets Manager to Collabase once and use 6 actions in your workflows. No code needed, hosted in Switzerland.
AWS Secrets Manager in Collabase
Connect AWS Secrets Manager to Collabase once and use 6 actions in your workflows. No code needed, hosted in Switzerland.
How to connect it
- Open the integrations in the workspace settings.
- Choose AWS Secrets Manager and connect your account.
- Add a trigger or an action to the workflow.
AWS Secrets Manager triggers
AWS Secrets Manager does not start a workflow on its own. You use its actions after any other trigger.
AWS Secrets Manager actions
| Name | Description | Fields |
|---|---|---|
| Create Secret | Creates a new secret. |
|
| Get Secret Value | Retrieves a secret value. |
|
| Update Secret | Updates an existing secret. |
|
| Delete Secret | Deletes an existing secret. |
|
| Find Secret | Finds an existing secret using filters. |
|
| Generate Random Password | Generates a random password using AWS Secrets Manager. |
+ 2
|
[ Developer tools ]
Related integrations
Tools that often share a workflow.
Questions about AWS Secrets Manager
What can I automate with AWS Secrets Manager in Collabase?
AWS Secrets Manager brings 6 actions and 0 triggers, for example Create Secret, Get Secret Value, Update Secret, Delete Secret and 2 more. You combine them in a workflow without code and mix them with every other integration.
How do I connect AWS Secrets Manager to Collabase?
You open the integrations in the workspace settings, choose AWS Secrets Manager and connect your account once, using custom credentials. After that all triggers and actions are available in the workflow.
Does the AWS Secrets Manager integration cost extra?
No. All integrations are included in every licence, in the Isolated Cloud and in Self-Hosted operation. There is no module price.
Test it against your own content. A proof of concept is ready within days.
We set up an instance with your content and you test it against real workflows. In a first conversation we clarify scope, operating model and timing.