Zuper Workflow Builder is a powerful tool for automating and streamlining business processes through a node-based system. It enables users to create custom workflows to automate tasks like job assignments, invoicing, and status updates, reducing manual effort and boosting efficiency. Workflow Builder is currently in Private Beta. To request access, please email our support team at support@zuper.co.

​
Zuper Workflow builder components

Below is an overview of its key components:
  • Canvas: The primary workspace where workflows are designed by arranging and connecting nodes to define task sequences.
  • Triggers: Define when a workflow starts and what data is passed into it. Three types include:
    • Zuper Event Trigger: Starts workflows based on platform events (e.g., “Job Created” or “Invoice Updated”).
    • Scheduled Trigger: Runs workflows for recurring tasks on fixed intervals (e.g., every 15 minutes) or cron-based schedules (e.g., daily at 9 AM PST).
    • Webhook Trigger: Initiates workflows via external HTTP requests (e.g., POST to https://zuper.workflow.endpoint/wf1) with headers like x-module and x-module-uid to link to records (e.g., job ID: abc123).
    • Zuper Workflow Builder Components Below is an overview of its key components:
      • Canvas: The primary workspace where workflows are designed by arranging and connecting nodes to define task sequences.
      • Triggers: Define when a workflow starts and what data is passed into it. Three types include:
        • Zuper Event Trigger: Starts workflows based on platform events (e.g., “Job Created” or “Invoice Updated”).
        • Scheduled Trigger: Runs workflows for recurring tasks on fixed intervals (e.g., every 15 minutes) or cron-based schedules (e.g., daily at 9 AM PST).
        • Webhook Trigger: Initiates workflows via external HTTP requests (e.g., POST to https://zuper.workflow.endpoint/wf1) with headers like x-module and x-module-uid to link to records (e.g., job ID: abc123).
      • Nodes: Individual actions or steps in a workflow, such as sending emails, updating attributes, or performing complex operations like API calls via the HTTP node for seamless external system integration.
      • Path: Links between nodes that dictate the workflow’s flow and sequence of actions.
      • Inputs: Data or information a node requires to execute, such as API parameters or user inputs, often sourced from triggers or previous nodes.
      • Variables: Variables are values you can define that can be shared across workflows and its execution.
      • Executions: Each workflow run, tracked in the Execution History tab with details like Execution ID, Workflow Name, Triggered/Created Time, Status (Success, Failed, In Progress, Queued), and duration. Use filters to analyze runs or flag issues for troubleshooting.
      • Templates: Pre-built workflow flows to serve as starting points or inspiration for faster setup.
      • Notes: Add annotations to workflows for additional context or links to documentation, improving clarity and maintenance.
      • Insights: Access the Execution Insights dashboard to view total executions, success/failure rates, and trends. Filter by time range (e.g., “Last Days”) and export data for analysis.