# Automation rules

> Launch approved runtime skills automatically when requests, tasks, notes, or invoices reach defined triggers, with every run visible in Agent Activity.

Source: https://flopinio.com/help/automation-rules · Last updated: 2026-10-29 · Status: Shipped

## Overview

An automation rule pairs one trigger with one compatible skill. When the trigger fires, Flopinio launches a standard agent run, the same runtime used for manual launches, so every automated action stays inspectable.

## Triggers

Triggers are defined by the platform. Some fire immediately; others are periodic scans.

- Request created, or request response overdue.
- Task created, task due soon (next three days), or task overdue.
- Note created.
- Draft invoice ready for preparation.
- Invoice due soon (within seven days) or invoice overdue, for sent invoices with a remaining balance.

## Skills

Each trigger only offers compatible skills, such as request triage or review for new requests, task review for task triggers, note review for new notes, invoice preparation for draft invoices, and invoice follow-up review for due or overdue invoices. Skills and their prompts are curated by the platform; a skill appears only when it is active, automation-safe, and has an active prompt version.

## Create a rule

1. Open Automation rules and start a new rule.
2. Name the rule, choose a trigger, then choose a skill allowed for that trigger.
3. Enable the rule immediately or leave it disabled. Disabled rules stay listed but do not launch runs.
4. Open the latest run from the rule list to inspect what happened.

## Example: Triage every new request

You create a rule named "Triage new requests" with the trigger "Request created" and the request triage skill, and enable it. When Northstar's next email is captured as a request, the rule starts a run. Open the request to review the recommendation and choose **Apply Triage**. Triage recommendations do not appear in Approvals.

## Recommended automations

Your workspace preset can suggest recommended automations. Accepting one creates a normal rule you can edit; ignoring one hides the suggestion.

## Approvals and credits

Automated runs follow the same review steps as manual runs. Apply triage from the request; triage does not create an approval. Workflows that stage approval-backed changes use the approval queue. Rules need AI access. Hosted runs require credits; BYOK generation uses the selected provider key and no hosted credits.

## FAQ

### Can I create a custom trigger?

No. Triggers are platform-defined. You choose which supported trigger and skill to pair.