Go to your table’s Automations. You have two ways to open the logs:

• • In the automations list window → Click the (Show logs) icon to the right of the target automation.
  • In the automation detail → click → then →

At the top of the logs window, several options help you explore executions efficiently:

Overall status	Icon color	Details / Example
Success		Trigger block green (actually triggered). Condition block green if met, otherwise grey. Action block green (executed). Everything ran successfully.
No action executed		Grey blocks (no trigger or conditions not met). Grey action blocks (nothing executed). The automation was evaluated but nothing ran.
ℹ️ If no log is available, your automation hasn’t been executed yet.

🎥 Examples of log status rendering:

Success

No action executed

Overall status	Icon	Details / Example
Success + Warning		If a “Call API” action had an error, all other icons (conditions met) are green, and the Call API icon is ⚠️ orange(warning on that action). Example: API error, code 403 or other non-blocking issue
Failure		If at least one action ran, all icons (trigger, conditions, actions) are orange.
Failure		If none of the actions could be completed, all icons (trigger, conditions, actions) are red.
Failure		If the trigger received a call but data didn’t match expectations, the trigger icon is red and the other icons are grey (not evaluated). Example: system error, missing data
ℹ️ If no log is available, your automation hasn’t been executed yet.

📌 Key takeaways

• A green trigger doesn’t guarantee an action ran.
• Greyed blocks are skipped because conditions weren’t met.
• Orange blocks indicate a failed call despite conditions being met.
• Red blocks mean an automation-level failure (e.g., trigger got unexpected data, action would create a duplicate, etc.).

🎥 Example renderings:

Success + Warning

Trigger & conditions succeeded, but the action has a ⚠️ warning.

Failure

(example: webhook trigger execution failed)

When you hover the trigger, condition(s), or action(s) icon in a block, a tooltip appears with a contextual summary of the configuration that led to the execution:

•  
  • Which condition was evaluated?
  • Which value triggered the run?
  • Which API endpoint was called and with what payload?
  • Which error caused the failure?

When an error occurs, click the log to read the HTTP status code, the sent payload, and the response message.

Example from the screenshot above:

Request status code: 404
Authentication type: Use Bearer token
Payload: test call: ""

✅ Best practices

• Always hover icons to verify values and applied logic.
• Use the error filter to quickly diagnose problematic automations.
• Use row-name search to locate a test or a client case.

Go to a record

➡️ In the right-hand menu "modification", find the log icon

➡️ Click on the icon to open a log details window for this automation