Skip to main content

Activity Logs

What you'll learn
  • How to access and view system activity logs
  • How log levels work and where they are configured
  • How to use logs for troubleshooting

Activity logs record system events and actions that occur within your AutoTalk company. They provide visibility into what is happening behind the scenes and are useful for troubleshooting issues, auditing activity, and monitoring AI agent behavior.

Accessing logs

Navigate to Empresa > Logs (Company > Logs) in the sidebar. This opens the logs page where you can browse recorded events.

Understanding log levels

The amount of detail captured in the logs is controlled by the Nivel do Log (Log Level) setting, which can be configured in multiple places:

WhereHow to access
Company levelSet in Empresa > Configuracoes under the "Nivel do Log" field. The default is "warn".
Agent levelIndividual AI agents may have their own log level setting, allowing more detailed logging for specific agents.
Workflow levelIf you use workflows, each workflow can have its own log level for granular control.

Common log levels, from least to most verbose:

LevelWhat it captures
errorOnly critical errors that need immediate attention
warnWarnings and errors (the default)
infoGeneral information about system operations, plus warnings and errors
debugDetailed debugging data, including internal process steps -- generates the most log entries

What appears in the logs

Depending on the configured log level, you may see entries for:

  • AI agent actions and decisions
  • Workflow executions and their results
  • API calls and integration events
  • Error messages and warnings
  • System-level events (channel connections, configuration changes)

Using logs for troubleshooting

If something is not working as expected (for example, the AI agent gives an unexpected response, or a workflow does not trigger), follow these steps:

  1. Go to Empresa > Logs.
  2. Look for recent entries around the time the issue occurred.
  3. If the logs do not contain enough detail, temporarily increase the log level to "info" or "debug" in Empresa > Configuracoes.
  4. Reproduce the issue.
  5. Return to the logs page and look for more detailed entries.
  6. After resolving the issue, set the log level back to "warn" to avoid generating excessive log data.
tip

Keep the log level at "warn" for normal operations. Only increase it to "info" or "debug" when you are actively investigating a problem. Higher log levels produce more data, which can make it harder to find relevant entries and may affect storage.

Next steps