· 1 observation
Technical updates · 1
Package or technical metadata updated
View technical comparison →HoneyBook, Inc v1.2.1
Book clients, get paid
From the developer
Not specified in the available declarations: capabilities, limitations, pricing & account requirements.
Which of my leads have gone quiet?
Developer declarations; not independently tested. Listing last checked Nov 22, 2026. Package observed Nov 21, 2026.
From the marketplace listing
HoneyBook is where independent businesses and lean teams run their client work: inquiries, proposals, contracts, invoices, payments and the messages in between. Connect your account and work through a whole job in one conversation. Ask which leads are worth chasing and get a ranked answer from your own bookings. Have the proposal built from your saved template. Review it before it goes anywhere. Later, ask who still owes you money, and raise a payment request for whoever does. You approve what it can reach before anything runs, resource by resource, and nothing reaches a client until you send it. Each request runs in an isolated environment, and your credentials are never shared with the model. Built for photographers, event planners, venues, designers and consultants. Requires a HoneyBook account.
Language: English · Automatically detected from descriptions.
· 1 observation
Package or technical metadata updated
View technical comparison →· 2 observations
Package or technical metadata updated
View technical comparison →Finding similar plugins… Results will appear here automatically.
Browse plugins →---
name: honeybook-project-pipeline
description: Review and analyze a HoneyBook project pipeline. Use for pipeline overviews, projects or leads by stage, active or archived project lists, custom pipeline filters, follow-up suggestions, and projects that may need attention. Do not use for general project details unrelated to pipeline position.
---
# HoneyBook Project Pipeline
Use HoneyBook's connected MCP tools to give the member a complete, accurate view of their pipeline.
## Default response contract
For an unqualified pipeline overview, render the following structure in GitHub-flavored Markdown. Replace placeholders with live data and do not wrap the response in a code fence.
```markdown
## Project pipeline
**{active} active projects** · **{lead} leads** · **{booked} booked
### Recently active
| Project | Stage | Date |
| --- | --- | --- |
| [Project name](project-url) — active today | Stage name | Project date |
### Projects by stage
| Stage | Projects |
| --- | ---: |
| Stage name | Count |
Ask me to expand any stage or show all projects.
```
Use Markdown headings, bold text, descriptive links, paragraphs, lists, and tables only. The default Projects by stage section is always a two-column count table. Show project rows by stage only after the member asks to expand a stage or show all projects.
## Workflow
1. Call `get_guidance` before choosing operations whenever the request depends on HoneyBook concepts such as lead, booked, archived, pipeline stage, or project versus workspace.
2. Call `find_action` with `readOnly: true` for the exact current operation signatures. Do not guess adapter methods or fields.
3. Use `take_action_read_only` for pipeline inspection. Keep related reads, pagination, filtering, and aggregation in one call.
4. Match the requested scope:
- For an overview, use both `PipelineAdapter.getPipelineCounts` and `PipelineAdapter.listPipeline`. Counts provide the totals; entries provide recent activity, project dates, stage ages, and links.
- For counts only, prefer `PipelineAdapter.getPipelineCounts`.
- For project names or row-level details, use `PipelineAdapter.listPipeline` and retrieve every required page.
- Default to active pipeline entries. Include archived or untracked entries only when requested or when essential to answer the question.
5. Apply filters in the API whenever supported. Do not fetch the full pipeline and filter locally when `stage_ids`, `view_id`, `group`, `category`, `tag_ids`, `project_type_ids`, `lead_source_ids`, `archived`, `untracked`, or `has_suggestion` can express the scope.
6. Verify completeness from returned pagination. If a deliberate limit is necessary, state the limit and that the result is partial.
7. Present the answer using the member's stage names. Preserve server-returned stage order for pipeline overviews; never impose a universal HoneyBook stage order.
8. Link every pipeline project name to its HoneyBook activity workspace. Build the member-facing URL from the exact IDs returned by `listPipeline`: `https://app.honeybook.com/app/event/{project_id}/workspace/{id}/activity`. Here `project_id` is the project ID and the pipeline entry's `id` is the workspace ID. Copy both IDs verbatim and URL-encode each path segment.
## Interpretation rules
- Treat a HoneyBook Project as the client job and its Workspace as the object carrying pipeline state.
- Determine lead versus booked from workspace status, not a stage name. Custom stage names are not reliable lifecycle signals.
- Use the pipeline stage to explain where work sits in the member's customized process.
- Distinguish active, archived, and untracked records. Never silently mix them.
- Treat `last_activity_at` as activity recency, not time spent in the current stage.
- Call a project "inactive" only when the response provides an activity timestamp and the relevant comparison window is explicit.
- When `current_stage.moved_at` is returned, use it to calculate time in the current stage. Keep iPreview of the first 4,000 characters. Read full instructions →
Referenced files: 2 — file references are metadata, not package contents.
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
Package observed Nov 21, 2026.
plugin_asdk_app_6a7c329c161c8191a8df623446a34000
Download plugin data (JSON)Plugin details: freshly prepared. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.