Esc

↑↓ move↵ openIndex · Pagefind
Admin and security / Automations

Automations

Build "when this happens, if that is true, then do this" rules without code. Notify people, create tasks and drafts, assign work or call a webhook when a project record changes or on a schedule.

On this page

An automation is a rule with three parts: When something happens (or on a schedule), If your conditions are true, Then run one or more actions. Company admins build company-wide rules in Company Admin → Automations. Project admins build rules for one project in that project’s Automations tool.

Start from a template

The Templates gallery has ready-made rules for general contractors:

  • Overdue RFI escalation: every weekday at 8:00, notify the assignees, RFI manager and project manager about RFIs 3 or more days overdue.
  • Submittal due reminders: every weekday at 7:00, remind whoever holds the ball on submittals due in 3 days.
  • Change order approved: tell the team: notify the project executive, accounting and the creator.
  • COI expiring: open a renewal follow-up: when a certificate is 30 days from expiring, open a renewal follow-up due in 7 days and tell the company admins.
  • Pay app certified: notify AR: tell accounting the amount due.
  • Daily log missing by 6 pm: remind the superintendent on each project without a completed log for today.
  • Punch item overdue: notify the assignees and punch item manager.
  • Budget line over 90%: every Monday, alert the project manager about budget lines whose committed and direct costs passed 90% of the revised budget.
  • RFI answered: review task and Change event: draft change order.

Pick Use template, review every step, then save. Nothing runs until you save with Turn on after saving ticked.

Build a rule

  1. Name it and choose where it applies

    On the company page, Applies to is All projects or one project. On a project’s Automations tool, rules apply to that project.

  2. When

    Something happens lists every project record event: an RFI created, answered or closed; a submittal submitted, returned or approved; a change order created, approved, rejected or executed; a change event created; a pay application submitted, certified or paid; a daily log completed; a punch item closed; an inspection item failed; an observation created; a document version, drawing set release, permit status change, schedule publication, task completed, insurance certificate expiring and more.

    On a schedule runs every day, on weekdays or once a week at a time in your time zone. Under For each you can have it check records: overdue RFIs, submittals, punch items, tasks or observations; items a number of days before or after their due date; insurance policies before they expire; projects missing today’s daily log; or budget lines over a percent of budget. A schedule acts on each matching record once a day.

  3. If (optional)

    Add conditions on the event, the record or the project: status, priority, amount, due date, days overdue, assignee, project, custom fields and more. Use all of these for AND and any of these for OR, and add a group to mix them. Dates accept today, today+7 or today-3.

  4. Then

    Add up to 10 actions; they run in order. Start approval workflow (on change order, pay application and submittal triggers) starts the matching policy from Company Admin → Approvals, or returns the run already in progress. Text can include placeholders such as {{project.name}}, {{resource.number}}, {{resource.days_overdue}} or {{link}}. Open Placeholders you can use in text for the full list for your trigger.

  5. Test, then turn it on

    Save, then use Test with a sample on the rule’s page. It shows whether the conditions match and exactly what each action would do, without creating or sending anything.

Who receives notifications

Recipients can be specific people, project team roles (for example Project Manager or Superintendent from the project directory), the record’s assignees, creator or manager, a distribution group, you, or the company admins. A notification and its email go only to active people in your company who can open the record themselves; anyone else is left out and the run log says so. Each person can turn automation emails off under Automation messages in their notification settings.

Whose permissions it uses

Every action runs with the permissions of the rule’s owner: the last person who saved it. If the owner couldn’t create a change order by hand, the rule can’t either; the run log shows the action as failed and the owner is told. If the owner later loses the right to manage automations, the rule pauses until another admin saves it and becomes the owner. Changes made by an automation show in each record’s history as made by the automation on the owner’s behalf.

Run history and errors

Each rule has a Run history with the trigger, the record, which conditions matched and what each action did, with links to anything it created. The Automations page shows runs and failures in the last 24 hours and a Needs attention list. Failed actions retry automatically with increasing delays. The owner is notified when a rule starts failing, and a rule pauses itself after 25 failed runs in a row. Versions keeps every saved version of the rule.

Safety limits

  • A rule runs at most once per event, or once per record per day for schedules.
  • A change an automation makes never triggers the same automation again, and chains of automations stop after 3 steps.
  • Each rule runs at most Max runs per hour times (60 by default). Runs over the limit are logged as skipped.

Developers can manage the same rules over the REST API: see the Automations API.

Keep exploring

Related across os.construction

Run it on your own project.

Start a 14-day free trial. Want a say in what ships next? Join the founding program.

Your role (optional)

14-day free trial. Pricing for paid plans isn't set yet. Talk to us. Already have an account? Sign in →

Ask the OS

Reading this page

Ask anything about this page. Answers use what you're reading as context.

Suggested

    AI · may be imperfect · sample data where shown

    Open file