Pipedrive Shopify integration: contacts and orders

Connect Shopify and Pipedrive through a verified method, with defined contact and deal mappings and checks for duplicates, permissions and failed syncs.

A Pipedrive Shopify integration works indirectly through an automation service such as Zapier. Connect the store event to a contact lookup, then create or update the intended Pipedrive record. Keep Shopify responsible for purchases and decide separately whether a purchase needs a sales deal.

Choose the supported method

Use Zapier for a defined Shopify-to-Pipedrive workflow with explicit triggers and field mappings. Zapier’s Shopify and Pipedrive connector is third-party automation. Connecting both accounts does not configure a two-way sync of every record.

The required products are an active Shopify store, an active Pipedrive account and a paid Zapier plan. Shopify is a premium Zapier app. Shopify connection requirements also require app and channel access for the connecting user.

Pipedrive connection requirements require API access for the connecting user. Zapier supports Pipedrive accounts on any plan, including a trial. Budget for the store and CRM subscriptions alongside Zapier’s paid plan and task allowance. The number of actions per order affects that allowance.

Start with Shopify’s New Order trigger, documented as instant. Add a filter for the order status your team accepts. A paid-at-creation order can pass a paid-status filter immediately. An order paid later needs a separate Updated Order route through the same matching rules. Instant describes event delivery, not a guaranteed end-to-end completion time.

Choose record ownership before mapping fields:

  • Shopify owns the store customer identifier and order facts, including payment and fulfilment status.
  • Pipedrive owns the contact’s sales owner and the deal’s sales stage.
  • The automation carries store facts into designated CRM fields. It changes only the fields assigned to that event.

A customer update can refresh mapped contact details. A refund can refresh copied order context through a separately configured workflow. Neither event needs permission to change a salesperson’s notes or reopen a closed opportunity.

Verify the retail record handover

Match the customer before creating a person, and match the order before creating a deal. Zapier documents Find Persons and Find Deals, plus create and update actions. Build those searches into the workflow instead of connecting New Order directly to Create Deal.

Consider this fictional mapping for a retailer that records completed purchases as won deals. Customer C104 places order O920 for a $240 lamp. Pipedrive person P88 already holds that customer’s store identifier in a dedicated field.

Example destination fields

Shopify inputPipedrive destinationMapping rule
Customer ID C104Store customer ID on person P88Search this identifier first
Customer name and emailPerson name and emailUpdate only approved contact fields
Order ID O920Store order ID on the dealSearch before creating a deal
Order total $240 and currencyDeal value and currencyCarry the order’s currency with its amount
Paid status and lamp purchaseOrder-context fields or linked noteKeep the purchase facts separate from sales notes
Completed purchaseWon deal in the chosen pipelineApply this retailer’s explicit reporting rule

Create the dedicated fields before mapping them. Use the field’s actual identifier in the connector and test the returned values. If a search cannot uniquely resolve a stored identifier, stop that record for review.

On the first run, find P88, then look for O920. Create the deal only when O920 has no match and attach P88 using the returned person ID. Record the created deal ID for later updates.

Repeat O920 through the same workflow. The expected result is the same person and deal, with approved fields updated once. A second purchase by C104 must reuse P88 while creating a different order record.

When the customer changes their email, use the stored customer ID to find P88. An email search can help match a first purchase to an existing contact. Shared addresses or several matches require manual resolution before writing.

A paid purchase is completed business. An open deal is work a salesperson is still trying to win. If your team only tracks future opportunities, retain the purchase as contact context and create a deal when a separate sales qualification rule passes. This prevents every repeat purchase from inflating the open pipeline.

Check permissions and failed syncs

Authorise the connection with accounts that can read the required Shopify records and write the intended Pipedrive fields. Inspect the permission request before approval. Mapping fewer fields limits what the workflow sends, but does not reduce the app permissions already granted.

Shopify’s app management guidance shows where to inspect permission and privacy details under Settings > Apps. Include Zapier in your assessment of who receives customer records. Keep payment credentials and unrelated customer notes out of the mapping. App authorisation does not establish a customer’s marketing preference, so preserve that preference separately from the purchase event.

Use the order ID to trace failures from the store event through each action to the destination deal. Check the actual Pipedrive record after a run reports success.

  • If a required name or order identifier is missing, hold that record and correct the source or mapping before retrying.
  • If two contacts match, resolve the identity and retain the chosen person ID before allowing the order to continue.
  • If a run is delayed, inspect whether the trigger arrived and which action stopped. Check account access and task availability before submitting another event.
  • If a create action times out, search Pipedrive for the order ID before replaying it. The destination record can exist even though Zapier did not receive its response.

Zapier’s duplicate-data troubleshooting guide identifies overlapping workflows and timeouts as causes of duplicates. Keep the new-order and updated-order routes behind the same order lookup. Where events can overlap, queue writes for the same order so both runs cannot create it at once.

Finish a recovery check by replaying one failed example and confirming its saved person and deal IDs. Then send a later customer update and confirm that the order history remains intact. Enable the workflow for further orders only when repeat delivery preserves the intended records.

Give your store its own shopping agent

Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.

See it in actionFree trial · Simple setup