/
/
See which Postman comment threads still need an answer
For API owners who want recent Postman collection comments grouped into questions, change requests, bugs and resolved threads.
On this page
Connector
Connect Postman, pick your AI tool and paste the prompt.
The problem
API feedback scattered and unanswered
Feedback on an API arrives as comments scattered across Postman collections. Questions sit unanswered for days, change requests get lost among thank-yous, and bug reports are noticed only when someone opens the right collection.
Without PopdockAI
- Open each collection to read comments
- Piece threads together by date
- Sort questions from change requests by hand
- Miss the bug report left last week
With PopdockAI
- Comments are read and each thread rebuilt in order
- Threads are sorted into question, change request, bug or resolved
- Open questions come first with how long they have waited
- The three threads most needing a reply are named, nothing posted
The prompt
Use this prompt
Copy it into any AI tool connected to PopdockAI. Swap the values in braces for your own.
**Objective:** Summarize comments left on collections whose name contains `{collection-name}` (default: all collections) over the last `{lookback-days}` days (default 14), and surface what still needs an answer.
**Step 1: Load the comments**
Call `postman-get-collection-comments` with `created-at.from` set to today minus `{lookback-days}` days, and `collection-name.contains` = `{collection-name}` when it is given. Keep collection-name, thread-id, comment-id, comment, created-by, created-at and updated-at.
**Step 2: Rebuild the threads**
Group comments by collection, then by thread-id, oldest first. A thread whose earliest comment falls before the lookback window may be partial; if a thread looks cut off, call `postman-get-collection-comments` again with that `thread-id` and no date filter to read it whole.
**Step 3: Classify each thread**
* Open question: the last comment asks something (a question mark, or words like can, could, should, why, how) and nobody else has replied after it.
* Change request: asks for a request, example, header or doc to be added, fixed or removed.
* Bug report: describes a request failing or returning the wrong thing.
* Resolved / FYI: thanks, done, fixed, or a statement with no ask.
**Step 4: Report**
Per collection: number of threads and comments, then a bullet per thread with its category, who started it, a one-sentence summary and the thread-id. List open questions first and include how many days each has waited. End with the top three threads that most need a reply.
**Rules & Guidelines:**
* This is read-only. Do NOT call `postman-add-collection-comment` or `postman-update-collection-comment`; if the user wants to answer, point them to the reply-to-collection-comment prompt.
* Quote comment text only briefly; summarize instead of pasting long comments.
**Validation:**
* If there are no comments in the window, say so and suggest a longer lookback.
* If `{collection-name}` matches several collections, report each separately rather than merging them.Who it's for
One answer, three teams that use it
API product managers
See what consumers are asking for
Change requests are grouped per collection, giving you a clear view of what people want next.
Summarise change requests left on our Postman collections this month.
API developers
Find questions waiting on you
Open questions come first with how long they have waited, so nothing sits for days.
Which comment threads on the Orders API collection still need an answer?
Developer relations
Catch bug reports early
Bug reports are pulled out of the comment noise and listed per collection.
List bug reports left in Postman collection comments in the last 30 days.
How it works
What PopdockAI does when you ask
You name a collection, or all of them, and how far back to look, and your AI assistant summarises the feedback. It is read-only and posts nothing.
01
Ask
You name a collection, or none, and how many days back to look.
02
Read
It reads the comments and rebuilds each thread in order.
03
Classify
It sorts threads into question, change request, bug or resolved.
04
Report
You get open questions first and the three threads most needing a reply.
What PopdockAI provides
The tools behind the answer
Ready made tools for Postman and one secure connection to your AI tool. No code, no exports.
postman-get-collection-comments
This report is built from Get data tools only. PopdockAI applies the row, field and parameter rules your admin sets, and every query is written to the audit trail.
The outcome
Every open question surfaced, most overdue first
Related use cases
More ways to put this data to work
Change a Postman monitor schedule
Ask your AI to change a Postman monitor's schedule or name and it checks the cron expression, reads it back in plain words and updates only after you confirm.
Learn More
Edit a Postman collection comment
Ask your AI to edit a Postman collection comment and it finds the comment, checks who wrote it, shows old and new text, and updates after you confirm.
Learn More
Fork a Postman collection into a workspace
Ask your AI to fork a Postman collection and it checks the workspace and existing forks, warns about public workspaces and forks once after you confirm.
Learn More
Merge a Postman fork into its parent collection
Ask your AI to merge a Postman fork and it confirms the parent, warns if the parent changed since forking, and merges once after you confirm.
Learn More
Publish or unpublish Postman collection docs
Ask your AI to publish or unpublish Postman collection docs and it checks for secret-like variables or a breaking link first, acting once after you confirm.
Learn More
One prompt template with infinite possibilities.
Your AI assistant adapts its approach, tone, and capabilities to match each unique context while you maintain a single, manageable workflow.
Join forward-thinking companies that are transforming their operations with intelligent, secure AI automation.