Factory.ai

Droid handles the work that keeps coming back.

Automations start Droid on a schedule, from a Slack message, on a GitHub event, or from a webhook. Pick a template or describe the job, and Droid runs it every time the trigger fires.

Set it up once. Droid runs it on every trigger.

Each automation pairs a trigger with instructions. When the trigger fires, Droid starts a session and does the job.

New automation

When

Every day at 9:00

Summarize all open PRs in GitHub and tickets in Linear, call out anything stuck and post the digest in Slack.

Runs on
Droid Computer
Posts to
#eng-standup
  1. 01 / Trigger

    Choose what starts a run

    A schedule, a message in a Slack channel, a GitHub event, or a webhook from any service that can send one. Webhook triggers are in private preview.

  2. 02 / Instructions

    Write the job once

    Droid follows the same instructions on every run, with the model and reasoning level you pick.

  3. 03 / Run

    Droid does the work

    Each run is a session on a Droid Computer, your own machine, or GitHub Actions. Open it to see what Droid did.

Start from the template directory.

The 16 starters from the app, each with its instructions, trigger, and defaults filled in. Point one at your repositories and channels, then create it.

  • Every 15 min

    Ticket to PR

    Pick up ready tickets from your tracker one at a time and drive each to an open pull request.

    Works with Linear
  • Weekdays, every 30 min

    PR Reviewer (GitLab/GitHub)

    Review new pull or merge requests on a schedule and post one comment review per head commit. Works with GitLab as well as GitHub.

    Works with GitHub
  • Weekdays at 9:00

    Daily Status Digest

    A morning digest of your PRs and tickets: what needs your action, what is waiting on others, and what moved since yesterday.

    Works with Slack, Linear, GitHub
  • Weekdays at 6:00

    Code Health

    Rotate through dependency audits, dead code, coverage gaps, and stale docs, landing one small maintenance PR per run.

  • Weekdays, 3 times a day

    Meeting Notes Sync

    Summarize finished meetings, extract action items, and file them into Notion, your CRM, or your tracker.

    Works with Granola, Notion
  • Hourly

    Scheduled Error Triage

    Poll Sentry, Datadog, or another error source hourly, investigate the errors that matter, and report root causes with a fix PR when safe.

    Works with Sentry
  • Weekdays at 8:00

    Slack Digest

    A private morning DM listing the Slack threads waiting on you, mentions to know about, and highlights from your channels.

    Works with Slack
  • Slack message

    Slack Bug Fixer

    Turn bug reports posted in a channel into tickets, a root-cause hypothesis in the thread, and a fix PR when the change is small.

    Works with Slack, Linear
  • Slack message

    Channel Q&A

    Answer questions in a channel from your docs, Notion, tickets, and code, always citing sources in the thread.

    Works with Slack, Notion
  • Slack message

    Slack Ticket Filer

    File actionable channel messages as tickets, deduplicated and routed to the right team, with the link posted back in the thread.

    Works with Slack, Linear
  • Webhook

    Private preview

    Webhook Alert Responder

    Investigate Sentry, Datadog, or PagerDuty alerts as they fire: root-cause analysis and a fix PR when safe.

  • Webhook

    Private preview

    CI Failure Triage

    Classify failed GitHub Actions or GitLab pipelines as flaky, infrastructure, or regression, and name the commit responsible.

    Works with GitHub
  • Webhook

    Private preview

    New Issue Investigator

    Investigate each new Linear, Jira, or GitHub issue: duplicates, likely cause, files involved, and a PR for trivial fixes.

    Works with Linear
  • PR comment

    Review Comment Fixer

    When a teammate comments on a pull request asking for a change, make it, push one commit to the branch, and reply.

  • PR opened / updated

    Test Coverage

    Add focused tests for the code each pull request changes, pushed to the branch with a comment on what is now covered.

  • Push

    Docs Refresh

    Keep the docs in your repo current with each push to the default branch, via a pull request. For the Factory wiki, use AutoWiki.

Don't see your job? Create with DroidArrow Right Icon

Template defaults

Template schedules run in UTC, so check the time before you create one. Webhook templates appear once webhook triggers are on for your organization.

Decide who each automation runs as and who sees its work.

Each automation runs as you or as a service account your team shares. Factory tracks every run and pauses an automation that can't run reliably.

  • Service accounts

    Run shared automations as a service account, with its own connector access and billing.

  • Private or shared

    Keep an automation to yourself or share it with your organization. Session privacy sets who can open each run.

  • Run health

    Every automation shows its status and an events feed of runs, alerts, and webhook deliveries.

  • Automatic pauses

    When five scheduled runs fail in a row, Factory pauses the automation and emails its owner why.

Delegate the work your team repeats.

Start from a template or describe the job. Droid handles every run after that.

Already in a Droid session? Ask Droid to create the automation.

Create from a sessionArrow Right Icon

Ready to build the software of the future?

Start building

Arrow Right Icon