Noteithub

Write a previously prepared draft into the user's connected Notion workspace. This CREATES a real page in the user's Notion account — call it only after the user has reviewed the preview and explicitly confirmed. It consumes no Noteithub credits. Pass the `writePlanId` from the prepare preview. You MAY pass an `editedBody` (the user's edited page body) and `relationChoices` (reviewed page ids for relations, or null to leave blank). Omitted relation choices use the model-picked page from prepare when one was validated. You can NOT add or change any fields/properties — those are taken from the reviewed plan on the server. The server re-reads the live Notion schema and re-validates the plan before writing; a stale or expired plan returns a 'prepare again' result instead of writing. Safe to retry: a plan can only be written once, so a repeat call on an already-used plan returns the re-run state, not a duplicate page.

confirm_integration_export

Turn this conversation into a structured TODO plan saved in the user's Noteithub account. Each call consumes Noteithub credits. Use this tool when the user: - asks you to create a plan, roadmap, or action steps - says things like 'make a todo list', 'break this down', 'show me the steps', 'what should I do next?' - is clearly working toward a goal and wants concrete tasks. The tool will: - summarize the conversation - infer a short goal name (1–3 words) - extract 4–9 actionable tasks with descriptions, priorities, and optional due dates. IMPORTANT - Conversation Key: - If Noteithub has previously returned a 'conversationKey' in a response, you MUST include that SAME conversationKey in ALL future calls to this tool within the same conversation. - This allows Noteithub to track that multiple TODO calls belong to the same chat session. - DO NOT include a conversationKey if you haven't received one yet - Noteithub will generate one for you.

noteithub_create_todo_list

Prepare (preview only) filing this conversation into the user's connected Notion workspace. Use this tool when the user says things like: - 'save this to Notion', 'file this in Notion', 'add this to my Notion database' - 'export this synthesis to Notion'. This tool does NOT write to Notion. It builds a faithful synthesis, generates a write-plan against the live database schema, resolves relations, and returns a preview for the user to verify before saving in a later step. The synthesis and the write-plan are stored as a draft in the user's Noteithub account so the confirm step can use it, and each call consumes Noteithub credits. Pass as much structured context as you have: a summary plus keyPoints, decisions, openQuestions, action items, entities, topics, and dates.

prepare_integration_export

Save changes to TODO statuses from the widget. This tool is called from the widget when the user clicks 'Save changes'. It updates todo statuses (TO_DO, IN_PROGRESS, DONE, CANCELLED) in the database.

noteithub_update_todos

Save this conversation's outcomes as a journal entry in the user's Noteithub account, where it can be revisited later. Each call consumes Noteithub credits. Use this tool when the user says things like: - 'save this', 'bookmark this', 'remember this', 'keep this' - 'this is important', 'log this', 'journal this' - 'store this decision', 'save these notes' THE MOST IMPORTANT RULE: capture what was PRODUCED and CONCLUDED, not what was discussed. - If the AI gave an answer, write that answer down. - If a decision was made, write what was decided and why. - If a problem was solved, write the solution. Do NOT write 'we discussed X' — write 'the answer to X was Y'. FILLING IN THE FIELDS: - compressed_context (REQUIRED, 2,000–4,000 chars): Cover results first — the actual answers, code, solutions, and recommendations produced. Then decisions (what was chosen and why, what was rejected). Then technical specifics, action items, open questions. State the actual answers, not just the topics — but do not copy messages word-for-word. - short_summary: outcomes, not topics — 'The solution was X. We decided Y because Z. Next step: W.', never 'we discussed X'. Length, coverage, and format rules are in the field's own description. - title: Specific and searchable (5–12 words). 'Fixed N+1 query in orders endpoint using eager loading' — not 'performance discussion'. IMPORTANT - Conversation Key: - If Noteithub has previously returned a `conversationKey`, ALWAYS include the same conversationKey in future calls within the same ChatGPT conversation when saving/updating the same saved chat. - With the same conversationKey, repeat calls UPDATE the existing entry (safe to retry); without it, each call creates a new entry. - If you haven't received one, omit it; Noteithub will generate and return it.

noteithub_journalize_conversation

Show the user's existing TODO list or plan for a specific goal, read from their Noteithub account. Each call that returns a goal consumes Noteithub credits to match the query to that goal; it never changes goals or tasks. Use this tool when the user: - asks to see their todo list, plan, or tasks - says things like 'show my todos', 'what's my plan for X', 'show tasks for my project' - wants to view progress on a goal The tool will: - match the query to the user's closest goal - fetch up to 10 tasks for that goal; when there are more, the response says how many exist and that the rest are on the Noteithub dashboard - show task status (completed, in progress, etc.) It can return a NEAR MATCH: when the user has no goal for what they asked about, it shows the closest goal instead and says so in its response text ("No goal named 'X'. The closest is 'Y'."). Relay that wording to the user — never present a near match as the goal they named. When the user has no goals, nothing matches, or the match fails, it returns no goal and charges nothing.

noteithub_get_todo_list