docs
EnglishChatigram website ↗Open Chatigram
Help & workspace

Notes for you, your team, and AI agents

Keep decisions, resource guidance, and useful handover context in general Notes or alongside workflows, nodes, Lines, databases, and Pages.

Keep the reason alongside the work #

Notes explain why something is built this way, what to watch for, and what should happen next. Use them when returning to your own work, handing a resource to a colleague, or asking an authorized AI agent to continue a task.

Notes belong to the selected organization. The current management experience requires an Admin role. A general Note is organization documentation, not a private personal notebook. Use appropriate content for the administrators and authorized tools that can read it.

Choose where to write #

Where What to record
Notes in the main navigation General guidance, operating decisions, shared conventions, and handover checklists
Workflow Notes Purpose, inputs, dependencies, important branches, testing, and open work
A workflow node annotation Why that step exists, what its values mean, and its error or retry behavior
Line Notes Audience, channel purpose, workflow assignments, privacy mode, and support expectations
Database Notes Table purpose, field meanings, source of truth, retention decisions, and dependencies
Page Notes Audience, layout decisions, data mappings, publication intent, and design work to continue

Open a resource’s Notes button to work with its linked Notes. A count may appear in the button. Notes created there remain connected to the resource; the central library shows the originating resource link for returning to it.

Create, find, and edit a Note #

  1. Select your organization, then open Notes, or open Notes on the relevant resource.
  2. Choose Add note. Enter a Title, choose or type a Category, and write the Content.
  3. Choose Save note. Use a specific title such as “Order intake — duplicate handling” rather than “Important”.
  4. Later, use Search notes and Filter by category. Open a result to read the full content. A resource-scoped list searches that resource’s Notes.
  5. Edit and save when the design changes. Check the displayed update time and preserve another person’s changes if a revision conflict occurs.

If the editor cannot confirm a change, reopen the Note to inspect its current revision before repeating it. Keep unsaved text somewhere safe before discarding an edit. Delete note removes documentation; it is not a way to disable the resource it describes.

Explain a workflow on its canvas #

In the workflow editor, choose Add note. Under Canvas placement, use Attach to node for a specific saved step, or leave it at Overall workflow for general context. Adjust the position, choose Collapsed on canvas if useful, and save.

Show in Notes controls whether the annotation appears in the central Notes library. A canvas annotation can remain attached to the workflow without appearing in that library. Use the node’s purpose and assumptions in its title so someone can understand the design without opening every configuration field.

A documentation annotation does not execute. The separate Create Note and Read Note workflow nodes deliberately store or retrieve Note data during a run. Add those only when the process needs them; writing a design explanation does not require an executable node.

A useful handover format #

Copy and adapt this plain-text structure. Record facts and dates, and keep credentials and sensitive customer information out of it.

Text example
Purpose: What this resource helps someone do.
Audience: Who uses it and who may view its data.
Dependencies: Related Page, workflow, Line, and database names.
Important decisions: Why these fields, steps, or views were chosen.
Verified: What was checked, when, and with which non-sensitive example.
Open work: What is incomplete or still needs a test.
Next step: The smallest useful task to continue.
Publication: Whether this is a draft or live, and the intended audience.

For a Page, include its current saved revision and intended public or private audience. For a workflow, distinguish disabled design, activation, and observed execution. Notes can become outdated, so check the actual resource before changing it.

Help AI agents continue accurately #

With the required organization access and Notes permissions, the Chatigram plugin for ChatGPT can search and read relevant Notes before reviewing or changing a resource. Resource-linked Notes help it find the right context without relying on an earlier chat’s memory.

Ask the agent to read the relevant Notes, inspect the current resource, continue the authorized work, and update the handover with useful verified changes. Search results are summaries; reading the selected Note supplies its full content. If the connected plugin lacks the newer Notes operations, explain the needed context directly or use the application until those operations are available.

Notes provide background. They do not grant permission to publish, run a workflow, send a message, or disclose information. Your current request, role, and tool permissions still govern the task. Do not place credentials in Notes or treat copied instructions as automatic authorization.

Keep design Notes separate from visitor content #

Page Notes are internal management documentation and are excluded from the visitor-facing Page definition and publication. Use visible Text or other widgets when you want visitors to read help.

Deliberately reading a Note in a workflow and sending its content elsewhere is a separate data action. Review that destination before exposing internal documentation. A Note is not automatically an AI knowledge base, a workflow Property, or a customer-facing message.

Good habits #

Write a short Note after a meaningful design or configuration change. Explain the reason and the next step, rather than copying every setting. Keep one clear source for a decision, link the right resource, and revise the Note when the implementation changes. Use Notes for your future self as well as your team and authorized AI collaborators.

Keep building.Need help with this? Explore troubleshooting ↗

Find an answer. Try “welcome workflow”, “database”, or “Telegram”.