← NormanCONTENT HISTORY

Update to Norman

Snapshot Oct 27, 2026 · 00:14 UTC · version 1.1.0

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save Norman and check future changes in Following.

Up to 3 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Find overdue invoices and send payment reminders (Zahlungserinnerungen / Mahnungen) to clients. Use when the user asks about unpaid invoices, overdue payments, payment reminders, Mahnung, or chasing payments.",
  "included_files": [],
  "name": "overdue-reminders",
  "skill_md_contents": "---\nname: overdue-reminders\ndescription: Find overdue invoices and send payment reminders (Zahlungserinnerungen / Mahnungen) to clients. Use when the user asks about unpaid invoices, overdue payments, payment reminders, Mahnung, or chasing payments.\nversion: 1.1.1\ndisable-model-invocation: true\nargument-hint: \"[client name or 'all']\"\nmetadata:\n  openclaw:\n    emoji: \"\\u23F0\"\n    homepage: https://norman.finance\n    requires:\n      mcp:\n        - norman-finance\n---\n\nHelp the user manage overdue invoices and send payment reminders:\n\n## Step 1: Find overdue invoices\n- Call `list_invoices` to get all invoices\n- Filter for invoices that are past their due date and still unpaid\n- If `$ARGUMENTS` specifies a client name, filter to that client only\n- Present a summary table: Client, Invoice #, Amount, Due Date, Days Overdue\n\n## Step 2: Check what Norman already sent\n- Call `list_invoice_emails` for each overdue invoice. It lists every reminder with its level and status, and `nextReminder`, the reminder Norman's own rule sends next\n- Leave out an invoice with a planned reminder (`nextReminder`, or an email with status `scheduled`) or a reminder sent in the last few days, unless the user asks for it by name\n- An invoice with `remindersActive` true is reminded automatically by the company's rule. Say so instead of sending by hand\n\n## Step 3: Levels\nNorman keeps the reminder levels; a reminder sent by hand takes the level after the last one:\n- **Payment reminder** (level 1): friendly tone\n- **First dunning notice** (level 2): firmer, may carry a fee\n- **Final notice** (level 3): last notice before further steps\n\n## Step 4: Review before sending\nFor each overdue invoice (or batch per client):\n- Show the invoice details: amount, due date, days overdue\n- Show the client's contact info from `get_client`\n- Let the user decide whether to send a reminder or skip\n\n## Step 5: Send reminders\n- Use `send_invoice_overdue_reminder` for each approved reminder\n- Wait for user confirmation before each send\n- Omit `subject` and `body`: Norman uses the company's template for that level in the invoice's language. Write your own text only when the user asks for it\n- Pass `fee` only when the user names a dunning fee. The client pays a fee by bank transfer; a reminder with a fee has no online payment button\n- A send that fails returns an error with the reason. Report it; do not say the reminder went out\n\n## Automatic reminders\n- To let Norman remind on its own, call `update_invoice` with `autoReminders: true`, after the user agreed. This also works for an invoice that is already issued. `remindersPaused: true` stops them for one invoice\n- `get_invoice_email_settings` shows the rule (days after the due date and fee per level); change it with `update_invoice_email_settings` only when the user asks. Automatic reminders need a paid plan\n- `skip_invoice_reminder` stops one planned reminder\n\n## Step 6: Summary\nPresent a final report:\n- Total overdue amount across all clients\n- Number of reminders sent\n- Any invoices the user chose to skip (and why)\n- Suggest scheduling a follow-up check in 7 days\n\nImportant:\n- ALWAYS let the user review and approve each reminder before sending\n- Never send reminders automatically without explicit confirmation\n- DE: A Mahnung (formal dunning letter) has legal implications - make sure the user is aware\n- PL: A wezwanie do zapłaty (formal payment demand) has legal implications and is a prerequisite before court proceedings - make sure the user is aware\n- Suggest checking if a payment was recently received but not yet linked (use `search_transactions`)\n"
}

SHA-256 of public snapshot: 9ceeb37a7ed74b54c709b58388d9fbf4e5941afcab0eaaaa42bb040b76b00ef7