This document explains the Error Shield node, which protects your workflow by catching and handling errors.

​
What It Does

Error Shield works like a protective wrapper around other nodes - if something goes wrong inside, it catches the error instead of letting your workflow crash.

​
Inputs and Outputs

​
Inputs

  • Wrapped Node: The node you want to protect from errors
  • Pass Inputs Through: When enabled, you can access the original input that caused an error

​
Outputs

Two possible paths:
  • Success Path: Data that processed successfully
  • Error Path: Triggered when an error occurs
When “Pass Inputs Through” is enabled:
  • Success Path: Processed data
  • Error Path: The original input that caused the error

​
Examples

​
Basic Example

Website Scraper wrapped in Error Shield:
Input: "https://example.com"

If successful:
- Success Path: Scraped content
- Error Path: Not triggered

If failed:
- Success Path: Not triggered
- Error Path: "https://example.com" (if Pass Inputs Through enabled)

​
Loop Mode Example

Website Scraper in Loop Mode wrapped in Error Shield:
Input: [
  "https://site1.com",
  "https://site2.com" (fails),
  "https://site3.com",
  "https://site4.com" (fails)
]

Results:
- Success Path: [site1 content, site3 content]
- Error Path: ["https://site2.com", "https://site4.com"] (if Pass Inputs Through enabled)

​
Working with Join Paths

You can use Join Paths to reconnect the success and error paths into a single workflow:

​
Basic Join Pattern

Error Shield
├─ Success Path → Process Success →
└─ Error Path   → Handle Error   → Join Paths → Continue Workflow

​
Example Use Case

Scrape Websites → Error Shield
                  ├─ Success → Extract Content   →
                  └─ Error   → Log Failed URLs   → Join Paths → Save Results
By using Join Paths after Error Shield, you can:
  • Handle both successful and failed cases
  • Continue your workflow with a single path
  • Process all results together, regardless of success/failure

​
Common Use Cases

  1. Web Scraping: Catch and handle failed website requests
  2. File Processing: Continue even if some files can’t be processed

​
Step-by-Step Usage

  1. Drag Error Shield onto canvas
  2. Place the node you want to protect inside it
  3. Enable “Pass Inputs Through” if you need to know which inputs failed
  4. Connect both success and error paths
  5. Use Join Paths to reunite the paths if needed
  6. Add error handling for failed cases

​
Additional Resources