Free AI Automation Templates for Obsidian (Any Role)

AI automations rarely fail because the model is weak. They fail because nobody owns them, nothing says what they may do, and nobody checks them each week.

Three free Obsidian notes fix that: an intake scorecard to pick the workflow, an approval matrix to decide what can run, and a weekly review to keep it honest. Copy them below. For the fuller model, see the vault workflows guide.

Template one: choose the workflow before you build it

One candidate, one owner, one reason to build it now. Score value, complexity and risk so the loudest idea doesn't win by default.

# AI Workflow Intake Scorecard

## Workflow Candidate
- Name:
- Owner:
- Trigger:
- Current manual process:

## Business Value (0-5)
- Revenue impact:
- Time saved:
- Error reduction:

## Implementation Complexity (0-5)
- Data access complexity:
- Integration complexity:
- Change-management complexity:

## Risk Exposure (0-5)
- Data sensitivity:
- Compliance/approval constraints:
- Failure blast radius:

## Decision
- Composite score:
- Recommended action: pursue now | queue | reject
- Why:

If you can't name the owner or the trigger, you don't have a workflow yet.

Template two: approvals are part of the architecture

Approvals shape the workflow from the start, so set them before launch, not after it proves itself.

# AI Approval Matrix

## Policy
- Default mode: approvals required for high-impact actions
- Escalation owner:
- Incident contact:

## Action Classes
- Read-only research
- Draft generation
- Internal notifications
- External communications
- Data mutation
- Financial operations

## Approval Rules
- Auto-allowed:
- Human-approval required:
- Dual-approval required:
- Blocked:

## Logging Requirements
- Event name:
- Actor:
- Timestamp:
- Input summary:
- Output summary:
- Rollback path:

Once the matrix exists, it is clear which automations can move fast and which only look low risk.

Template three: the weekly review that keeps automation from drifting

Without a review, an approval policy set once is never read again until something breaks. Catch drift in a calm weekly pass instead.

# Weekly AI Risk Review

## Week of
- Date range:
- Reviewer:

## Reliability
- Incidents this week:
- Top recurring failure mode:
- Mean time to recovery:

## Safety and Governance
- Approval bypasses detected:
- Access scope changes:
- New compliance concerns:

## Product and Revenue
- Workflows with highest ROI:
- Workflows with poor ROI:
- Biggest conversion blocker:

## Actions for next week
- [ ] Reliability hardening task
- [ ] Approval policy update
- [ ] Conversion-path improvement

It keeps reliability and revenue on one page: a workflow can impress and still waste time, or pay off while piling up approval debt.

How to run all three each week

1. Score the top candidates before you argue for one.
2. Update the approval matrix before launch.
3. Run the weekly review and leave with one reliability task and one business task.

Where templates turn into theater

• Filling them in after the decision instead of before it.
• Scoring every idea as high value, so the scorecard ranks nothing.
• Approval rules with no named escalation owner.
• A weekly review that names problems but creates no next action.

Done in the first week

• One workflow selected to build now.
• One workflow queued or rejected.
• One escalation owner named for high-impact actions.
• One reliability task and one business task from the weekly review.

If the notes don't produce those decisions, simplify the loop until they do.

Next: build the workflow

Keep the work in your vault with SystemSculpt for Obsidian and the workflow docs. SystemSculpt is free to install. Hosted AI uses credits, and paid plans are $9 a month or $90 a year: compare plans.