Browse topics

Documentation

AI Workflows

How Effitrio’s AI plans work, what triggers them, and how approval keeps you in control

AI in Effitrio is built around goals: multi-step plans that can include drafting content, analyzing expenses, or running catalog workflows (such as overdue invoice reminders).

How AI works (high level)

  1. You ask for help from the chat on the Dashboard, or a scheduled/automation path creates a goal when applicable.
  2. The Effitrion planner turns that into an actionable graph (steps). Some steps are automatic; others stop at an approval gate. It depends on the actions involved in the goal.
  3. You can review pending work in the AI Action Center (/dashboard/action-center).
  4. After approval, execution is queued; you can track status (in progress, completed, failed, rejected, expired).

If the chat returns an AI Action Plan, read the summary and follow the prompt to open the Action Center when approval is required.

What triggers AI suggestions and goals

Typical triggers include:

  • Natural language requests in Dashboard chat (for example reminders, validation, or workflow kickoff when supported).
  • Catalog workflows (for example overdue invoice reminder flows) when you start or complete steps that create a goal.
  • Guardrails in the product — duplicate or recently completed similar goals may be blocked with a clear message so you are not spammed with repeat runs. example, not to send multiple reminders to client within short time frame.

Reviewing AI proposals

Open /dashboard/action-center to see goals with their status, risk level, and summary. Select a goal to inspect steps, step outcomes, and any drafts attached to the workflow.

For workflows that produce email drafts, you can step through drafts, edit subject/body where supported, and mark which drafts are approved for sending before final goal approval.

Approving and rejecting

  • Approve goal — allows execution to proceed after any required draft approvals are satisfied.
  • Reject goal — stops the run; the goal ends in a rejected state.
  • Per-draft approve / unapprove — for reminder-style flows, controls which drafts are eligible to be send to client when the goal is executed.

Example goals in Effitrio

  • Invoice overdue reminders — Effitrio drafts payment reminder emails for overdue invoices, pauses for your review/approval, then sends only the reminders you explicitly approve.

Safety and control principles

  • Approval gates for sensitive outcomes (especially outbound communications).
  • Expiry — goals awaiting approval expire after a configured window so stale plans do not linger indefinitely.
  • Concurrency limits — caps on how many active goals a workspace can hold at once.
  • Retries — transient step failures may retry up to a fixed maximum before the goal fails visibly.
  • Duplicate protection — cooldown-style rules reduce repeated goals for the same workflow shortly after a completion.