xtiles_create_notification
Create a notification for the owner of the account you are working in, about work they did not watch happen. It appears in their own xTiles notification feed and, with the xTiles mobile app, as a push on their phone: there is no recipient parameter and nothing is sent to anyone else. WHEN: (1) a scheduled or recurring run, or a prepared workflow, whose instructions say to notify the person — no such line in its instructions, no notification; (2) the person explicitly asks to be told, reminded or notified; (3) you set up a schedule and the person agreed to be notified — one notification at the end of the setup. Never after an ordinary one-off request in a live conversation, and do not offer one there: the person is reading your reply and already has the links. When you set up a schedule, offer this notification together with it, and only with consent make "when everything is ready, send a notification titled ' is ready' for each place changed" the last step of the scheduled instructions. HOW: the very last calls of the turn, after all the work including layout and styling — nothing may change after them. Always with a title. Once per place you changed (a project page, a planner day), one notification covering everything done there — never once per task or tile. Two places changed means two calls, each with its own url and its own summary, even when the person asked for "a notification" in the singular. If it fails, the work still stands: report the work with its links, mention the failed notification in one line, and retry at most twice.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | A ready-to-use absolute https URL on xtiles.app that opens the result (you build this URL yourself — the backend does not resolve a destination from ids). If you added tiles anywhere — a project page or a planner day, new or existing — use the `resource_url` the creating tool returned for the FIRST added tile, so the app scrolls to it. Link a page (`parent_resource_url` / `link`) only when you created that page or project itself. Only tasks, no tiles: link the planner day they are due on — https://xtiles.app/<view_id>, with the view_id from reading that day. Never invent a path; never the home screen or the project list. | |
| text | Yes | 1–2 facts from the result not already in the headline (count, time, person, date, topic), then a short call to action. With no concrete detail, write a fixed phrase and the call to action; never invent. Call to action always, facts or not. Max 100 chars. Language of the person or their content — the call to action in that language too. No assistant name, marketing or emoji pile. Examples show the shape only — write yours in that language. Examples: Daily Brief: "3 tasks due, sync at 11:00. Tap to see details", Budget approved: "40k for Q4, sign-off by Friday. Tap to open", no facts: "Your plan for today is ready. Tap to open". | |
| title | No | Required on every call, though the schema allows omitting it. What happened, in a few words. Max 60 chars, one line, no assistant name. In the person's language: translate "is ready", keep only the routine's name as given. Scheduled run or workflow: "<its name> is ready", identical every run (verbatim if its instructions give one). Examples show the shape only — write yours in that language. Examples: "Daily Brief is ready", "Weekly Review is ready", "Budget approved". | |
| agent_source | No | A raw label identifying the calling client, e.g. "Claude". Unrecognized values are accepted. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| sent | Yes |