nexo_followup_create
Create autonomous agent followups to verify or execute actions, with optional scheduling, recurrence, and priority settings.
Instructions
Create a new agent followup (autonomous task).
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Unique ID starting with 'NF' (e.g., NF-MCP2). | |
| description | Yes | What to verify/do. | |
| date | No | Target date YYYY-MM-DD (optional). | |
| verification | No | How to verify completion (optional). | |
| reasoning | No | WHY this followup exists — what decision/context led to it (optional). | |
| recurrence | No | Auto-regenerate pattern (optional). Formats: 'weekly:monday', 'monthly:1', 'monthly:15', 'quarterly'. When completed, a new followup is auto-created with the next date. The completed one is archived with date suffix. | |
| priority | No | critical, high, medium, low (default: medium). | medium |
| internal | No | '1'/'true' hides from default user views (agent bookkeeping, protocol, audit). Leave empty to auto-classify by ID prefix. | |
| owner | No | 'user' | 'waiting' | 'agent' | 'shared'. Leave empty for auto-classification. | |
| exception | No | Reason this followup should be allowed even under an active autonomy mandate (NF-DS-45569A27). Valid only for the three pre-approved cases: >1GB download, credential the operator must physically enter, or a presence-dependent session with María/Nora. |