Versioning

Notiflows uses a versioning system that lets you safely make changes without affecting live notifications. This ensures you can iterate on your workflows while keeping production stable.

How Versioning Works

Each notiflow has:

• Draft version - The version you're actively editing
• Published version - The live version that runs when triggered

When you trigger a notiflow, it always uses the published version. Your draft changes don't affect live notifications until you publish.

Version Lifecycle

Create notiflow → Edit draft → Publish → Edit draft → Publish → ...

1. Create - A new notiflow starts with a draft version
2. Edit - Make changes to steps, templates, and configuration
3. Publish - Draft becomes the new published version
4. Iterate - Continue editing the draft for future changes

Publishing

When you publish a notiflow:

1. The current draft is saved as a new immutable version
2. The published version pointer updates to this new version
3. All future triggers use the newly published version
4. In-flight workflows (already triggered) continue with their original version

Draft Changes

While editing a draft, you can:

• Add, remove, or reorder steps
• Change step configurations
• Edit template content
• Modify connections between steps

None of these changes affect the published version until you explicitly publish.

Activating and Deactivating

Notiflows can be activated or deactivated:

• Active - Can be triggered, uses published version
• Inactive - Cannot be triggered, API calls return an error

Deactivating a notiflow is useful when you need to temporarily stop notifications without deleting the workflow.

Best Practices

Test before publishing

Use the preview and test features to verify your changes work correctly before publishing.

Publish intentionally

Review all draft changes before publishing. Once published, the version is immutable.

Use descriptive names

Name your notiflows clearly so you can identify them when managing multiple workflows.