Log node

Record custom messages to workflow execution logs for debugging and monitoring

The Log node records custom messages to workflow execution logs during runtime. It enables you to track workflow progress, capture variable values at specific points, and add contextual information that helps with debugging and monitoring integration workflows.

When to use

• Debug complex workflows by logging intermediate values
• Track workflow progress through multi-step processes
• Capture error context before handling failures
• Record audit information for compliance requirements
• Monitor data transformations between nodes

Log messages appear in Logs > Executions and are visible in the workflow execution details for each run.

Input parameters

Log Level · dropdown · required

Severity level for the log entry. Select based on the type of information being logged.

Level	Use Case
Debug	Detailed diagnostic information for development and troubleshooting
Info	General operational messages confirming workflow progress
Warning	Potential issues that don’t stop execution but need attention
Error	Failures or problems that may affect workflow results

Message Title · textarea · required

The message content to record. Supports dynamic variables using {{variable}} syntax to include data from previous nodes.

Message Body · code editor

Additional structured data to include with the log entry as JSON key-value pairs. Values support templating.

Message Body Example:

{
  "record_id": "{{netsuite_customer.id}}",
  "workflow_step": "validation",
  "timestamp": "{{instance_meta_data.instance_created_time}}"
}

Output

The Log node returns a minimal response confirming the log was recorded.

Success Response:

{
  "status": "Success",
  "node_id": "9",
  "node_name": "Log",
  "body": {}
}

Error Response:

{
  "status": "Errored",
  "node_id": "24",
  "node_name": "Log",
  "body": "Instance with id 696d306cb46e93331ac32f8d not found"
}

Adding to your workflow

1. Add the Log node

   In the workflow editor, click Add Node and select Log from the utility nodes section.

2. Select action

   Choose Log Message from the Action dropdown.

3. Set log level

   Select the appropriate Log Level based on the type of information you’re recording.

4. Configure the message title

   Enter your message in the Message Title field. Use {{variable}} syntax to include dynamic values from previous nodes.

5. Add a message body (optional)

   Expand Message Body to include additional structured data with your log entry.

6. Test the node

   Click the Run tab to execute a test and verify the log output in Logs > Executions.

Examples

Debug SAP Purchase Order Processing

Log detailed information when processing purchase orders from SAP for troubleshooting sync issues.

Configuration:

Field	Value
Log Level	Debug
Message Title	Processing SAP PO {{sap_purchase_order.PONumber}} for vendor {{sap_purchase_order.VendorName}}

Message Body:

    {
      "po_number": "{{sap_purchase_order.PONumber}}",
      "vendor_id": "{{sap_purchase_order.VendorID}}",
      "total_amount": "{{sap_purchase_order.TotalAmount}}",
      "line_item_count": "{{sap_purchase_order.Items.length}}"
    }

Use Case: Track each purchase order as it flows through the workflow to identify where failures occur during high-volume syncs.

Track NetSuite Customer Creation

Record successful customer creation in NetSuite for audit trails.

Configuration:

Field	Value
Log Level	Info
Message Title	Created NetSuite customer {{netsuite_response.entityId}} - {{netsuite_response.companyName}}

Message Body:

    {
      "internal_id": "{{netsuite_response.internalId}}",
      "entity_id": "{{netsuite_response.entityId}}",
      "source_system": "crm_sync",
      "linked_account": "{{linked_account.udf.company_name}}"
    }

Use Case: Maintain a record of all customers created through the integration for compliance and reconciliation.

Warning for Tipalti Payment Validation

Flag potential issues when payment data doesn’t meet expected criteria.

Configuration:

Field	Value
Log Level	Warning
Message Title	Payment validation warning: Vendor {{tipalti_vendor.name}} missing {{validation_result.missing_field}}

Message Body:

    {
      "vendor_id": "{{tipalti_vendor.id}}",
      "payment_amount": "{{payment_request.amount}}",
      "missing_fields": "{{validation_result.missing_fields}}",
      "validation_status": "incomplete"
    }

Use Case: Identify payments that may fail due to incomplete vendor data before they’re submitted.

Error Logging Before Failure Handling

Capture detailed error context before routing to error handling logic.

Configuration:

Field	Value
Log Level	Error
Message Title	API request failed: {{http_response.status}} - {{http_response.body.error.message}}

Message Body:

    {
      "endpoint": "{{http_request.url}}",
      "status_code": "{{http_response.status}}",
      "error_code": "{{http_response.body.error.code}}",
      "request_id": "{{instance_meta_data.instance_id}}",
      "retry_count": "{{loop_node.body.iteration_count}}"
    }

Use Case: Capture comprehensive error details that help diagnose integration failures without needing to reproduce the issue.

Troubleshooting

Log Messages Not Appearing

Problem	Solution
Logs not visible in execution details	Navigate to Logs > Executions and select the specific workflow run. Log messages appear in the node execution details.
Message Title shows raw variable syntax	Verify the variable path is correct. Check that the referenced node executed successfully before the Log node.
Message Body not appearing	Ensure the JSON syntax is valid. Use the code editor’s validation to check for formatting errors.

Variable Resolution Issues

Problem	Solution
Variable returns empty or undefined	Confirm the source node has output data. Run the source node individually to verify its response structure.
Nested properties not resolving	Use dot notation for nested objects: {{node.body.data.property}}. Check the exact path in the source node’s output.
Array values not displaying correctly	Access specific array items using index: {{node.body.items[0].name}} or use a Loop node to iterate.

Execution Errors

Problem	Solution
”Instance not found” error	The workflow execution context is no longer available. This can occur if the workflow was terminated or timed out.
Log node causing workflow delays	Log nodes execute synchronously but should complete instantly. Check if variable resolution is causing delays by simplifying the message title.

Place Log nodes at key decision points in your workflow to create a clear execution trail. This makes debugging complex multi-branch workflows significantly easier.

Next steps

Custom Code node

Process data and add conditional logging.

Rule node

Add conditional logic that determines when to log.

Workflow testing

Verify log output during development.