Automate the work that keeps coming back

By Factory Team - September 30, 2026 - 3 minute read

Product

A lot of engineering work these days can feel reactive or repetitive: following up on pull requests, investigating CI failures, running security checks, or updating documentation as features ship. Other recurring tasks also take up part of everyday work: mornings may start with Slack and email catch-up; meetings need recaps, follow-up tickets, and next steps. Each task takes time, and switching between them interrupts focused work.

Automations are generally available in Factory and many of our enterprise customers have been deploying them throughout their organizations. Describe a recurring workflow, choose a schedule or event trigger, and Droid runs it to the desired result. You choose the model for each task, balancing capability and cost, and the machine it runs on.

What teams automate today

Ticket to PR. Droid picks up ready tickets from Linear or Jira, implements the changes, and opens a pull request for review.
Code Review and Fixer. Droid reviews pull requests and posts findings on the PR. Add Review Comment Fixer to address requested changes with a commit.
Security Audit. A scheduled GitHub Actions workflow audits a repository each week. Droid checks potential security issues against the code and reports its findings.
PR Babysitter. Droid checks open pull requests for failing CI and works on fixes. Add CI Failure Triage to classify failed pipelines as flaky, infrastructure, or regression.
Morning brief. Start the day with a private Slack message covering threads, pull requests, and tickets that need your attention.
What shipped this week? A custom automation turns the week's merged pull requests into a short Slack recap, complete with a custom meme using image generation celebrating a feature launch, stubborn bug fix, or long-awaited cleanup.

Incident response

1 / 4

Other templates turn actionable Slack messages into Linear tickets, investigate incident alerts, sync meeting notes and action items, or update documentation as code changes.

For workflows specific to your team, create a custom automation to monitor key metrics or prepare release notes. Set the instructions, trigger, model, and computer.

Describe the automation, or start from a template

Select Create with Droid and describe the workflow and intended outcome in natural language. Droid then asks for any missing details before creating the automation. This also works from an existing session: Take this analysis we just did of our error logs over the weekend and run it every Monday at 9am.

The Automations Marketplace provides pre-filled use cases and setup flows for popular use cases including Code Review, Security Audit, PR Babysitter, and more.

Every automation has four parts:

TriggerSchedule, Slack, GitHub, or webhook.

InstructionsPrompt or template

ModelPick any model and reasoning level

ComputerYour machine or a Droid Computer

AutomationRuns as you or a service account

Your model, your machines

Model and reasoning level are configurable by the user per automation. A lower-cost model may be chosen to handle a daily digest, while a more capable model for important deep security reviews.

Choose any model, bring your own keys (BYOK), or use Factory Router (subject to your organization's model policies) to automatically delegate to the right model for the job. Among current Automations users, 30% of all code review automation runs use an open-weight model.

Runs can execute locally, on a connected machine you provide, or on a Factory-managed Droid Computer.

Connected and governed

During an automation run, Droid uses connected tools to gather context and deliver results. For example, a webhook from an alerting tool can start an investigation, or a scheduled daily automation can summarize activity across repositories and Slack.

Automations can run under a user's identity or a service account. Visibility settings control access, and run history provides a record of execution.

Each run opens a session you can inspect. The automation's overview includes an Events feed and a 7-day success rate. Failure notifications alert the owner, with follow-up digest emails when an automation fails.

How our customers and Factory use Automations

Among enterprise organizations who have been using Factory Automations in the past 30 days, 52% used automated code review, 48% used security review, and 35% used AutoWiki. And automation session volume grew 51% compared with the previous 30 days.

At Factory, Automations are used across all teams, every day. Droid responds to incident threads, with median acknowledgment of 20 seconds and resolution time of 6 minutes. Droid reviewed 99.5% of mergeable pull requests and engineers resolved 81% of its comments.

Get started today

Automations are available for all users starting today. Open Automations in the Factory app and select Create with Droid, or choose a template.