⚠️ Important: Always sync Schema and Category changes before pushing Workflows. If the schema or category referenced in a workflow is not available in the target workspace, it will result in validation errors during sync.
Pushed workflows are saved in draft version. Make sure to pass --commit=true flag to commit the workflows while pushing it.

​
Syntax

suprsend workflow push [flags]

​
Flags

FlagDescriptionDefault
-h, --helpShow help for the command–
-c, --commit stringCommit the workflows (—commit=true)true
-m, --commit-message stringCommit message describing the changes for —commit=true–
-d, --dir stringOutput directory for workflowssuprsend/workflow
-g, --slug stringSlug of the workflow to push–

​
Example

# Push workflows from default directory
suprsend workflow push

# Push workflows from custom directory
suprsend workflow push --dir dev-environment/workflows

# Push individual workflow by passing it's slug
suprsend workflow push --slug welcome-email

# Push workflows and commit them
suprsend workflow push --commit=true --commit-message "Commit message"
🚨 Push and Commit Behavior:
  • New workflow not showing up? → Push without commit first, then commit separately
  • Changes not appearing in live mode? → Check if workflows are linked to other workflows
  • Fix: Update your workflow files to include all dependencies, or remove the links