Manage automations

An automation is a good fit for a job that follows known rules, such as a scheduled backup, CI job, release pipeline, or synchronization triggered by an event.

It belongs to your account but has its own name, credentials, and sign-in history. Shutting down one automation does not affect your personal sign-in or an unrelated programmatic task.

Create an automation

In with.sudomimus.com:

1. Open Programmatic access → Automations.
2. Select Create.
3. Use a name that identifies both the job and environment, such as “Production release” or “Nightly backup.”
4. Note its trigger, runtime location, or owner in the description, then save it.

Next, create an access key or register a public key for the automation. The target application must accept automation sign-in with that credential type.

Manage its lifecycle

• Suspend the automation during maintenance or an investigation.
• Before you resume it, check that its trigger will not replay stale or unsafe work.
• Revoke it when the automation is permanently retired. Revocation cannot be undone.

If you only need to remove access to one application, revoke the credentials that cover that application instead of shutting down the entire automation.

Good operating habits

• Give each pipeline or job its own automation and credential.
• Use separate identities and credentials for test and production.
• Store credentials in a secret manager or protected runtime environment, never in a script or repository.
• Rotate credentials when the runtime platform or responsible team changes.
• Review Session security and confirm that recent applications and activity times are expected.

Use an agent when the software chooses tools and next steps from context.