Runwork
8,000+ Recipes Don't start from scratch

Browse ready-to-use automation patterns for sales, marketing, operations, and more.

Browse recipes
All Features

Automations

Event-triggered logic that runs itself

Set it and forget it. Automations respond to data changes, scheduled times, or manual triggers. Code-first but generated via natural language. Powerful without the complexity.

Capabilities

Event Triggers

React to data changes, app lifecycle events, or custom signals. When X happens, do Y.

Schedule Triggers

Run automations on a cron schedule. Daily cleanups, weekly reports, monthly aggregations.

Manual Triggers

Click a button to run an automation. Perfect for on-demand tasks.

Integration Access

Automations can call any connected integration. Send Slack messages, create HubSpot contacts, charge Stripe customers.

Entity Access

Read and write workspace entities. Update records, create new entries, aggregate data.

Error Handling

Built-in logging, error capture, and retry logic. Know when things fail and why.

Use Cases

Welcome email on signup Slack alert on new lead Daily report generation Data cleanup tasks Cross-app syncing Notification workflows

Why It Matters

How It Works

Automations in Runwork are event-driven functions that execute automatically when specific conditions are met. Unlike visual automation builders that limit you to predefined actions, Runwork automations are code-first—giving you full flexibility while still being easy to create through natural language with the Work Assistant.

Every automation starts with a trigger. Event triggers respond to data changes: when a customer is created, when an order status updates, when a specific field changes. Schedule triggers run on a cron schedule—daily cleanups at midnight, weekly reports every Monday, monthly aggregations on the first of each month. Manual triggers let you run automations on-demand with the click of a button.

The automation body is where the logic lives. You have full access to your workspace entities—query customers, update orders, create new records. You can call any connected integration—send a Slack message, create a HubSpot contact, process a Stripe charge. You can trigger workflows for multi-step processes that require approvals or human input.

Creating automations is conversational. Tell the Work Assistant: "When a new customer signs up, send them a welcome email and create a task for the sales team to follow up." Runwork generates the automation code, tests it in a sandbox, and deploys it to production. You can review the code, modify it manually, or iterate through more conversation.

Reliability is built in. Automations run on Runwork's global edge network with automatic error handling, retry logic, and comprehensive logging. When something fails, you know exactly what happened and why. Failed automations can be replayed with a single click once the underlying issue is fixed.

Need inspiration? Browse our recipe library with over 8,000 automation patterns covering sales, marketing, operations, finance, and more. You can also import n8n workflows directly—paste a workflow URL and Runwork builds a complete app around it.

Frequently Asked Questions

What is an automation in Runwork?
An automation is an event-driven function that runs automatically when specific conditions are met. Automations can be triggered by data changes (a new customer created), schedules (every Monday at 9am), or manual actions (clicking a button). They have full access to your workspace data, integrations, and workflows.
How do I create an automation without coding?
Use the Work Assistant to describe what you want in natural language. For example: "When a new order is placed, send a Slack notification to the sales channel and update the customer record with the order count." Runwork generates the automation code automatically, which you can review and modify if needed.
What can automations access in my workspace?
Automations have full access to your workspace entities (customers, orders, products), connected integrations (Slack, HubSpot, Stripe), and workflows. They can read and write data, call external APIs through integrations, and trigger multi-step processes. Access is governed by the same permissions system as your apps.
How are automations different from workflows?
Automations are single-step reactive functions—when X happens, do Y. Workflows are multi-step processes that can span time and require human input, like approval chains or onboarding sequences. Automations often trigger workflows: "When a contract is uploaded, start the legal review workflow."
What happens if an automation fails?
Runwork provides comprehensive error handling with automatic retries, detailed logging, and failure notifications. You can see exactly what went wrong in the automation logs. Failed automations can be replayed with a single click once the underlying issue is resolved, without losing any data.
Are there pre-built automation templates I can use?
Yes! Runwork has a library of 8,000+ automation recipes covering sales, marketing, operations, finance, and more. Browse the recipe library to find patterns that match your needs, or import n8n workflows directly. Each recipe becomes a complete application with UI, database, and APIs included.

Related Features

See How Teams Use Automations

Ready to try Automations?

Start vibe-coding with Runwork today.