Schedule a dormant task for later on your own ticket
Plan work for later on the ticket you are currently working: creates a dormant task that wakes on the given date, instead of writing “I will check back on Monday” in a comment and forgetting. System agent transport only — refused for a human MCP token or a REST API key. You may only schedule on the ticket you are the agent of, onboarding tickets included. The task stays hidden for its whole life, asleep or awake: it never shows in the ticket tasks, its task lists or its status, and nothing has to close it. Until it wakes, getTicket lists it to you in sleepingReminders: check there before scheduling, and cancel one with updateTaskStatus (CANCELLED) to move or drop it. When it wakes, your run on the ticket receives its title and description — there is no separate prompt field, write what to do, not just a title. To create a task that should run now instead of later, use createTask.
Authorizations
Use your Primo API key in the Authorization header as Bearer <API_KEY>.
Body
Id of the parent ticket: the 24-character id returned by getTickets or getTicket, not the reference displayed in the product (e.g. IT-1741). Must be the ticket you are currently the agent of.
^[a-f\d]{24}$1What to do when this task wakes up. This is the only context you will have then — there is no separate prompt field, so write it as full instructions, not a one-line reminder.
1^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d(?::[0-5]\d(?:\.\d+)?)?(?:Z))$Response
PENDING, IN_PROGRESS, COMPLETED, CANCELLED, SCHEDULED, LOADING, SLEEPING LOW, MEDIUM, HIGH ^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d(?::[0-5]\d(?:\.\d+)?)?(?:Z))$Wake-up date of a SCHEDULED (dormant) task; null on any other status
^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d(?::[0-5]\d(?:\.\d+)?)?(?:Z))$Pick-up date of a SLEEPING task, which nobody sees until then; null on any other status
^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d(?::[0-5]\d(?:\.\d+)?)?(?:Z))$Whether a human (not only the system) may complete this task
Whether only an admin may assign this task or change its status
- Option 1
- Option 2
- Option 3
Ids of the tags attached to this task
Id of the AI agent handling it; null when no agent is on it
Type of a typed task, which Primo runs through its intent (EMPLOYEE_CREATION, EMAIL_ACCOUNT, EMAIL_ACCOUNT_SELECTION, SAAS_SELECTION, SAAS_PROVISIONING, EQUIPMENT_ORDER, OFFBOARDING_CONFIRMATION, DEVICE_HANDLING); null for a plain task
Id of a typed task's intent, to pass to its update and execute tools; null for a plain task