Current Automation Info
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.
Node Outputs
The node provides several metadata outputs that can be used for tracking, logging, and referencing:
Output | Description | Example Value |
---|---|---|
Run Link | Direct URL to view this specific flow run | https://www.gumloop.com/pipeline?run_id={your_run_id}&workbook_id={workbook_id} |
Run Started Timestamp | When this flow execution began (in UTC) | 2023-08-15T14:32:17Z |
User Email | Email address of the person who triggered the flow | user@company.com |
Flow ID | Unique identifier for this specific flow/tab | fCcACCY6kf5Foj6g6cEZdG |
Run ID | Unique identifier for this specific execution | 9JroUj99fMAWEoCtgXQtQj |
Parent Run ID | ID of the parent run (if this flow was triggered by another flow) | bALShPdR6PmV8816HHrJLW |
Root Run ID | ID of the very first run that started this chain of flows | pzYEDhXYvkLxsRdPeDvKEF |
Flow Name | Name of the current subflow/tab | Customer Data Processor |
Workbook Name | Name of the workbook containing this flow | Sales Pipeline Automation |
Workbook ID | Unique identifier for the entire workbook | cAr7Ybw5JxmGjQJAb5vsqD |
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):
- “Lead Generator” (main flow)
- “Email Processor” (subflow)
- “Data Enricher” (another subflow)
When you run the main “Lead Generator” flow, and it calls the other subflows, here’s how the IDs work:
Output | Main Flow (Lead Generator) | Subflow (Email Processor) | Subflow (Data Enricher) |
---|---|---|---|
Workbook ID | abc123 (same) | abc123 (same) | abc123 (same) |
Flow ID | xyz789 | def456 | ghi789 |
Run ID | run123 | run456 | run789 |
Parent Run ID | empty | run123 | run123 or run456 |
Root Run ID | run123 | run123 | run123 |
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:
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:
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
-
For Triggered Flows: Place at the start of the flow to ensure run information is captured even if later steps fail
-
For Error Tracking: Place outside of subflows or complex logic that might fail
-
For Complete Logging: Add both at the beginning and end of critical flows to capture start and completion times
-
For Subflows: If a subflow might be reused in multiple contexts, add this node to understand its execution context
Practical Examples
Error Notification System
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
-
The Run Link is particularly valuable for debugging and support as it provides a direct way to view the specific execution details.
-
Place this node strategically in your flows where it will still execute even if other parts of the flow fail.
-
For critical workflows, consider adding this node at either the beginning or end to capture complete execution information.
-
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.