CONFIGURATION BACKUPS · Workflow idea
For an automation workspace and code repository you are authorized to manage, export process definitions and compare them with saved files. Create or update a backup when content changes, skip unchanged records, and identify files whose source process no longer exists. Definitions may expose business logic or secret values, so sanitize sensitive fields, restrict repository access, and require an owner to approve deletions before removing backup history.
01 / The starting point
Workflow definitions and a private repository managed by the same authorized team
“Preserve a recoverable history of process definitions without exposing secrets or removing records by mistake.”
02 / The work
Helps teams save process definitions to a repository, update changed files, and identify removed processes.
Check that the backup destination is controlled by the authorized team.
Remove credentials, tokens, personal data, and private values before saving.
Update changed files and avoid rewriting unchanged definitions.
Verify a missing process before changing repository history.
Have a workspace owner confirm sensitive exports and any file removal.
03 / The result
A versioned definition backup with change notes and review status for proposed deletions.
Security · Example outcome
A versioned definition backup with change notes and review status for proposed deletions.
Exported definitions can contain credential references, internal endpoints, or sensitive business logic. Remove secrets before saving, limit repository access, test that backups can be restored, and review missing-source matches before deleting version history.
04 / Make it yours
A few choices shape the work around your team.
Limit exports to approved workspaces and private repositories.
Exclude tokens, passwords, private data, and other sensitive values.
Restrict readers and preserve recovery points.
Keep repository files until an owner confirms a deletion is intended.