Runwork
New Import n8n Workflows

Get started instantly with 8,000+ ready-to-use workflow recipes from the n8n community.

Browse recipes
All Features

Workflows

Multi-step processes that span hours or days

Long-running business processes with human-in-the-loop approvals, automatic retries, and full execution history. Workflows survive infrastructure restarts and never lose state.

Capabilities

Durable Execution

State persists across restarts. Workflows never lose progress.

Multi-Step Pipelines

Chain operations with branching logic, conditional paths, and error handling.

Human-in-the-Loop

Pause workflows for manual approval. Resume when a human clicks "approve" or "reject".

Automatic Retries

Failed steps retry automatically with configurable backoff. Transient errors don't break your process.

Instance Tracking

Monitor workflow instances: queued, running, paused, errored, or complete. Full visibility.

Execution History

See every step, every decision, every retry. Debug complex processes with confidence.

Use Cases

Order fulfillment Approval chains Onboarding sequences Data migration Multi-stage deployments Contract signing

Why It Matters

How It Works

Workflows in Runwork are durable, long-running processes designed for business operations that span minutes, hours, or even days. Unlike simple automations that execute immediately and complete, workflows maintain state across time, handle failures gracefully, and can pause for human decisions before continuing.

A workflow is a series of steps that execute in sequence or parallel. Each step can query your entities, call integrations, or invoke AI agents. The key difference from automations is durability: if the infrastructure restarts mid-execution, your workflow picks up exactly where it left off. No lost state, no duplicate operations.

Human-in-the-loop approval is built in. When a workflow reaches an approval step, it pauses and notifies the designated approver via email, Slack, or in-app notification. The approver reviews the context, clicks approve or reject, and the workflow continues down the appropriate path. This enables real business processes like expense approvals, contract reviews, or hiring decisions—not just automated code.

Creating workflows follows the same conversational pattern as everything in Runwork. Tell the Work Assistant: "When a contract is uploaded, extract the key terms, send it to legal for review, and if approved, create the customer record and notify sales." Runwork generates the workflow with all the necessary steps, approval gates, and error handling.

Every workflow instance is tracked from start to finish. You can see which instances are queued, running, paused for approval, errored, or complete. The full execution history shows every step taken, every decision made, and every retry attempted. When something goes wrong, you know exactly what happened and can replay the workflow from any point.

Don't want to start from scratch? Runwork lets you import n8n workflows directly. With over 8,000 community-built workflow templates available in our recipe library, you can find proven automation patterns for everything from lead nurturing to invoice processing—and have them running as full Runwork apps in minutes.

Frequently Asked Questions

What is a workflow in Runwork?
A workflow is a durable, multi-step process that can span hours or days. Unlike automations that execute immediately, workflows maintain state across time, can pause for human approvals, handle failures with automatic retries, and never lose progress—even if infrastructure restarts mid-execution.
How are workflows different from automations?
Automations are single-step reactive functions (when X happens, do Y). Workflows are multi-step processes that span time and can include human decisions. Use automations for immediate reactions. Use workflows for processes like approval chains, onboarding sequences, or order fulfillment that require multiple steps and human input.
How does human-in-the-loop approval work?
When a workflow reaches an approval step, it pauses and notifies the designated approver via email, Slack, or in-app notification. The approver sees the relevant context, clicks approve or reject, and the workflow continues down the appropriate path. Workflows can have multiple approval gates with different approvers.
What happens if a workflow step fails?
Failed steps automatically retry with configurable exponential backoff. If a step continues to fail after retries, the workflow pauses in an errored state. You can see exactly what went wrong in the execution history, fix the underlying issue, and replay the workflow from the failed step without losing any progress.
Can I track the status of running workflows?
Yes. The workflow dashboard shows all instances with their current status: queued, running, paused (awaiting approval), errored, or complete. You can drill into any instance to see the full execution history—every step, decision, and retry. This gives you complete visibility into your business processes.
Can I import existing workflows from n8n?
Yes! Runwork supports importing n8n workflows directly. Just paste an n8n marketplace URL or upload your workflow JSON, and Runwork converts it into a full application with UI, automations, and workflows. We have over 8,000 ready-to-use workflow recipes available in our recipe library, so you can get started instantly with proven automation patterns.

Related Features

See How Teams Use Workflows

Ready to try Workflows?

Start vibe-coding with Runwork today.