Skip to main content
Learn about the configuration and behavior of Workflows.
Read Build workflows to create and publish a workflow.

​
Workflow access

You can access Workflows in the menu when you have the Read Workflows permission. Without it, the menu item is hidden. These permissions also require Read Workflows:
  • Create and modify Workflows
  • Publish Workflows
  • Delete Workflows
  • Activate and deactivate Workflows
Without Create and modify Workflows, the designer shows You have view-only access to this workflow. Blocks stay inactive. Built-in role access is listed in Members and roles.

​
Triggers

A trigger defines when a workflow starts.
Transaction statuses such as APPROVED, PENDING, and REJECTED are trigger filters. They are not separate event types. They determine which transactions start a workflow.

​
Webhook callouts

A webhook callout sends a signed HTTP POST request. The target URL must use http or https. A webhook callout can include up to 10 custom headers for authentication or routing data. Voucherify generates the webhook payload automatically. Read Workflows webhooks for the payload structure. To verify signatures, generate a secret in Project settings > Webhooks and validate the x-voucherify-signature header. Read Webhook authentication for details.

​
Identifiers

Each trigger and webhook callout has an ID. You see it on the canvas and in the settings panel. The prefix can’t be changed. You can edit the suffix. Use 1 to 40 characters: lowercase letters, digits, and underscores. The ID must be unique in that workflow. A new block gets the next number.

​
Save, publish, and activate

Saving, publishing, and activation are separate operations.

​
Statuses

A workflow has three statuses: Draft, Active, and Inactive.

​
Deactivation and version behavior

The Versions list in the designer shows Current draft and the latest 100 published versions. Select a published version to view it. The canvas is read-only. Restore as draft requires Create and modify Workflows. It copies that version into the working copy. Save and publish the copy to make it live. Voucherify keeps the newest 100 published versions. Older versions are dropped. Events that occur while a workflow is inactive do not start a run. Deactivation does not cancel a run that has already started. The run completes every pending action in the published canvas it started with. Existing runs keep the version they started with when you publish a new version. New runs use the latest published version.

​
Limits

Trigger and action limits are separate. A workflow can contain five triggers and five actions.
Last modified on October 13, 2026