What are the requirements for Pipedrive integration with MyOperator?
Scope: This article lists the requirements called out for enabling the Pipedrive ↔ MyOperator integration and the coordination needed to complete it.
🧭 Table of Contents
- Overview
- Requirements
- Prepare & share
- Troubleshooting & changes
- Notes & limitations
- FAQs
- Support & escalation
🧠 Overview
To integrate Pipedrive with MyOperator, you need a small set of items (from your Pipedrive and MyOperator accounts) and a short coordination with MyOperator tech support to turn it on. The PDF emphasizes: API token, MyOperator service number, matching user emails, eligible plan, and user sync when team members change.
📋 Requirements
Item | Why it’s required | Source (from PDF) |
Pipedrive API token | Identifies and authorizes your Pipedrive account for the connector | “API token” requirement |
MyOperator service number | The MyOperator number used for call events in the integration | “service number” requirement |
Matching user emails (Pipedrive ↔ MyOperator) | Ensures calls/activities map to the correct users | “matching emails” requirement |
Eligible plan (e.g., Pro plan) | Plan prerequisite mentioned for access to the integration | “Pro plan” mention |
Coordinate with MyOperator tech support | Required step to complete enablement | “tech support coordination” |
User sync when users are added/changed | Keeps user mappings current after staffing updates | “user sync requests” |
⚙️ Prepare & share
- Collect your Pipedrive API token.
- Note your MyOperator service number.
- Verify user emails match in both systems (the same addresses in Pipedrive and MyOperator).
- Confirm plan eligibility (the PDF cites a Pro plan requirement).
- Share with MyOperator tech support: your Pipedrive API token and MyOperator service number so they can complete the setup.
🧯 Troubleshooting & changes
- New or changed users aren’t reflected → The PDF says to request a user sync when users are added or changed, so that email-based mapping stays accurate.
- Records not mapping to the right user → Re-check that the email address for that user is identical in Pipedrive and MyOperator.
- Setup stalled → Confirm you’ve sent tech support the API token and service number and that your plan requirement is met.
⚠️ Notes & limitations
- The integration relies on email matching between platforms.
- The PDF calls out a plan requirement (e.g., Pro plan).
- MyOperator tech support completes enablement—this isn’t a self-serve switch.
- After staffing changes, request a user sync per the PDF guidance.
❓ FAQs
Q1. Do I need to share my Pipedrive API token?
A. Yes—the PDF lists the API token as a required item for the integration.
Q2. Which MyOperator number should I provide?
A. Share the MyOperator service number referenced in the PDF.
Q3. Do user emails have to match in both systems?
A. Yes—the PDF specifies matching emails across Pipedrive and MyOperator.
Q4. Is there a plan prerequisite?
A. The PDF mentions a Pro plan requirement.
Q5. What if we add or change users later?
A. The PDF says to request a user sync so mappings stay accurate.
🆘 Support & escalation
To complete setup or request user sync, coordinate with MyOperator tech support (as stated in the PDF). Include:
- Pipedrive API token
- MyOperator service number
- List of user emails that should map (and any recent changes)
- A brief note of what you expect vs what you’re seeing
🏷️ Keywords
Pipedrive integration requirements, Pipedrive API token, MyOperator service number, matching user emails, Pro plan requirement, tech support coordination, user sync, MyOperator–Pipedrive setup
Related Articles
What are the requirements for Pipedrive integration?
Requirement: API (https://support.myoperator.com/portal/en/kb/articles/what-information-do-i-need-to-provide-to-sync-myoperator%E2%80%99s-data-into-pipedrive) token from Pipedrive MyOperator number Email ID of users on Pipedrive should be same as on ...What are the requirements for Pipedrive integration?
Requirement: API (https://support.myoperator.com/portal/en/kb/articles/what-information-do-i-need-to-provide-to-sync-myoperator%E2%80%99s-data-into-pipedrive) token from Pipedrive MyOperator number Email ID of users on Pipedrive should be same as on ...What is the logic behind the Pipedrive integration with MyOperator?
? Table of Contents Overview Logic at a glance Decision flow (incoming vs outgoing) User mapping requirements Verify the behavior (steps) Edge notes & clarifications FAQs Related articles ? Overview The integration automates deal and activity ...🧩 What are the requirements for Zendesk integration with MyOperator?
Short answer: You’ll need your Zendesk subdomain, a Zendesk API token, your MyOperator service number, and matching agent email IDs across both systems. A MyOperator Pro plan is required, and you must be able to share these details with Support and ...What steps are involved in configuring the integration of Pipedrive CRM with MyOperator?
Short answer: Provide your Pipedrive API token and MyOperator service number to Support for backend enablement, then validate call logging (deals/activities) and sync users by email when team changes occur. • Applies to: Pipedrive (latest), ...