Skip to main content
This document explains the Current Automation Info node, which provides metadata about the currently running automation, helping you track and reference flow execution details.

​
Node Overview

The Current Automation Info node outputs key information about the current automation and its execution context. It requires no inputs and automatically generates metadata about the current flow run.
Current Automation Info node interface

​
Node Outputs

The node provides several metadata outputs that can be used for tracking, logging, and referencing:
OutputDescriptionExample Value
Run LinkDirect URL to view this specific flow runhttps://www.gumloop.com/pipeline?run_id={your_run_id}&workbook_id={workbook_id}
Run Started TimestampWhen this flow execution began (in UTC)2023-08-15T14:32:17Z
User EmailEmail address of the person who triggered the flowuser@company.com
Flow IDUnique identifier for this specific flow/tabfCcACCY6kf5Foj6g6cEZdG
Run IDUnique identifier for this specific execution9JroUj99fMAWEoCtgXQtQj
Parent Run IDID of the parent run (if this flow was triggered by another flow)bALShPdR6PmV8816HHrJLW
Root Run IDID of the very first run that started this chain of flowspzYEDhXYvkLxsRdPeDvKEF
Flow NameName of the current subflow/tabCustomer Data Processor
Workbook NameName of the workbook containing this flowSales Pipeline Automation
Workbook IDUnique identifier for the entire workbookcAr7Ybw5JxmGjQJAb5vsqD
Note: The Parent Run ID will only be populated if the current flow is running as a subflow of another automation. If the flow is running independently, this value will be empty.

​
Node Functionality

The Current Automation Info node:
  • Automatically generates metadata about the current flow run
  • Requires no configuration or inputs
  • Makes tracking and debugging of flows easier
  • Provides context for logging and monitoring

​
Understanding the IDs and Outputs

​
ID Relationships Explained

Let’s clarify the different IDs with a practical example: Imagine you have a workflow called “Sales Pipeline” (the workbook) with three tabs (subflows):
  1. “Lead Generator” (main flow)
  2. “Email Processor” (subflow)
  3. “Data Enricher” (another subflow)
When you run the main “Lead Generator” flow, and it calls the other subflows, here’s how the IDs work:
OutputMain Flow (Lead Generator)Subflow (Email Processor)Subflow (Data Enricher)
Workbook IDabc123 (same)abc123 (same)abc123 (same)
Flow IDxyz789def456ghi789
Run IDrun123run456run789
Parent Run IDemptyrun123run123 or run456
Root Run IDrun123run123run123
Key Points:
  • Workbook ID stays the same for all tabs/flows in the workbook
  • Flow ID is unique to each tab/flow (Lead Generator, Email Processor, etc.)
  • Run ID is unique for each execution instance
  • Parent Run ID shows which execution triggered this flow
  • Root Run ID always points to the original/first flow that started the chain

​
Practical Use Cases

​
1. Error Tracking in Triggered Flows

One of the most valuable uses is adding this node to triggered flows (like those running on schedules or webhooks) to know when errors occur: 
[Trigger Node] → Current Automation Info → [Main Flow Logic]
                                       ↓
                 [Error Shield] → Slack Notification with Run Link
If something fails, you’ll receive a notification with the exact Run Link to investigate what happened.

​
2. Execution Logging

Keep a record of every time critical flows run: 
Current Automation Info → Google Sheets Writer (Execution Log)
    |
    ↓
[Rest of your flow]
This creates a permanent record with timestamps of each execution, who ran it, and links to review the runs. This allows you to answer questions like “Where did this data come from?” or “When was this processed?” weeks or months later.

​
Best Practices for Placement

  1. For Triggered Flows: Place at the start of the flow to ensure run information is captured even if later steps fail
  2. For Error Tracking: Place outside of subflows or complex logic that might fail
  3. For Complete Logging: Add both at the beginning and end of critical flows to capture start and completion times
  4. For Subflows: If a subflow might be reused in multiple contexts, add this node to understand its execution context

​
Practical Examples

​
Error Notification System

• Current Automation Info
   ↓
• [Complex automation logic in a subflow]
   ↓
• Error Shield (wraps the subflow)
   ↓
• If error occurs:
   ↓
• Combine Text:
  "⚠️ Automation Error in {Flow Name} (Run ID: {Run ID})
   Time: {Run Started Timestamp}
   Triggered by: {User Email}
   Review the run: {Run Link}"
   ↓
• Slack Message Sender (to your #automation-alerts channel)
This gives your team immediate notification when automations fail with a direct link to review what happened. This creates a complete audit trail showing exactly when data was processed and by whom.

​
Important Considerations

  1. The Run Link is particularly valuable for debugging and support as it provides a direct way to view the specific execution details.
  2. Place this node strategically in your flows where it will still execute even if other parts of the flow fail.
  3. For critical workflows, consider adding this node at either the beginning or end to capture complete execution information.
  4. In triggered flows (scheduled or webhook), this node is essential for tracking executions since no user is actively watching the run.
In summary, the Current Automation Info node provides essential metadata about your running automation, and makes it easier to track, reference, and debug your flows.
⌘I