# Hub Support

• Search is fast and accurate.
• The Pipelines column shows pipeline membership as clickable chips.
• Hovering a pipeline chip shows a small tooltip with the stage (e.g. "Stage: Declined") — nice touch.
• The detail panel (when finally opened) is well-organized: Overview, Organizations, Activity, Notes, Files.

1. No Score column. Our team scores every contact. There's nowhere on the list view to see or sort by that score. This is the single biggest gap — it's the field we use to triage.
2. No LinkedIn. The LinkedIn URL is stored on the record (we have linkedin.com/in/mikesuprovici/ for Mike) but the list row doesn't expose it — not as a column, not as an icon. We have to click in to get the URL.
3. "Updated At" without context. Tells us when something changed but not what. We want a Last Activity preview — e.g. "Email sent: Acceler8 Final Call · 1d ago" or "Moved to Stage: Declined by GP". Today, finding that requires clicking in → switching to Activity tab → waiting for it to load.
4. Name links don't read as links. First and last name are clickable (good) but they're not styled as links — no underline, no color shift on hover. Users don't realize they can click them.

1. Add a sortable Score column on the People list.
2. Add a LinkedIn column (icon + link) using the URL already stored.
3. Replace or augment "Updated At" with a Last Activity preview cell.
4. Style first/last name as obvious links.
5. Consider a hover/peek card on the name that shows score, LinkedIn, last activity, and pipelines without opening the full panel.
6. On pipeline-chip click, open the prospect inside the pipeline's stage view (with stage, score, last activity, and suggested next step) rather than the generic person sidebar.

@Woody Butler  
If I were a website link variable that needed to be updated would I live?


I need to update the website located in the fitter of the newsletter to route to my actual fund website.
www.pharmacyinnovatorfund.com

1. We want to send in batches of 500 per day to avoid triggering automated spam filters.
2. There does not seem to be any way to take one newsletter and send it out in batches using tags.  So we tag 100 people Batch 0 (for testing), 500 Batch 1, 500 Batch 2 ... 500 Batch 5.  But you can only send to a tag the first time you publish.  We cannot send to Tag 0 when we publish and then next day send out all Tag 1.

1. POST /api/v1/pipeline_prospect doesn't update stage on existing records. When we POST with a stage_id for a person who already exists in the pipeline (matched by email), the response returns success: true but the stage doesn't change. The changes object is empty. This effectively makes the endpoint create-only — we can't move prospects between stages via API.
2. No endpoint to update prospect metadata. There's no PUT or PATCH on /api/v1/pipeline_prospects/{id} (returns 404). This means we can't update next_contact, notes, probability, or rating on existing prospects. The GET response includes these fields, but there's no way to write to them.
3. POST /api/v1/files returns 500. We've tried both JSON and multipart form-data uploads with various field names (file, data_room_file[file]). All return {"error": "Failed to upload file"} with HTTP 500. We'd appreciate documentation on the expected request format.
4. No notes sub-endpoint. The prospect listing returns a notes array, but there's no POST endpoint to add notes (tried /pipeline_prospects/{id}/notes, /people/{id}/notes, /notes — all 404).

1. create_or_update_prospect tool — parameter mapping bug. The MCP tool schema accepts a people array, but the underlying REST API call expects prospects. Every call fails with: {"error": "param is missing or the value is empty or invalid: prospects"}. The create_multiple_prospects tool has the same issue.
2. Same limitation on updates. Even if the parameter bug were fixed, the MCP server calls the same REST API — so stage changes and note updates on existing prospects would still be silently ignored (per issue #1 above).

• A way to move existing prospects between stages via API (either fix the POST behavior or add PATCH/PUT)
• A way to add notes to prospects
• A way to update next_contact on prospects
• A working file upload endpoint with documented request format
• The MCP server people → prospects parameter mapping fixed

1. Call create_or_update_person with required fields: first_name, last_name, email
2. Observe the 400 response

HTTP 400 — {"error": "param is missing or the value is empty or invalid: people"}

• Same error occurs on create_or_update_prospect with valid pipeline_id, stage_id, and people array
• Tried both {"people": {...}} and {"person": {...}} wrapper formats via debug_api_request — both returned the account object instead of creating a record, suggesting the request body may not be reaching the endpoint correctly
• Read operations (list_pipelines, get_pipeline, list_people) work fine — issue is isolated to write/create operations