Runwork
All Features

Build

Automations

It runs when it should, whether or not anyone is at their desk.

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.

Active Automations
5 rules
When New deal closes in HubSpot
Then Create invoice in Stripe + notify #sales
HubSpot Stripe Slack
142 runs
When New customer signs up
Then Send welcome email + create onboarding task
Gmail Tasks
89 runs
When Support ticket priority is "urgent"
Then Page on-call engineer + create incident
Slack Linear
23 runs
When Invoice is overdue by 7 days
Then Send reminder email + flag in dashboard
Stripe Gmail
57 runs
When New lead added from website form
Then Enrich with Clearbit + add to HubSpot sequence
Clearbit HubSpot
214 runs

What Automations gives you

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.

Why Automations matters

How Automations 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 your agent.

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, whether that means sending a Slack message, creating a HubSpot contact, or processing a Stripe charge. You can trigger workflows for multi-step processes that require approvals or human input.

You create automations in your own AI tool. Tell your agent: "When a new customer signs up, send them a welcome email and create a task for the sales team to follow up." Your agent writes the automation, tests it in a sandbox, and deploys it to your team cloud, where it keeps running for everyone. You can review the code, modify it, or have your agent iterate.

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.

Sales, marketing, operations, finance: the work that runs on a schedule and nobody enjoys owning. Describe one and your agent builds it, then it runs in your team cloud where everyone's AI can reach 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 your agent 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." Your agent writes the automation code and deploys it to Runwork, and you can review and modify it 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.
Do we have to build every automation from scratch?
No. Describe the one you need and your agent builds it against your real data and the tools you have already connected, so it fits your process instead of a generic template. It then runs in your team cloud where everyone's AI can reach it.

Use Cases

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

Related Features

See How Teams Use Automations

Ready to try Automations?

One shared cloud under the AI tools your team already uses.