# Pipedrive

Connect **Pipedrive** so your 42min bookings show up in your CRM without anyone copying
them over by hand. New bookings, the contacts behind them, and meeting activities sync
across automatically. You set it up on the [**Integrations**](/360/integrations) page,
and there's a settings page and a sync log once it's connected.

## What it does

- **Connect** your Pipedrive account (OAuth) from Integrations → CRM.
- **Sync bookings → activities/meetings**, and **invitees → persons/contacts**, so a
  booked meeting is visible on the right Pipedrive record.
- **Map users** — match your 42min users to Pipedrive users so synced records are owned
  by the right person.
- **Pick what syncs** — choose which events (new booking, cancellation, reschedule,
  etc.) push to Pipedrive.
- **Watch the sync log** — recent sync activity, with any errors, on the integration's
  log page (Integrations → Pipedrive → Sync log).

<Screenshot
  src="/help/screenshots/integrations/list.png"
  alt="The Integrations page in the 42min dashboard, with a Pipedrive 'Connect Pipedrive' card under CRM and a Calendly card under Data Import"
  caption="Integrations → CRM → Pipedrive. Once connected, a Settings button opens the field/user mapping and sync options."
/>

## How to do it

1. Open [**Integrations**](/360/integrations) and click **Connect Pipedrive**; sign in
   and authorize 42min.
2. On the Pipedrive **settings** page, map your 42min users to Pipedrive users and
   choose which events should sync.
3. Adjust any field mapping if offered, then save.
4. After a few bookings, check the **sync log** to confirm records are landing where you
   expect.

## Common pitfalls

- **Records owned by the wrong person.** That's a user-mapping gap — make sure every
  active 42min host is mapped to a Pipedrive user.
- **Connected but nothing appears.** Check which events you've enabled for sync — if
  "new booking" isn't on, new bookings won't push.
- **Sync errors.** The sync log surfaces them (auth expired, missing required field,
  rate limits). Reconnect or fix the mapping, then let it retry.
- **Removing the connection.** Disconnecting Pipedrive stops future syncs; it doesn't
  remove records already pushed.