haystack_ai_search
ChatGPTSearch Haystack for people, teams, posts, events, knowledge pages, glossary terms, files, and links. Each result includes a display_title (human-readable name) and a url with an absolute link back to the relevant page in Haystack. Results also include entity_type and, when present, entity_id from the typed hit (not from the url). Pass both to haystack_get_entity only when entity_id is set: that is knowledge_page, post, event, glossary_term, and link. person, team, and file hits omit entity_id because they are not fetchable; files remain available via the signed url, and people/teams have no long-form body. Do not parse Haystack URLs for ids. When presenting results to the user, always render each result as a clickable markdown link using its display_title as the link text and url as the target (for example [display_title](url)), so the user can open it directly in Haystack. When a summary is present (first page only), it is an AI-generated answer grounded in the top results; lead with it and then cite the supporting results as links. Follow-up pages omit summary; present only the returned links. Use next_page_token as the page_token on a follow-up call to page through more results.
haystack_create_draft_event
ChatGPTCreate a draft event in a Haystack group. This tool never publishes or notifies. First call haystack_list_groups_for_events and use its group_id as owner_group_id. Before calling this tool, show the proposed name, subtitle, body, schedule, timezone, location, and group to the user. Send the body as standard Markdown, not HTML; Haystack converts it to safe editor HTML before storing it, and raw HTML is rejected. Send start_time and end_time as RFC 3339 timestamps. For all-day events set is_all_day_event true and timezone UTC. start_time is UTC midnight of the first day and end_time is the exclusive UTC midnight after the last day, so a one-day event ends at midnight of the next day. To publish instead, use haystack_create_published_event only when the user explicitly asks to publish.
haystack_create_page
ChatGPTCreate a private knowledge page owned by the authenticated user. Private pages behave like personal drafts and are not published to a group. The response includes entity_type (always knowledge_page) and entity_id; pass both to haystack_get_entity when the user wants to reload the page. Do not parse Haystack URLs for ids, and do not rely on search to find a just-created page. Send body as standard Markdown, not HTML. Haystack converts it to safe editor HTML before storing it; raw HTML is rejected.
haystack_create_published_event
ChatGPTCreate a published event in a Haystack group. First call haystack_list_groups_for_events and use its group_id as owner_group_id. Before calling this tool, show the proposed name, subtitle, body, schedule, timezone, location, and group to the user. Use this tool only when the user explicitly asks to publish; publishing may notify the group through Haystack's configured email, mobile, Slack, or Microsoft Teams channels. When the user wants a draft, use haystack_create_draft_event instead. Send the body as standard Markdown, not HTML; Haystack converts it to safe editor HTML before storing it, and raw HTML is rejected. Send start_time and end_time as RFC 3339 timestamps. For all-day events set is_all_day_event true and timezone UTC. start_time is UTC midnight of the first day and end_time is the exclusive UTC midnight after the last day, so a one-day event ends at midnight of the next day.
haystack_draft_post
ChatGPTSave a draft post in a Haystack group. This saves a draft and does not notify the group. First call haystack_list_groups_for_posts and use its group_id as owner_group_id. Before calling this tool, show the proposed title, subtitle, body, and group to the user. Send the body as standard Markdown, not HTML; Haystack converts it to safe editor HTML before storing it, and raw HTML is rejected.
haystack_get_entity
ChatGPTLoad the full document for a Haystack entity identified by entity_type and entity_id from a haystack_ai_search hit (or haystack_create_page). Do not parse Haystack URLs for ids. Supported types: knowledge_page, post, event, glossary_term, and link. person, team, and file are not fetchable: files remain available via the signed url from search, and people/teams have no long-form body. body is TipTap HTML for pages/posts/events, definition text for glossary terms, and empty for links. For links, url and content_url are the off-site HTTP(S) target when a safe URL is stored, otherwise empty (links have no in-Haystack detail page). When presenting the entity, render display_title as a markdown link to url if url is present.
haystack_list_groups_for_events
ChatGPTList the Haystack groups where the authenticated user can create events. groups lists only groups the user belongs to, capped at 20, and is never the user's full reach unless additional_group_scope is none. When that field is open_groups or all_groups, Haystack has authorized the user to create events outside their own groups: report that they can also create events in unlisted groups, ask which group they want, and call this tool again with that name in query. Treat query as the way to settle whether any specific group is usable, since results are filtered by the user's publish permission server-side, so a group that comes back is usable and one that does not is not. Use the returned group_id as the owner_group_id for haystack_create_draft_event or haystack_create_published_event; do not use an id from another source.
haystack_list_groups_for_posts
ChatGPTList the Haystack groups where the authenticated user can create posts. groups lists only groups the user belongs to, capped at 20, and is never the user's full reach unless additional_group_scope is none. When that field is open_groups or all_groups, Haystack has authorized the user to post outside their own groups: report that they can also post to unlisted groups, ask which group they want, and call this tool again with that name in query. Treat query as the way to settle whether any specific group can receive a post, since results are filtered by the user's publish permission server-side, so a group that comes back can receive a post and one that does not cannot. Use the returned group_id as the owner_group_id for haystack_draft_post or haystack_publish_post; do not use an id from another source.
haystack_publish_post
ChatGPTPublish a post in a Haystack group. Call this tool only when the user explicitly asks to publish. Publishing may notify the group through configured Haystack channels, including email, mobile, Slack, and Microsoft Teams. A title is required. First call haystack_list_groups_for_posts and use its group_id as owner_group_id. Before calling this tool, show the proposed title, subtitle, body, and group to the user. Send the body as standard Markdown, not HTML; Haystack converts it to safe editor HTML before storing it, and raw HTML is rejected.
haystack_ai_search
Claudehaystack_create_draft_event
Claudehaystack_create_page
Claudehaystack_create_published_event
Claudehaystack_draft_post
Claudehaystack_get_entity
Claudehaystack_list_groups_for_events
Claudehaystack_list_groups_for_posts
Claudehaystack_publish_post
Claude