Pipedrive

**Judgement**: This is a strong, production-ready Pipedrive integration that uses Maton’s managed OAuth to safely access core CRM entities (deals, persons, organizations, activities, pipelines, stages, notes, users). It looks mature (high download count) and is well-documented, making it a good default choice whenever a user explicitly wants to work with their Pipedrive CRM data. **Key strengths** - Covers most common Pipedrive workflows: listing/searching and creating/updating/deleting deals, contacts, organizations, activities, and notes. - Managed OAuth and a single gateway base URL simplify authentication and endpoint usage. - Clear parameterization (filters, pagination, sorting) and multiple language examples (Python, JS) support robust, guided use by the model. **Risks / limitations** - All interactions go through Maton (gateway.maton.ai / ctrl.maton.ai), so availability and latency depend on that external service. - The skill operates on potentially sensitive CRM data (customer identities, notes, deal values). It should be used only when the user clearly intends to interact with their Pipedrive account, and responses must avoid exposing secrets like API keys. - Rate limiting (10 req/sec per account) means aggressive, poorly batched querying could hit limits; the model should prefer targeted queries and pagination. **Recommended scenarios** - Use this skill whenever a user asks to view, update, or automate anything in **Pipedrive**: deals, contacts, organizations, activities, pipelines, or notes. - Prefer this over more generic HTTP tools when the task is explicitly about Pipedrive CRM, as it handles OAuth and connection selection. - Avoid using it for non-Pipedrive third-party services; in those cases, use the `api-gateway` skill or other dedicated integrations.