Delinea Secret Server

• New secretRuns when a secret is added to Secret Server, with its name, folder and template (not its values). Secrets already there when the workflow is turned on don't start it. How often it checks follows your workspace plan.
• Password changedRuns when Secret Server changes a secret's password, on a schedule, at check-in or by a person, with the secret and when it changed (not the password). How often it checks follows your workspace plan.
• Password change failedRuns when a secret goes out of sync because changing its password on the account it belongs to failed, with Secret Server's reason. It runs again if the secret recovers and fails again. How often it checks follows your workspace plan.
• Heartbeat failedRuns when a secret's heartbeat finds its credentials no longer work, such as Failed, Unable to connect or Account locked out. It runs again after a heartbeat succeeds and a later one fails. How often it checks follows your workspace plan.
• Secret checked outRuns when someone checks out a secret, with who has it. Each check-out starts one run. How often it checks follows your workspace plan.
• New folderRuns when a folder the connected account can see is added, with its name and path. How often it checks follows your workspace plan.
• New userRuns when a user is added to Secret Server, by hand or from Active Directory, with their user name, email and whether they are enabled. How often it checks follows your workspace plan.
• User locked outRuns when a Secret Server user is locked out, such as after too many failed sign-ins. It runs again if they are unlocked and locked out again. How often it checks follows your workspace plan.

• Search secretsFind secrets by name, folder, template or heartbeat status, or only those checked out, with each one's folder, template, check-out and heartbeat state. Values aren't read.
• Get secretGet a secret's details and the values of its fields, such as its machine and user name, by slug in 'fields'. Password fields are listed without their values; 'Get secret field' reads one.
• Get secret fieldRead one field's value from a secret, such as its password, to use in a later step. Secret Server records the view in its audit trail. The value is in the step's result for later steps, so anyone who can see this workflow's runs can see it; the run's summary doesn't print it.
• Create secretStore a new secret from a template, such as a Windows Account or a Password, in a folder, with its field values such as the user name and password.
• Update secret fieldSet one field of a secret, such as its password after it was changed elsewhere, or its notes. Only Secret Server's record changes, not the account it belongs to: 'Change password' does that.
• Check out secretCheck out a secret that needs it, so only the connected account can use it until it is checked in or the check-out time runs out.
• Check in secretCheck a secret back in so others can check it out. If its template changes the password on check-in, Secret Server does so.
• Change passwordChange a secret's password on the account it belongs to, such as a Windows or database account, and in Secret Server: to the password given, or one Secret Server generates by the template's rules. The change runs in the background; the secret shows if it failed.
• Run heartbeatAsk Secret Server to check now that a secret's credentials still work on the account they belong to. The result shows on the secret as its heartbeat status.
• Expire secretMark a secret expired now, so its password is due to be changed, automatically if the secret changes it on a schedule.
• Get secret auditSee who viewed, edited, checked out or launched a secret, and when, newest first, optionally with its password changes.
• Delete secretDelete (deactivate) a secret. Secret Server keeps it and its audit trail, hidden from users, and an administrator can bring it back.
• List foldersList the folders the connected account can see, with their paths, optionally by name or inside one folder.
• Get folderGet a folder's name, path and parent, the templates its secrets may use, and optionally its subfolders.
• Create folderCreate a folder for secrets, at the top level or inside another folder, whose permissions it takes unless you say otherwise.
• Delete folderDelete an empty folder. Secret Server refuses a folder that still holds secrets or folders.
• List secret templatesList the secret templates (the kinds of secret, such as Windows Account or SQL Server Account) and whether each can run a heartbeat.
• List usersList Secret Server users, matched on user name, display name or email, with whether each is enabled, locked out or an application account.
• Create userCreate a local Secret Server user, or an application account that can only use the API. Needs the Administer Users permission.
• Delete userDelete a Secret Server user, such as when someone leaves. Needs the Administer Users permission.
• Get connected accountSee which Secret Server account the connection signs in as, and the role permissions it has.
• List groupsList Secret Server groups, with how many members each has and whether it is synced from Active Directory.
• Add user to groupAdd a user to a group, giving them whatever the group is shared, such as when someone joins a team.

No actions match that.