Event Logs

A complete and structured record of every workflow execution — monitor automation performance, trace data flow, and diagnose issues with full visibility into each step of a Konnector.

Platform Feature Monitoring Debugging Execution History

What are Event Logs?

An Event Log is a record of a single execution instance of a Konnector. Every time a workflow runs, a new event log is automatically generated. These logs are essential for maintaining reliability, ensuring accuracy, and troubleshooting failures within integrations.

Each event log captures the full picture of what happened during that execution run — from the trigger through every downstream node.

Each event log captures

The Konnector that was executed
The time of execution
The execution status
Step-by-step node execution details
Input and output data for each node
Error information, if applicable

Accessing Event Logs

To view event logs in Konnectify:

Navigate to the Home dashboard

Locate the left-side navigation panel

Click Event Logs

This opens the Event Logs page where all execution records are listed.

Event Logs Page

The Event Logs page displays a table of workflow executions. Each row represents a single execution run.

Table columns

Column	Description
Konnector	The name of the workflow that was executed
Status	The result of the execution (Executing, Success, Partial Success, or Failed)
Executed	The timestamp of when the execution occurred

Available actions

Filters

Refine the event logs list based on:

Konnector name
Execution status
Date range

Refresh

Reloads the latest execution data to ensure the most up-to-date logs are displayed.

Columns

Customise the table view by:

Selecting which columns are visible
Pinning important columns
Resetting to the default configuration

Execution Status Types

Each event log is categorised into one of the following statuses. If a workflow fails, detailed error information is available within the log.

Status	Meaning
EXECUTING	The workflow is currently in progress
SUCCESS	The workflow completed successfully
PARTIAL SUCCESS	Some nodes executed successfully while others failed
FAILED	The workflow execution failed — detailed error information is available within the log

Detailed Execution View

Clicking on a specific event log opens the detailed execution view, which provides complete insight into how the workflow was executed — node by node.

Node-Level Details STEP BY STEP

Each step in the workflow is displayed as a node with its individual execution status. This allows you to identify exactly where the workflow succeeded or failed.

Input Data DATA IN

Displays the data received by each node
For trigger nodes, this represents the initial event payload

Output Data DATA OUT

Shows the processed data generated by each node
Helps trace how data transforms across the workflow

Error Details FAILED NODES

Available for failed nodes only
Includes error messages and response details
Useful for diagnosing issues such as invalid data or duplicate entries

Example Scenario

Slack message triggers ticket creation — workflow fails

Slack trigger · Ticket system · Debugging with Event Logs

FAILED

A workflow is configured so that a message in Slack triggers ticket creation in an external system. The workflow fails mid-execution.

Open the Event Logs page and locate the failed execution.

Click into the log to open the detailed execution view.

Identify the failed node — for example, the ticket creation step.

Review the error message and response details in the Error Details panel.

Make the necessary corrections and re-activate the workflow.

✓ Result — The exact failure point is identified in seconds, the root cause is understood, and the fix is applied without needing to re-examine the entire workflow.

Why Event Logs Matter

Event Logs play a critical role in workflow management. They give you the visibility needed to keep automations running reliably.

✓ What they enable

Debugging of failed executions
Monitoring of automation performance
Validation of data flow across nodes
Identification of configuration issues
Execution history for auditing

✗ Without event logs

No visibility into what ran or failed
Difficult to pinpoint where data was dropped
No record for compliance or audit purposes
Longer resolution time for integration failures

Ready to build smarter workflows?

Use Event Logs to monitor, debug, and keep every automation running reliably.

Get started free →