Workflow Logs

Note to customers: This is a part of our upcoming Summer ’26 release and will be rolled out in phases. If you would like early access to explore the feature, please fill out this form.

Workflow logs help you track, analyze, and debug your configured workflows. They provide complete event-level visibility, including request, response, and execution details, so you can understand how each workflow runs.

Logs are available for all workflow platforms, including Flow Builder, Deluge scripts, and Webhooks.

Why use workflow logs?

Workflow logs are essential for improving reliability and performance:

• Faster debugging: Identify exactly where and why a workflow failed.
• Performance tracking: Monitor success and failure trends over time.
• Integration validation: Verify third-party responses using detailed request and response logs.

Accessing logs

You can view logs in two ways:

Global logs (All Workflows) 

• Navigate to Settings > Workflow > Logs to view executions across all workflows.

Workflow-Specific logs

• Navigate to Settings > Workflow > Select a workflow > Logs to view logs for a specific workflow.

Note: You can also apply filters based on status, event, or module to narrow down results.

Logs list overview

Each log entry includes:

• Module: Name of the workflow module
• Record ID: Associated record (e.g., chat ID for conversations module, department ID for department module)
• Event: The event from the module that initiated the workflow
• Timestamp: Execution time
• Status: Success or failure

Action (Detailed view)

Each workflow execution provides detailed logs to help you debug and validate behavior. These logs vary slightly based on the component used.

For Deluge scripts & Webhooks

The logs include:

Event payload

• Data received when the workflow was triggered.

Execution logs

• Request
  • Shows the exact payload sent to the script or external API.
  • This helps you verify whether all required data is passed correctly. If a workflow fails, this is the first place to check for missing or incorrect inputs.
• Response
  • Displays the response returned by the script or API.
  • If the execution fails, the response helps you understand the reason, such as validation errors, API failures, or incorrect configurations.

For Flow builder

The logs provide both event-level and card-level visibility:

Event Payload 

• Data received when the workflow was triggered

Execution Logs (Card-Level Details):

• Each card execution is tracked individually, including:
  • Card Name: Name of the executed card
  • Card Type: Type of card (e.g., response, action, integration)
  • Status: Success or Failure
  • Message: Outcome of the execution. You can expand each card to view detailed logs, including:
    • Card input data
    • Execution input and processing details
    • This helps you identify if any required data is missing, incorrectly mapped, or causing the failure at a specific step.