Skip to main content
Automation Suggestions turn recurring requests into scheduled jobs — but only when you tap Accept.

​
Quick Start

1

See pending suggestions

Type /automations in chat. The bot lists each pending suggestion with its own Accept/Dismiss buttons.
/automations
2

Accept from chat

Tap the ✓ Accept button on a suggestion. Exactly one scheduled job is created — nothing runs until you accept.
3

Or create from a template

Skip suggestions and build a job straight from a blueprint:
/blueprint morning-brief hour=8 weekdays=mon-fri

​
How It Works

Two paths lead to the same result — a scheduled job — but only ever on an explicit accept.
PathCommandWhat happens
Accept an existing suggestion/automations → ✓ AcceptMaterialises the suggested blueprint into one job and marks the suggestion accepted.
Create directly from a template/blueprint <name> [slot=value ...]Resolves slots against blueprint defaults and schedules the job immediately.
Button taps travel through the shared callback contract: sug:accept:<id> accepts a suggestion, sug:dismiss:<id> dismisses it. The interactive registry decodes sug:accept:<id> as namespace sug with the remainder as the payload — a Telegram-side detail you never type by hand.

​
Built-in Blueprints

Three blueprints ship ready to use, straight from blueprint_catalogue.py.
NameDescriptionCategoryDefault deliverKey slots
morning-briefDaily morning briefing with news and prioritiesdailytelegramhour (int, 8), minute (int, 0), weekdays (choice, mon-fri), focus (choice, general)
important-mailCheck for important emails at a regular intervalmonitoringtelegraminterval_minutes (int, 30), keywords (str, "urgent,important,deadline")
weekly-reviewEnd-of-week summary and reviewweeklytelegramhour (int, 17), minute (int, 0), weekdays (choice, fri), focus (choice, general)
If your app already registers a custom /automations or /blueprint handler via @bot.on_command, that handler wins — the built-ins step aside for those two names only. All other built-in commands still take precedence.

​
Custom Blueprints (YAML)

Author your own blueprints under ~/.praisonai/blueprints/<name>/blueprint.yaml; a custom blueprint overrides a built-in of the same name. 
name: standup-digest
version: "1.0.0"
description: Team standup digest
category: daily
default_deliver: telegram
prompt_template: "Summarise today's standup for {team}."
schedule_template: "cron:{minute} {hour} * * {weekdays_expression}"
slots:
  - name: hour
    type: int
    default: 9
  - name: minute
    type: int
    default: 30
  - name: weekdays
    type: choice
    default: mon-fri
    choices: [mon-fri, daily, weekends]
  - name: team
    type: str
    default: engineering
Discovery scans each <name>/blueprint.yaml subdirectory — see BlueprintCatalogue._load_from_directory for the exact rule.

​
Chat Commands

/automations

List pending suggestions with inline ✓ Accept / ✕ Dismiss buttons. Telegram only today. Full detail in Bot Chat Commands.

/blueprint

Create an automation from a template: /blueprint <name> [slot=value ...]. Telegram only today. Full detail in Bot Chat Commands.

​
CLI Commands

Drive the same engine from the shell — full flags in Schedule CLI.
CommandPurpose
praisonai schedule blueprint <name>Create a job from a blueprint template
praisonai schedule blueprint-listList available blueprints (built-in + user YAML)
praisonai schedule suggestionsList pending automation suggestions
praisonai schedule suggestion-accept <id>Accept a suggestion and materialise the job
praisonai schedule suggestion-dismiss <id>Dismiss a suggestion
praisonai schedule suggestion-propose <blueprint>Manually propose a blueprint as a suggestion

​
Python Usage

Propose and accept a suggestion programmatically. 
from praisonai.scheduler.suggestion_engine import SuggestionEngine
from praisonai.scheduler.blueprint_catalogue import BlueprintCatalogue

engine = SuggestionEngine()

sug_id = engine.propose(
    "morning-brief",
    slots={"hour": 8, "weekdays": "mon-fri"},
    deliver="telegram",
    reason="Detected daily morning request pattern",
)

if sug_id:
    catalogue = BlueprintCatalogue()
    bp = catalogue.get_blueprint("morning-brief")
    sug = engine.get_suggestion(sug_id)
    resolved = catalogue.resolve_slots(bp, sug.slots)
    prompt = catalogue.materialize_prompt(bp, resolved)
    schedule = catalogue.materialize_schedule(bp, resolved)
    engine.accept(sug_id)
    print(prompt, schedule)
propose() returns None when the pending cap (20) is reached or the same blueprint + slots was suggested within the 24-hour dedup window.

​
User Interaction Flows

Flow A — Accept an existing suggestion in chat: 
User → /automations
Bot  → "💡 You have 1 pending automation suggestion:"
Bot  → "💡 Detected daily morning request pattern
        morning-brief · hour=8, weekdays=mon-fri"
        [✓ Accept]  [✕ Dismiss]
User → taps ✓ Accept
Bot  → "✅ Automation scheduled. Added job 'morning-brief' (schedule cron:0 8 * * mon,tue,wed,thu,fri)"
Flow B — Create directly from a blueprint: 
User → /blueprint
Bot  → "📋 Create an automation from a template:
        • morning-brief — Daily morning briefing with news and priorities
        • important-mail — Check for important emails at a regular interval
        • weekly-review — End-of-week summary and review
        Usage: /blueprint <name> [slot=value ...]
        Example: /blueprint morning-brief hour=8 weekdays=mon-fri"
User → /blueprint morning-brief hour=8 weekdays=mon-fri focus=tech
Bot  → "✅ Automation scheduled from 'morning-brief'. Added job 'morning-brief' (schedule cron:0 8 * * mon,tue,wed,thu,fri)"

​
Safe by Default & Multi-tenancy

The underlying SuggestionStore is a single, global, single-tenant store (~/.praisonai/suggestions.json) with no per-user field on Suggestion. Suggestions are shared across everyone who can reach the gateway — exactly like the praisonai schedule CLI. Access is gated by CommandAccessPolicy (the automations permission is re-checked on every accept/dismiss tap); restrict that policy to admins for multi-user bots. Per-user scoping would require a core data-model change and is out of scope for this wiring.
Nothing is ever auto-created — the engine only materialises a job on an explicit accept. MAX_PENDING_CAP (20), the 24-hour dedup window, and the 3-day TTL are all inherited from the store.

​
Platform Coverage

Telegram-only today. Discord, Slack, and WhatsApp adapters do not register /automations or /blueprint yet — parity is tracked in future PRs. The shared helper module keeps the accept/dismiss/blueprint glue in one place so those adapters can wire it later.
The commands also degrade gracefully: if the scheduler extra isn’t installed, they reply ❌ Automations are not available (scheduler not installed).

​
Best Practices

The suggestion store is single-tenant. Restrict the automations and blueprint permissions in CommandAccessPolicy to admin users so one person’s suggestions aren’t accepted or dismissed by everyone. See Command Access Control.
When a suggestion already exists for a pattern, accept it rather than running /blueprint — the dedup key latches on accept and avoids duplicate jobs.
Drop a blueprint.yaml in ~/.praisonai/blueprints/<name>/ to codify team-specific automations. A custom blueprint overrides a built-in of the same name.
For monitoring blueprints like important-mail, add a --pre-run gate to the resulting job so ticks with no new work spend no tokens. See the pre-run gate in the Schedule CLI.

Bot Chat Commands

Full /automations and /blueprint command details.

Schedule CLI

Blueprint and suggestion subcommands with every flag.

Proactive Delivery

Home channels and delivery tokens for scheduled jobs.

Scheduled Run Policy

Guardrails and the pre-run gate for unattended runs.