sales-jamie
Facilitates AI-driven meeting note-taking and CRM integration for sales teams, enhancing productivity and workflow automation.
Install this skill
Security score
The sales-jamie skill was audited on Jun 3, 2026 and we found 17 security issues across 1 threat category. Review the findings below before installing.
Categories Tested
Security Issues
Webhook reference - potential data exfiltration
| 3 | description: "Jamie platform help — bot-free AI meeting note-taker, REST API with personal and workspace keys, webhook automations, CRM sync to HubSpot/Salesforce/Attio, MCP server for Claude/ChatGPT/ |
Webhook reference - potential data exfiltration
| 20 | - C) Webhook setup — automating workflows when meetings complete |
Webhook reference - potential data exfiltration
| 52 | **Read `references/platform-guide.md`** for the full platform reference — modules, pricing, API endpoints, webhook setup, integrations, data model. |
Webhook reference - potential data exfiltration
| 60 | - **API vs webhooks**: Use webhooks (`meeting.completed`) for real-time pipelines; use REST API for batch queries and search. Combine both for production: webhook for push + nightly reconcile poll. |
Webhook reference - potential data exfiltration
| 62 | - **Plan gating**: API/webhooks require Pro+. CRM sync (HubSpot/Salesforce/Attio) requires Pro+. Free and Plus are personal-use only. |
Webhook reference - potential data exfiltration
| 77 | - **No native Zapier integration.** Automation goes through Make.com or custom webhooks. |
Webhook reference - potential data exfiltration
| 79 | - **Webhook endpoint URL can't be updated.** Delete and recreate if the URL changes. Events are also immutable after creation. |
Webhook reference - potential data exfiltration
| 87 | - `/sales-integration` — General CRM/tool integration patterns (Zapier, Make, webhooks, iPaaS) |
Webhook reference - potential data exfiltration
| 92 | ### Example 1: Setting up Jamie webhooks with Make.com |
Webhook reference - potential data exfiltration
| 95 | 1. Confirms user is on Plus+ plan (webhooks require it) |
Webhook reference - potential data exfiltration
| 96 | 2. Walks through: Jamie Settings → Integrations → Webhooks → Create Webhook → paste Make.com webhook URL |
Webhook reference - potential data exfiltration
| 98 | 4. Shows Make.com scenario: webhook trigger → parse JSON → create Notion page with summary + action items |
Webhook reference - potential data exfiltration
| 107 | 4. Suggests hybrid: webhook for real-time + nightly batch to catch gaps |
Webhook reference - potential data exfiltration
| 131 | ### Webhook not firing after meeting ends |
Webhook reference - potential data exfiltration
| 132 | **Symptom**: Webhook endpoint never receives `meeting.completed` event |
Webhook reference - potential data exfiltration
| 133 | **Cause**: Webhook requires Plus+ plan, endpoint must be HTTPS, or webhook was created with wrong event |
Webhook reference - potential data exfiltration
| 134 | **Solution**: Verify plan is Plus or higher. Check webhook URL is HTTPS (HTTP is rejected). In Jamie Settings → Integrations → Webhooks, confirm the webhook shows `meeting.completed` as the selected e |