Skip to main content
The Current Automation Info node provides metadata about the currently running automation, helping you track and reference workflow execution details.

​
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 workflow run.
Current Automation Info node interface

​
What This Node Does

No Configuration Needed

Automatically generates metadata without any setup or inputs required

Tracks Execution Context

Captures when workflows run, who triggered them, and how they’re connected

Enables Debugging

Provides direct links to view specific runs and troubleshoot issues

Creates Audit Trails

Records execution history for compliance and tracking purposes

​
Node Outputs

The node provides several metadata outputs for tracking, logging, and referencing your automations:
OutputDescriptionExample
Run LinkDirect URL to view this specific workflow runhttps://www.gumloop.com/pipeline?run_id=...
Run Started TimestampWhen this workflow execution began (UTC)2023-08-15T14:32:17Z
User EmailEmail of the person who triggered the workflowuser@company.com
The Parent Run ID will only be populated if the current workflow is running as a subflow of another automation. If the workflow runs independently, this value will be empty.

​
Understanding the ID Hierarchy

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

​
Common Use Cases

Error Tracking in Triggered Workflows

Add this node to workflows running on schedules or webhooks to capture run information when errors occur:
[Trigger Node] → Current Automation Info → [Main Workflow 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.

Execution Logging

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

Automated Error Notifications

Build a complete 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 {Workflow 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 with a direct link to review what happened.

​
Best Practices

Place the node at the start of the workflow to ensure run information is captured even if later steps fail. This is essential for scheduled or webhook-triggered automations where no user is actively watching the run.
Place the node outside of subflows or complex logic that might fail. This ensures you can still capture the run details even when other parts of the automation encounter errors.
Add the node both at the beginning and end of critical workflows to capture start and completion times. This provides a complete picture of execution duration and success/failure status.
If a subflow might be reused in multiple contexts, add this node to understand its execution context and trace back to the original triggering workflow.

​
Important Considerations

The Run Link is particularly valuable for debugging and support as it provides a direct way to view the specific execution details in the Gumloop interface.
Place this node strategically in your workflows where it will still execute even if other parts of the workflow fail. This ensures you always have execution information available for troubleshooting.
For critical workflows, consider adding this node at either the beginning or end to capture complete execution information. For maximum visibility, add it at both points.
In triggered workflows (scheduled or webhook-based), this node is essential for tracking executions since no user is actively watching the run in real-time.