Help / Integrations

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 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.
• Choose the activity type per event type — log each event type as the Pipedrive activity that fits (Demo, Call, Meeting…), or let everything use one default.
• Watch the sync log — recent sync activity, with any errors, on the integration's log page (Integrations → Pipedrive → Sync log).

Zoom

How to do it

1. Open 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.

Set the activity type per event type

When a booking is created, 42min logs a Pipedrive activity. By default every booking uses the same type — the Default activity type set under Create Activity. If you'd rather have a "Demo" event log as a Demo activity while a "Quick chat" logs as a Call, add a per-event-type override on the Pipedrive settings page:

1. Under Create Activity, find Per-event-type overrides.
2. Click Add override, pick an event type, then pick the activity type it should create.
3. Add a row for each event type you want to redirect. Anything you don't list keeps using the default activity type.
4. Save.

Each booking uses its event type's override if one exists; otherwise it falls back to the default activity type.

Saving also tidies the list: blank rows, duplicate event types, and overrides pointing at an event type that no longer exists are dropped, so a saved override always does something. (If the event-type list can't load when you save, your existing overrides are left untouched rather than cleared.)

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.