A caller says they have already spoken to your sales team. Your assistant can ask them to confirm their email and check for an existing Pipedrive contact without waiting for the call to finish. The HeyRik Pipedrive integration adds a direct, read-only lookup tool to the assistants you choose.
For example, an Indian sales team using Pipedrive could use the result to decide whether to collect new enquiry details or arrange a follow-up with its team. This is a workflow you configure, not an automatic identity check or a promise that a salesperson is available. This first version stays focused on exact-email contact lookup; it does not create contacts, read deals or change your pipeline.
One lookup, minimal contact context
The pipedrive_find_contact tool searches the caller-confirmed email. A single matching person returns a contact ID, name and that email. Stored phone numbers, notes, deals and custom fields are not passed back to the assistant. If more than one contact matches, the tool reports ambiguity instead of choosing one.
A match is not proof of identity. Keep your normal verification process and instruct the assistant not to disclose stored information to an unverified caller. For example, finding a sales contact must not authorize an account change.
Connect a test assistant
- 1Open Connected apps, select an assistant and choose Pipedrive.
- 2Enter your company subdomain, such as your-team, and the API token for a user with only the visibility you need. Use the subdomain from your Pipedrive URL; custom domains are not supported.
- 3Save the connection. HeyRik checks contact read access and encrypts the credentials. The API token itself inherits the Pipedrive user's permissions, even though this connector only reads.
- 4Enable contact lookup and tell the assistant when to use pipedrive_find_contact. Enabled tools apply to new calls.
- 5Test a known email, an unknown email and an unavailable result before enabling a production assistant. Saving credentials checks read access, not every possible search permission.
Keep failures honest
A provider outage, API limit or permission problem can prevent lookup. Requests have bounded waits and are not automatically retried by this connector. Your assistant should explain that it could not confirm the result and offer your configured fallback, such as a team follow-up. It must not invent a contact or treat an error as no match.
Disabling or disconnecting blocks subsequent lookup requests. An already-running request may still finish. Changing the company subdomain requires entering the token again, so a previously saved token is not silently sent to another company address.
Start with one caller workflow
Choose a low-risk sales enquiry workflow and a test contact. Verify the assistant asks for the email clearly, receives the expected result and handles duplicate contacts without guessing. Review who can access tool logs and whether your privacy notices cover sharing minimal contact context with the AI provider. There is no bulk import, record creation, post-call sync or India data-residency guarantee in this release. Once your test calls behave as expected, enable lookup only for the assistants that need it.
A little more before you begin.
Can this create a lead or update a deal?
No. This version only finds an existing person by exact email.
Does it need a call-end webhook?
No. The assistant requests the lookup during the conversation and waits for its result.
Does an email match verify the caller?
No. Keep your normal identity checks before sharing stored information or taking sensitive actions.
Start here
Set up Pipedrive contact lookup
Build a voice agent, upload your list or connect your leads, and run your first campaign on HeyRik — free to start, no credit card required.