Automation Logs
The Automation Logs dashboard provides a centralised view of the health, performance, and history of all your automated actions.
Use this page to monitor the success of your Workflow Webhooks and Destination deliveries, debug failures, and ensure your automated processes are running reliably.
This guide will walk you through each component of the Automation Logs dashboard.
Accessing the Automation Logs
To navigate to the Automation Logs page:
From the main Workspace Overview, select the Automations icon from the left-hand sidebar.
In the sub-menu that appears, click on Automation Logs.
Understanding the Dashboard
The dashboard is composed of three main areas: high-level summary metrics, performance charts, and a detailed, filterable log table.
Summary Metrics
At the top of the page, you'll find four key performance indicators (KPIs) that provide a quick overview of your automation health:
Workflow Deliveries & Fails: The success and failure rate of webhooks triggered from your User Flows and Data Flows.
Destination Deliveries & Fails: The success and failure rate of events sent to your configured Destinations.
Performance Charts
The four charts provide a visual breakdown of your automation performance over time and by endpoint.
Workflow Webhooks & Destination Webhooks: These line charts display the volume of successful versus failed deliveries over the last 30 days. Hover over a point on the chart to see the daily counts.
Workflow Endpoints & Destination Endpoints: These doughnut charts show the distribution of your deliveries across all target endpoints (e.g.,
slack.com, custom APIs). This helps you quickly identify which services are receiving the most traffic or experiencing the most failures.
Inspecting Individual Log Entries
The Logs table at the bottom of the page contains a detailed, real-time record of every individual automation event. This is the most powerful tool for debugging specific issues.
Filtering Logs
You can filter the log table to quickly find what you're looking for:
Status Codes: Enter the range of the error messages e.g. 200 - 599 to quickly filter for the specific logs that you are looking for.
Endpoint: Click the Endpoint button to filter logs for a specific destination service.
Analysing a Log Entry
Each row in the table represents a single event and contains key information like the timestamp, the type of event, the destination, and the result. To dive deeper:
Locate the log entry you wish to inspect in the table.
Click the expansion arrow on the far right of the row.
This will open a modal window containing the full request and response details.
Understanding Request and Response Details
The details modal gives you everything you need to debug a specific event.
Request Details: This section shows you exactly what was sent from our platform.
Endpoint: The URL the request was sent to.
Method: The HTTP method used (e.g.,
POST).Body Content: The exact JSON payload that was sent in the request.
Response Details: This section shows you the response we received from the endpoint.
Status Code: The HTTP status code returned by the server (e.g.,
200for success,404for not found).Body Content: The response body returned by the server, which often contains important error messages for failed requests.
Last updated