⚡ Quick answer

• Configuration – Email MyOperator Support your Pipedrive API token, MyOperator service number, and a CSV of user e-mails. Support flips a backend switch (< 1 business day) that starts logging every call as a Deal update or Call Activity. Validate with one inbound and one outbound test call.

• Logging logic – For every call, MyOperator checks:

1. Call direction
2. Whether the contact already has an open deal in Pipedrive

When should I use this guide?

Use it if you:

• Manage MyOperator on the Pro / Professional plan (or higher), and

• Want every inbound and outbound call to appear inside Pipedrive—while also knowing exactly where and how each call is logged for reports, automations, or coaching.

1. What the integration does

Alt-text: Sequence diagram showing MyOperator sending call data to Pipedrive via backend.

2. Requirements checklist

Watch the video walkthrough

Alt text: video demo

3. Gather & send your details

1. Copy your API token from Pipedrive.

Alt text: Collect your Pipedrive API token

1. Record the service number
2. MyOperator Dashboard → Numbers → choose the number you answer inbound business calls on.

1. Export user list
2. Pipedrive → Settings → Manage Users → Export as CSV.
3. MyOperator → Settings → Users → Export.
4. Confirm the email column matches 1-for-1.

1. Confirm plan eligibility
2. Pipedrive → Billing → make sure “Professional” (or higher) is shown.

1. Requesting enablement

Email support@myoperator.com.

• You will receive a confirmation once the backend toggle and user mapping are complete.

4. Support-side setup

MyOperator will:

• Store your API token securely.
• Enable webhook delivery.
• Map users by email.
• Toggle “Deal create” logic per your JSON.

5. Call-logging logic & decision matrix

How the integration works

The backend listens to every call event emitted by MyOperator and then:

1. Matches the calling/called number to a Pipedrive Person.
2. Finds the most recent open deal for that Person.
3. Applies the decision matrix below to log either an Activity or a new Deal + Activity.
4. Assigns the Activity owner based on the e-mail match between the MyOperator agent and the Pipedrive user.

Decision flow:

Alt-text: Flowchart showing branch decisions for incoming vs outgoing calls and open-deal checks

6. Verification checklists

6.1 Post-setup validation

6.2 Logic verification

1. Place an incoming call from a number with an open deal → Activity appears on that deal.
2. Place an incoming call from a new number → New deal + Activity.
3. Make an outgoing call to a contact with an open deal → Activity on that deal.
4. Make an outgoing call to a contact with no open deal → Default = Activity only • If flag enabled = New deal + Activity.
5. Confirm the Activity owner matches the agent who handled the call.

7. Ongoing maintenance

• User changes → Email Support for a “user sync”.
• Token rotation → Send new token; Support updates backend.
• Plan downgrade → Integration pauses until the Pro plan is restored.

8. When does this NOT work?

• Plan downgraded below Professional – API scopes are revoked.
• E-mails don’t match → Activities log to “Unknown Owner”.
• Token revoked/expired → No calls appear until a new token is supplied.
• Calls bypass MyOperator (e.g., direct mobile call) → Nothing to log.
• Users added later – new hires won’t see activities until you request a user sync.
• Multiple open deals – The most recently updated open deal is chosen; close extras to avoid confusion.
• Unmatched phone numbers – Activity logged only under the Organisation; no deal is touched.
• API rate limits (429) – Events retry for up to 5 min; if all retries fail, they queue for the nightly re-sync.

9. Troubleshooting guide

Still stuck? Email support@myoperator.com with timestamps & screenshots.

Keywords: Pipedrive–MyOperator logic, auto-deal creation, inbound call activity, outbound call new deal, email mapping, activity owner, sales call automation

Updated on: 12/01/2026