Logs

FlowStack captures structured logs from every automation execution, providing detailed insight into what happened during each run.

Log Levels

Level	Description	Example
INFO	Normal execution events	"Flow started", "Step completed", "Email sent"
WARN	Non-critical issues	"Rate limit approaching", "Retry attempt 2/3"
ERROR	Failures that stopped execution	"Connection refused", "Invalid API key"
DEBUG	Detailed execution data (verbose)	Input/output payloads, expression evaluation

Viewing Logs

Per-Run Logs

1. Go to Automations → View Runs
2. Click a specific run
3. Each step shows its logs inline
4. Click Show Details on any step to see full input/output data

Global Log Viewer

1. Go to Observability → Logs
2. View logs across all automations in chronological order
3. Filter by:
   • Flow name
   • Log level (INFO, WARN, ERROR)
   • Date range
   • Search text

Log Content

Each log entry includes:

{
  "timestamp": "2026-04-21T10:30:00.123Z",
  "level": "INFO",
  "flowId": "flow_abc123",
  "flowName": "Daily Sales Report",
  "runId": "run_xyz789",
  "step": "Send Slack Message",
  "message": "Message sent successfully",
  "duration": 870,
  "metadata": {
    "channel": "#sales",
    "messageId": "1234567890.123456"
  }
}

Code Node Logs

In the Workflow Builder, use console.log() in Code nodes to add custom logs:

console.log('Processing order:', $json.orderId);
console.log('Items:', JSON.stringify($json.items));

// These appear in the step's execution output

Log Search

Search across all logs using the global search:

• Text search — Search by message content, flow name, or error text
• Structured queries — level:ERROR flowName:"Daily Report" to narrow results
• Time-based — Quick filters for last hour, last 24 hours, last 7 days

Sensitive Data

FlowStack automatically redacts sensitive data in logs:

• API keys and tokens are replaced with ***REDACTED***
• Passwords in connection configs are never logged
• On Enterprise plans, configure custom redaction rules for PII (emails, phone numbers, etc.)