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.
• Create deals and notes for new bookings, and leads for routing-form submissions, if you turn them on.
• 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, no-show, routing-form submission) 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

Connecting and changing the settings are admin-only.

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. Choose what each event creates or updates in Pipedrive (see the settings page below), then click Save Settings.
4. After a few bookings, check the sync log to confirm records are landing where you expect.

How the sync works

Every time something happens to a booking (it's made, canceled, rescheduled, or marked as a no-show), 42min checks whether that event's trigger is on and, if it is, sends the changes to Pipedrive in the background. The booking itself never waits on Pipedrive.

• New booking. 42min finds the invitee's Pipedrive person by email, or creates one, and then creates whatever you've switched on: a deal, an activity for the meeting, and a note. They're all linked to that person, and to the deal if one was created.
• Later changes. A cancellation, reschedule, or no-show updates the records 42min created for that booking. Records you made by hand in Pipedrive, and bookings made before you connected, are left alone.
• Routing forms. When the routing-form trigger is on, each submission can create a Pipedrive lead (and a person) straight from the answers, whether or not the respondent goes on to book.
• Retries. If Pipedrive doesn't answer or returns an error, 42min retries the sync up to five times, waiting a little longer each time. Each failed attempt shows in the sync log.

Settings apply to events from the moment you save; nothing is re-sent for bookings that already synced.

The settings page

Once connected, open the Pipedrive settings page from the Pipedrive card on Integrations. A section for an event only appears while its trigger is on, so the page gets shorter as you turn triggers off.

Zoom

Nothing on the page takes effect until you click Save Settings at the bottom. That one button saves both the sync options and the user mapping.

Connection buttons

Under the title, Connected as shows the Pipedrive company you're linked to.

• Reconnect runs the Pipedrive sign-in again over the existing connection. Use it when the page shows a red "connection is broken" banner (Pipedrive rejected the saved credentials). Your settings and user mapping are kept.
• Disconnect stops all syncing and removes the connection, including these settings and the user mapping. Records already in Pipedrive stay there.
• View sync log opens the sync log.

Triggers

Pick which events push data to Pipedrive. Each has its own section below, shown only while it's on.

On booking created

• Create Person. Finds the invitee in Pipedrive by email, or creates a person with their name, email, and phone. The phone comes from the booking's phone field, or from a phone-number question on the booking form.
  • If person exists: Update overwrites the existing person's name and phone with what the invitee entered. Skip links the booking to that person and leaves their details as they are.
• Create Activity. Logs the meeting as a Pipedrive activity: titled with the event type's name, set to the booking's date, time, and length, and linked to the person and deal. The activity's note uses the Create Note template below.
  • Default activity type: the Pipedrive activity type every booking uses, unless an override says otherwise. The list is read from your Pipedrive account, so custom types appear too.
  • Assign to: Matched host gives the activity to the Pipedrive user mapped to the booking's host (see User mapping). Pipedrive account owner gives every activity to the Pipedrive user who connected 42min.
  • Per-event-type overrides: log some event types as a different activity type. See Set the activity type per event type.
• Create Note. Adds a note to the person (and the deal, if one is created). Edit the text in the box; HTML such as <b> and <br> is allowed. It can use these variables: {{event_name}}, {{event_date}}, {{event_time}}, {{event_timezone}}, {{event_duration}}, {{event_location}}, {{host_name}}, {{invitee_name}}, {{pipedrive_activity_type}}, and a {{#form_answers}}…{{/form_answers}} block that repeats {{question}} and {{answer}} for every booking-form and routing-form answer. Dates and times are written in the booking's own time zone.
• Create Deal. Opens a deal for every booking, owned by the host's mapped Pipedrive user.
  • Pipeline and Stage: where the deal starts. The stage list shows the stages of the pipeline you picked. Both are required: with either one left blank, no deal is created.
  • Deal title template: the deal's name, built from {{event_name}}, {{invitee_name}}, {{host_name}}, {{event_date}}, and {{pipedrive_activity_type}}.

On booking canceled

• Mark activity as canceled. Marks the booking's activity as done and puts [CANCELED] in front of its title.
• Add note with cancellation details. Adds a note to the person and deal with the cancellation reason (if the invitee or host gave one) and the time the meeting was scheduled for.
• Move deal to a canceled stage. Moves the booking's deal to the Canceled stage you pick (a "Lost" or "Canceled" stage, say).

On booking rescheduled

• Update activity date and time. Moves the activity to the new date, time, and length.
• Add note with old → new time. Adds a "Rescheduled" note to the person and deal with the meeting's new time.

On booking no-show

When a host marks a booking as a no-show:

• Mark activity as no-show. Marks the activity as done and puts [NO-SHOW] in front of its title.
• Add note with no-show details. Adds a note to the person and deal with the reason (if one was given) and the time the meeting was scheduled for.

On routing form submitted

• Create Lead. Adds a lead to Pipedrive's Leads inbox for every routing form submission.
  • Lead title template: the lead's name, built from {{form_name}}, {{respondent_email}}, and {{routing_destination}}.
  • Include form answers and Include routing destination add a note to the lead with the answers and with where the form sent the respondent.
• Create Person. Finds the respondent in Pipedrive by email, or creates a person from the name, email, and phone answers. It needs an email answer to work; an existing person is linked but not changed.

Each submission also logs a Pipedrive Task activity, due the day the form was sent, owned by the Pipedrive user who connected 42min, with the answers in its note. There's no switch for this one on the settings page.

User mapping

A table of your 42min hosts, each with a Pipedrive user dropdown. 42min matches them by email when you connect, and again for anyone who joins your organization later, so most rows fill themselves. Fix any mismatch by hand, or pick (Not matched) for a host who has no Pipedrive seat.

The mapping decides who owns the activity (with Assign to: Matched host) and every deal. A booking whose host isn't mapped still syncs, but its records go to the Pipedrive user who connected 42min.

Field mapping

Shows which booking fields fill which Pipedrive person fields: the invitee's name, email, and phone go to the person's name, email, and phone. These three rows are fixed (marked with a lock) and always sync.

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.)

The sync log

Click View sync log on the settings page to see every sync 42min has attempted: the trigger, the booking or form response it was about, whether it worked, and the error if it didn't. Filter by status (success, partial, failed, retrying) or by trigger. Entries are kept for 30 days.

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.
• Changes don't stick. Settings and user mapping only save when you click Save Settings; leaving the page drops unsaved edits.
• No deal created. Create Deal needs both a Pipeline and a Stage.
• A cancellation didn't update Pipedrive. Cancel, reschedule, and no-show updates only touch records 42min created for that booking. A booking made before you connected, or with Create Activity off, has no activity to update.
• 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 and clears your Pipedrive settings and user mapping; it doesn't remove records already pushed. To fix a broken connection, use Reconnect instead, which keeps your settings.