get_featurebase_post
Retrieve a specific feedback post by slug, optionally including its full comment thread.
Instructions
Get a single post by slug, optionally with full comment thread.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | The post slug (the URL path segment after /posts/). Example: 'more-byok-options' | |
| teamUserIds | No | Optional override for the team-user-id set. When provided as a NON-EMPTY array, comments (and engagement fields on the post) are re-classified using these IDs as the team — useful for drilling into a single thread after calling find_featurebase_user. A non-empty override REPLACES the FEATUREBASE_TEAM_USER_IDS env var for this call only. An EMPTY array ([]) is treated as ABSENT — the env var is used if configured. With no env var configured AND no teamUserIds passed, comment authors will show role='unknown' and engagement fields will be omitted. | |
| include_comments | No | If true, fetch and inline the full comment thread as a `comments` array on the response (nested with `replies`). Each comment carries author (name, userId, role='admin'|'customer'|'unknown'), bodyHtml, bodyText, createdAt, updatedAt, upvotes, parentId, and replies[]. On fetch failure the post is still returned with `commentsError` set. Default: false. |