Workflow Versions And Folders
Workflow Versions and Folders
As your app grows, you'll have more workflows and you'll change them more often. Two features help you keep them organized and recoverable: Versions let you see and restore previous saves of a workflow, and Folders let you group related workflows together.
Workflow Versions
Every time you save a workflow, Tadabase stores a snapshot. The snapshot includes the trigger, every step, every condition, every value mapping — the complete configuration at the moment of save.
That means you can go back to any previous version and restore it.
Viewing versions
- Open the workflow in the editor.
- Click Versions in the editor header. A panel opens showing every saved version.
- Each row shows the date, who saved it, and an optional comment.
Restoring a version
Click the restore icon next to any past version. Tadabase prompts you to confirm, then replaces the current workflow's configuration with the snapshot. The current state is also versioned automatically before the restore — so a restore is always reversible.
Adding a comment when saving
When saving a workflow, you can add a short comment describing what changed (e.g. "Added Slack notification," "Fixed condition for VIP path"). The comment is shown in the version list and makes it much easier to find the right version later.
Workflow Versioning is included on most paid plans. If you don't see the Versions button, your plan may not include it — check your subscription details.
Tips for using versions effectively
- Save often, with comments. Treat versions like commits in source control.
- Restore before experimenting. If you're about to make big changes, take note of the current version date so you have a clean rollback point.
- Versions are per-workflow. Restoring one workflow doesn't affect others.
- You can delete old versions from the panel if you're cleaning up — but most users find it useful to keep them.
Workflow Folders
Folders are a flat organization layer for workflows — like email folders. Group related workflows together to keep the workflow list scannable.
Creating a folder
- From the workflow list, click Manage Folders (or the folder icon).
- Click Add Folder and give it a name (e.g. "Onboarding," "Billing," "Notifications").
- Drag-and-drop workflows into the folder, or open a workflow and pick its folder from the editor.
Common folder structures
| By | Example folder names |
|---|---|
| Functional area | Onboarding · Billing · Notifications · Cleanup · Reports |
| Lifecycle stage | Lead · Trial · Active Customer · Churned |
| Owner | Sales workflows · Ops workflows · Marketing workflows |
| Status | Production · Staging · Drafts · Archived |
Filtering the list
The workflow list lets you filter by folder so you only see what's relevant to your current task. Combine folder filters with search and table filters to drill down quickly in apps with many workflows.
Tips for folders
- Don't over-engineer. Three to seven folders is usually enough — too many makes them as hard to scan as no folders at all.
- Move drafts to an "Archived" or "Drafts" folder instead of deleting. You can always come back to them.
- Use a "Production" folder for the workflows you don't want anyone to edit casually — even if it's just a naming convention reminder.
Active vs. Inactive workflows
Independent of versions and folders, every workflow has an active/inactive toggle. Use it to:
- Pause a workflow that's misbehaving without losing the configuration.
- Stage a new workflow — keep it Inactive until you're done testing.
- Stop a scheduled workflow that no longer needs to run, without deleting it.
Inactive workflows don't trigger and don't run. Toggling back to Active makes them eligible to fire again on the next event or scheduled tick.
We'd love to hear your feedback.