Skip to main content

Content Tagged "workflow-automation"

This page collects all articles and projects tagged workflow-automation. Tags help you navigate by tool, theme, or topic—whether you're looking for content on specific technologies like n8n or Databricks, or broader themes like workflow automation or hockey analytics.

Content spans agentic engineering, production AI agents, data pipelines, full-stack work, and hockey analytics. Browse other tags or case studies for applied examples.

Projects describe case studies with real outcomes—conversational analytics prototypes, AI feedback agents, automated content pipelines, and hockey analytics dashboards. Writing posts cover implementation details, tool comparisons, and lessons learned. If you're looking for something specific, the writing index and portfolio offer alternative ways to explore.

Writing

From Unused Dashboards to Unused AI Output — The Next Shift Is Operations, Not More Artifacts

analysis ·
Dashboards failed because they never entered daily action. Generative AI is repeating the trap with decks, drafts, and more boards. The shift is embedding agents into operations with policy and ROI discipline.

n8n HTTP Request Node: Calling External APIs from Your Workflows

tutorial · · Updated
The HTTP Request node is the workhorse of n8n — it connects your workflows to any API that accepts HTTP calls. Here is how to configure it correctly, handle authentication, and deal with real-world API quirks.

n8n Error Trigger: Workflow-Level Error Catching and When It Actually Fires

tutorial · · Updated
The n8n Error Trigger node is a workflow that runs when another workflow fails — but the when and why are full of edge cases. Here is how it actually works, what it misses, and how to build reliable error handling in production n8n.

n8n getWorkflowStaticData: 64KB of Cross-Execution State Without External Dependencies

tutorial · · Updated
Most n8n state persistence requires Redis, a database, or a file. getWorkflowStaticData lets you store up to 64KB of data that survives between workflow executions with zero infrastructure — built right into the workflow engine.