People
Find an existing person by phone number or create one from available details.
Turn supported conversations from existing phones, WhatsApp accounts and connected numbers into Pipedrive people, notes, deals and follow-up activities so sales teams can track leads without manual copying.

Keep leads received on business phones visible.
Use the sender phone number to find or create a person.
Add notes, deals or activities where appropriate.
Capture the original enquiry and connect it with the records sales teams use to assign and progress opportunities.
Find an existing person by phone number or create one from available details.
Attach supported incoming message content to preserve conversation context.
Create or associate a deal where a message represents a genuine opportunity.
Create available follow-up activity for calls, quotes, meetings or reminders.
Complete international phone formatting improves matching. If the source has no name, the person may initially be identified by phone number.

A practical workflow captures the lead, preserves the original message and creates only the sales records that make sense.

Use the company domain shown when signed in—not a full deal URL—and protect the personal API token like a password.
Use the domain shown in the Pipedrive browser address, such as yourcompany.pipedrive.com.
Find the API token in your Pipedrive personal preferences or API settings.
Add the company domain and API token in AutoForward Text CRM Integrations.
Confirm sample records, then test a fresh real message and search by phone number.
The message must first reach AutoForward Text before it can be sent to Pipedrive.
The integration is designed to capture supported new incoming messages in Pipedrive. It does not automatically import old history or send a CRM-written reply back through the original channel.
Old conversations are not imported after connection.
Routine messages may only need a note; reserve deals for genuine opportunities.
A Pipedrive comment or note is not automatically sent back to SMS or WhatsApp.
If other CRMs are active, supported messages may be sent to each connected platform.
Grant only the scopes and account access required for CRM record creation.
Never publish tokens or include them in screenshots and unsecured support messages.
Verify matching and record creation without using sensitive customer data.
Use international phone formatting and inspect test records before launch.
Current behavior may evolve, so use the detailed setup guide when connecting your account.
Read the Pipedrive GuideYes. Supported new incoming SMS from connected AutoForward Text sources can be sent to Pipedrive and stored as people, notes, deals or activities.
Yes. Supported new incoming messages from a connected WhatsApp account can be matched to a CRM contact using the sender phone number and added as people, notes, deals or activities.
Yes. A supported Android phone can keep receiving SMS through its existing SIM while AutoForward Text sends eligible incoming messages to the connected CRM.
No. Sources can also include a connected Android phone, supported iPhone workflow, WhatsApp account, virtual number or another available channel.
The sender phone number is used where possible. Storing numbers in complete international format improves matching and reduces duplicates.
No. The integration processes supported new messages received after the CRM connection becomes active.
Not through the basic CRM logging workflow. A CRM-written response is not automatically sent through the original SMS or WhatsApp channel unless a separate supported workflow is configured.
The connection requires your Pipedrive company domain and personal API token. Protect these values like passwords and grant only the access needed by the integration.
Connect Pipedrive, verify phone matching and capture supported new conversations as useful sales records.