Connect Pipedrive

Pipedrive is one of the three CRMs you connect yourself. It is the leanest of the three in what it exposes, which makes the mapping into Spiich simple to hold in your head.

Connect Pipedrive

1. 1

   Open the CRM section

   Go to Settings > Integrations and scroll to CRM platform. During signup this screen is step 3 of 4, Connect your CRM.

2. 2

   Click Connect Pipedrive

   A button reading Unavailable means another CRM is already connected to this workspace.

3. 3

   Approve the Spiich app

   Pipedrive's authorization screen lists the permissions the Spiich Marketplace app holds. Sign in to the company account you want linked and approve.

4. 4

   Let the import run

   Spiich registers Pipedrive webhooks and starts the first import. Chat shows Setting Up Your Workspace with a progress bar until it finishes.

What syncs, and what it becomes

The one mapping worth remembering is that Pipedrive activities are Tasks in Spiich. Ask the assistant about your tasks and it is your Pipedrive activities it is talking about. A task created or completed in Spiich turns into the matching change on the activity in Pipedrive.

How it stays current

Spiich subscribes to Pipedrive webhooks for every action on deals, persons, organizations, activities, notes, users and pipelines, so changes made in Pipedrive reach Spiich without waiting for a poll. Once an hour Spiich also re-reads your field definitions and users, which is how a field you just added in Pipedrive becomes usable.

Writes go the other way in the same action. When you or an agent creates or edits a record, task or note in Spiich, it is pushed to Pipedrive straight away. If Pipedrive refuses the write you see a message beginning Pipedrive error: and Spiich undoes its own change, so nothing survives in Spiich that Pipedrive rejected.

There is no manual resync anywhere in the product, and none is needed.

What Pipedrive has no equivalent of

Some things you may have read about in the HubSpot or Attio guides simply do not exist here, and Spiich does not pretend otherwise.

• No leads or tickets. Those are HubSpot objects. There is no Pipedrive equivalent to connect.
• No custom objects. Spiich syncs the five record types above. Pipedrive custom fields on those records do sync and get their own switches; whole custom objects do not.
• No lists. List tools are Attio-only and are not offered on a Pipedrive workspace.
• No email sync. Spiich does not pull email history from Pipedrive. The CRM Emails switch in Settings > Object Types only has an effect on workspaces whose CRM syncs email, which today is HubSpot. Your own mailbox is a separate, per-person connection: see Connect Gmail and Google Calendar.
• No call recording backfill at connect. Attio queues 28 days of recordings on connect; Pipedrive does not. Meetings you record with Spiich work exactly the same either way.

Limits

• One CRM per workspace, and no Disconnect button. A connected Pipedrive shows a greyed-out Connected badge. Switching CRMs is a support request.
• Reconnecting must target the same Pipedrive account. Spiich checks the API domain and refuses a different one.
• Field definitions refresh hourly, so a brand-new custom field is not immediately available to the agent.
• Which objects and fields the agent may read and change is set at Settings > Object Types, and only admins can change it. See Control what Spiich can see and change.

If something goes wrong

*Saving a record fails with Pipedrive error: and the record vanishes.* Pipedrive rejected the write, usually a required field or an invalid value. Read the message, supply what it asks for and save again. The rollback is deliberate: it stops Spiich holding a record Pipedrive refused.

A task you completed in Spiich is still open in Pipedrive. Check the object's Writable switch in Settings > Object Types. If Tasks are not writable, the agent and the interface can read activities but not change them.

A newly added Pipedrive field is not selectable. Field definitions are re-read hourly. Wait for the next refresh.

*Chat shows Reconnect to Pipedrive. Spiich needs a permission the existing connection does not hold. An admin clicks Reauthenticate* and approves. Members do not see the banner.

Filtering a deal table by pipeline returns nothing. Older saved filters stored Pipedrive's internal pipeline ID while synced deals store the readable pipeline name. Re-pick the pipeline by name in the filter and save.