Automation Logs

Every automation execution is recorded in Automation Logs. Logs show which steps ran, whether they succeeded or failed, and provide details for debugging. Use logs to verify your automation works as expected and to troubleshoot issues when something goes wrong.

Where to Find Logs

1. Go to CRM in the sidebar.
2. Select your Entity and then the Status Group (pipeline).
3. On the Kanban board, click the ⋮ (three-dots menu) on the stage column header.
4. Select Stage Automation.
5. In the automation visualizer, look for the Logs section or tab.

You'll see a list of automation runs for that stage, sorted by date (most recent first).

What Logs Show

Each log entry includes:

Step-Level Details

Click a log entry to expand it and see each step:

• Step name – The action type (e.g., Email, Webhook).
• Status – Success (✓), Failed (✗), or Skipped (e.g., Filter condition false).
• Input – What data was passed to the step (e.g., lead ID, variables).
• Output – What the step returned (e.g., webhook response, formatted value).
• Error – For failed steps, the error message or stack trace.

Debugging Failed Steps

When a step fails:

1. Open the log for the failed run.
2. Find the failed step – It will show an error icon and message.
3. Check the error – Common issues: invalid email, webhook URL unreachable, missing required field.
4. Fix the automation – Update the action configuration (e.g., add a Filter to skip leads without email).
5. Retry – If supported, use the Retry button to re-run the failed step or entire automation.

Retrying Failed Automations

Some automations support retry:

• Retry step – Re-run only the failed step (if the lead data hasn't changed).
• Retry automation – Re-run the entire automation from the start.

Retry is useful when the failure was transient (e.g., temporary API outage). If the failure is due to bad data or configuration, fix the automation first, then retry.

Best Practices

• Monitor logs regularly – Spot patterns (e.g., same step failing for many leads).
• Use filters – Reduce noise by filtering logs by status (Failed only) or automation.
• Fix root causes – Don't just retry; fix the underlying issue to prevent future failures.

Next Steps

• Return to automations overview
• Review available actions
• Use variables correctly to avoid errors