See exactly what's
running in the background.
Every automation, webhook, and background process writes to the same log system. The Log Viewer is where you see it all — filtered, searchable, and linked to the notification system so errors don't go unnoticed.
What Gets Captured
Automations run silently. Logs are your window into what's actually happening.
Automations don't have a screen. When the campaign send engine fires at 6am, or the task reminder processes overnight, the only record of what happened is the log.
Every automation and webhook writes structured log lines: the process name, log level, a message, a timestamp, and optional metadata (objects, counts, error details).
Log Levels
Four levels. Each means something different.
Something failed. An automation couldn't complete its work. These need attention.
Something unexpected happened but execution continued. Worth reviewing.
Normal operational messages. "Sent 12 emails", "Processed 45 records", etc.
Verbose detail written during development or debugging. Usually filtered out in production.
Filtering
Narrow 100,000 log lines down to the 12 you care about.
Filter to a single automation or webhook. E.g. "campaign-send-engine" or "add-task-activities".
Show only errors, warnings, info messages, or debug lines.
Full-text search across the log message content.
Trace all log lines from a single execution run. Every automation run gets a unique session ID.
Filters combine. Process name + ERROR level gives you only the failures from one specific automation.
Session Tracing
Follow one run from start to finish.
Each time an automation runs — whether triggered by a cron schedule or a manual trigger from the Automations App — it writes all its log lines under the same session ID.
Click the session ID badge on any log line and the viewer immediately filters to show only that run. You see the full sequence of what happened, in order, without noise from concurrent runs.
Expanding Detail
Every log line can carry structured data.
Beyond the message text, automations can attach metadata to any log line — full JSON objects, error stack traces, record counts, API responses. It's stored separately so it doesn't clutter the list view.
Click any row to expand it and see the full metadata, formatted as readable JSON. A copy button lets you paste the raw content elsewhere for deeper investigation.
Alerts
Errors don't just sit in a log. They get pushed to you.
Telegram alerts
Configure automations to push error-level log lines to a Telegram bot. You get a message the moment something fails — no need to poll the log viewer.
Platform notifications
Errors can also route into the platform notification system — the same bell you see in the task and chat apps. One place for all your alerts.
Housekeeping
Clear logs for a process or all at once.
Logs accumulate fast when automations run every minute. The Truncate button clears logs for the currently-filtered process, or all logs across all processes.
Irreversible
Truncation cannot be undone. Filter to the specific process you want to clear before using this — it's easy to accidentally clear more than intended.