schedule_update
Change explicit fields on a reminder or recurring alert the requester set up, including how often it repeats and when it next arrives. Use schedule_list first when neither the schedule ID nor its current description is known. At least one field to change is required. `workspace_write` · v1
Authorization
memberToken The tools internkim uses inside a company, callable from outside it. A token belongs to a person, and every call runs as that person, so a token can never do more than its owner can.
The first token is made signed in, from the settings screen. After that a token makes its own
successors: POST /token for a new one, DELETE /token for the old one, so a script rotates
without a browser. A token can neither mint a rung above its own nor revoke itself.
Send Authorization: Bearer <token> on every request.
In: header
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
text/plain
text/plain
text/plain
text/plain
text/plain
text/plain
text/plain
curl -X POST "https://example.com/tools/schedule_update/invoke" \ -H "Content-Type: application/json" \ -d '{ "input": { "scheduleHint": "…" } }'{ "toolName": "schedule_update", "outcome": "succeeded", "selectedBackend": "device", "effects": [ { "objectType": "schedule", "effect": "created", "id": "7a93de11-…" } ], "result": { "…": "the tool's own document" }}schedule_list POST
List scheduled tasks created by the current requester. Filter by active, failed, or expired status and cap the result with limit. Use it to answer what reminders or recurring tasks are scheduled. `read` · v1
task_add POST
Create a new workspace task with typed task fields. Never ask the user to classify it: send the business when you know it, and the record decides whatever business, type and size is left out from the company definitions. Use this to add a todo or assignment for the requester or another team member. Use task_update for existing work. `workspace_write` · v7