KeeperHub / KeeperHub/keeperhub
feat: REST endpoint or query param for workflow template search
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 24
- Forks
- 93
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 266
Description
Split from #1869 (credit: @subheeksh5599).
**Problem**
`GET /api/workflows/public` supports `featured`, `featuredProtocol`, and `tag` - no free-text query. No other REST route under `app/api` touches template search (`app/api/auth/template-intent` is an unrelated session-intent route). `docs/getting-started/agent.md` routes template discovery to MCP only.
**Impact**
A REST-only integration (no MCP client, no CLI) can't discover templates by keyword, only by tag/featured flag - pushing agents back to the dashboard for the most useful onboarding path.
**Open question**
Add a `q` param to `GET /api/workflows/public`, or a dedicated template endpoint if templates should be modeled separately from the public feed?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at GET /api/workflows/public and compare its existing featured, featuredProtocol, and tag handling with the template-discovery guidance in docs/getting-started/agent.md. Review app/api/auth/template-intent only to confirm it is unrelated. Done means REST-only integrations can discover templates by keyword through a documented endpoint or query parameter, with the chosen API shape resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, backend, search
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 48/100