> For the complete documentation index, see [llms.txt](https://learn.mechanic.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.mechanic.dev/faq/whats-possible-with-timeline-comments.md). # What's possible with timeline comments? ## What's possible * Reading timeline [comments](https://shopify.dev/docs/admin-api/graphql/reference/events/commentevent), and [other events](https://shopify.dev/docs/admin-api/graphql/reference/events/basicevent), for orders, draft orders, customers, and inventory transfers. * Writing order and customer *notes*. This is *not the same* as the timeline comments. We mention it here because this frequently makes for an acceptable fallback approach. ## What's not possible * Using a timeline event as a Mechanic event. This means that Mechanic tasks can't run in direct response to a new comment (or other timeline event). * Reading the name of the staff person who left a comment, or the name of the app responsible for another event. * Creating, updating, prefilling, or deleting timeline comments. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://learn.mechanic.dev/faq/whats-possible-with-timeline-comments.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.