Skip to main content

Documentation Index

Fetch the complete documentation index at: https://hypha-docs.plinqx.app/llms.txt

Use this file to discover all available pages before exploring further.

The LOG node logs messages and data during flow execution, providing visibility into flow behavior for debugging and monitoring.

​
Overview

LOG nodes enable:
  • Debugging: Log intermediate values and states
  • Observability: Track flow execution progress
  • Monitoring: Monitor flow behavior in production
  • Troubleshooting: Diagnose issues with detailed logs

​
Configuration

​
Log Level

Select log level:
  • Info: General information (default)
  • Warn: Warning messages
  • Error: Error conditions
  • Debug: Detailed debugging information

​
Message

Log message (supports expressions): 
Processing user {{START.userId}}
API call completed with status {{action.response.statusCode}}
Found {{items.length}} items

​
Data

Additional data to log (supports expressions): 
{
  "userId": "{{START.userId}}",
  "action": "{{START.action}}",
  "response": "{{action.response}}"
}

​
Expression Support

Log messages and data support expressions:
  • Variable Access: {{node.field}}
  • Nested Access: {{node.response.data.id}}
  • Functions: String, number, date functions
  • Calculations: Mathematical operations

​
Use Cases

​
Debugging

Log intermediate values: 
LOG: "Processing step 1"
ACTION: Execute operation
LOG: "Step 1 completed: {{action.response}}"

​
Monitoring

Track execution progress: 
LOG: "Flow started for user {{START.userId}}"
LOG: "Processing {{START.itemCount}} items"
LOG: "Flow completed successfully"

​
Error Context

Log context before errors: 
LOG: "About to call API with {{START.params}}"
ACTION: Call API
LOG: "API call result: {{action.response}}"

​
Output

LOG node provides output: 
{
  "message": "Processed user user_123",
  "data": {
    "userId": "user_123",
    "action": "update"
  },
  "timestamp": "2024-01-15T10:30:00Z"
}

​
Best Practices

Use Appropriate Levels

Use appropriate log levels (info, warn, error, debug)

Include Context

Include relevant context in log messages

Avoid Sensitive Data

Don’t log sensitive information (passwords, tokens)

Structured Logging

Use structured data for better log analysis

​
Next Steps

TRY Node

Log errors in catch blocks

Transform Node

Transform data before logging