The Pipedrive integration connects your meeting recordings and AI-generated summaries from tl;dv to your CRM, helping you keep your sales records up to date without manually copying information between tools.
With the integration, you can update properties on contacts, deals, and companies, or log meetings and notes as activities.
There are 2 ways to sync your meeting information:
Automatically: Set up a workflow that runs whenever a new meeting recording matches your conditions.
On demand: Choose a meeting and manually trigger an existing workflow.
This guide explains how to connect to Pipedrive, configure your workflows, and troubleshoot common syncing issues.
Part 1: How tl;dv matches meetings to Pipedrive records
Everything else in this article depends on how tl;dv identifies the correct CRM records, so it's worth understanding this first.
How meeting matching works
When a recording finishes, tl;dv checks the email addresses of the invitees on the calendar event and looks for matching Persons in Pipedrive.
🚨 Important: The matching key is the calendar invitee's email address. Before creating a workflow, make sure the people invited to your meetings exist as Persons in Pipedrive or select a toggle Create new contact if no existing option is available. Otherwise, the workflow may not have an existing record to update.
Once a matching Person is found, tl;dv can use the associated CRM records.
Part 2: Connect Pipedrive to tl;dv
Open the Pipedrive integration
In tl;dv, click Integrations in the left sidebar, then click the Pipedrive tile in the Marketplace tab.
Click Connect to Pipedrive, choose the Pipedrive account you want to link, and click Allow to complete OAuth authorization. You only need to do this once per tl;dv account.
Once connected, the Pipedrive page shows your Connection, your Active workflows, and Additional setup options.
Turn on "Tag meetings with the CRM info"
Scroll to Additional setup options at the bottom of the Pipedrive page and switch on Tag meetings with the CRM info.
This is the setting that links each meeting to its Pipedrive contact, company, and deal. Turning it on gives you:
the CRM Info panel on every meeting page, showing the contact and deal the meeting is linked to - see Part 5;
that CRM data as filters in your meeting library - including a Meeting deal stage filter, so you can pull up every call that happened at a given point in the pipeline;
that CRM data as conditions in AI template automation, so the right notes template is applied based on the CRM record or the deal stage;
richer AI analysis across meetings.
🚨 Applies to future meetings only. Meetings recorded before you turn this on won't be tagged retroactively. You need to connect Pipedrive (above) before this toggle does anything.
Turn it on for the whole team at once
Team admins on the Business plan or above can enable tagging for everyone at once, instead of asking each person to do it - the same permission that lets you create team workflows.
On the Pipedrive integration page, click the filter icon next to New workflow.
Under Filter by workflow owner, select your team instead of Personal workflow.
The page switches to the team scope. Switch on Tag meetings with the CRM info there.
Part 3: Create an automated Pipedrive workflow
Workflows help you automatically send relevant meeting information from tl;dv to Pipedrive. Instead of updating your CRM manually after every call, you can define what information should be synced and when.
Workflow types
When you create a workflow, you choose its scope:
Individual workflow - it applies only to the meetings recorded by you
Teamworkflow - it applies to meetings recorded by your team members
Use an individual workflow for personal experiments, and a team workflow when you want consistent automation across the team. Team workflows can be created by team admins on the Business plan or above.
Available Pipedrive actions
Action | Type | What it does |
Update Contact in Pipedrive | Property update | Writes meeting data into fields on the matched contract |
Update Lead in Pipedrive | Property update | Writes meeting data into fields on the matched lead |
Update Deal in Pipedrive | Property update | Writes meeting data into fields on the deal linked to that contact |
Create Activity in Pipedrive | Activity creation | Logs a meeting or note on a contact, deal or a lead |
Setup follows the same flow for all four actions. The only differences appear in Step 5 (Configure the action).
1. Open the Pipedrive integration
In tl;dv, click Integrations in the left sidebar, then click the Pipedrive tile in the Marketplace tab.
2. Choose a workflow type
Select Individual workflow or Team workflow, then click Confirm.
3. Pick an action
Choose one of the four actions and click Try it now.
4. Set the trigger and conditions
Under Trigger this workflow when, select A new meeting recording is ready.
(Optional) Click Add condition to limit when the workflow runs. Available criteria include Meeting type, Role, Personal attendance, Meeting title, Participant email, and Email domain.
If you add multiple conditions, choose All (every condition must match) or Any (one match is enough).
Click Continue.
💡 Use conditions to keep your workflows focused. For example: only run for external meetings, or only when the meeting title contains "Demo".
💡 You can also leave the workflow OFF and run it only when you want it, using Trigger now (Part 4).
5. Configure the action
This step looks slightly different depending on the action you picked.
For Update Contact, Lead, or Company
Leave Create new Contact if no existing option is available turned ON. When no match exists, tl;dv creates a new Contact.
Email is pre-filled with Participants email.
For each property you want to populate, choose how to fill it:
Insert tl;dv data - drop variables like Meeting title, Meeting notes, Transcript, or Participants email into the field.
Custom prompt - switch on the Custom prompt toggle in the top-right of the field, then write a free-text instruction. tl;dv runs the prompt against the meeting and writes the result into the property.
🚨 Property mapping currently supports text-format properties only. Number, date, , and other property types aren't supported yet.
💡 New values are appended below existing content in open-text properties, so the most recent meeting appears at the bottom.
For Create Activity
Pick an Activity type: Meeting or Call.
Under Linked object, choose Contact, Lead, or Deal.
Fill in Title and Content using inserted variables, custom prompts, or both.
💡 Use a custom prompt when you want activity content that differs from your tl;dv meeting notes for example, a shorter summary for the activity feed, or internal-only notes that customers shouldn't see.
6. Test the workflow
Click Continue to reach the Test step.
Select a recent meeting and click Test workflow. tl;dv runs the workflow once so you can verify the result in Pipedrive before going live.
When the test completes successfully, click Activate workflow.
7. (Optional) Rename your workflow
Click the workflow title at the top of the page (e.g., Integration 1) and rename it to something descriptive like Sales - Contact sync or CS - Activity log. This makes the workflow easier to find later, and easier to pick from the Trigger now menu.
Part 4: Run a Pipedrive workflow manually
The next three sections all happen on the meeting page in tl;dv, not on the Integrations page.
Automatic workflows run on everything that matches their conditions. Trigger now lets you run a workflow on one specific meeting, whenever you want.
Open the meeting in tl;dv.
In the top-right toolbar, click Trigger now.
Pick one of your existing workflows from the list.
Trigger now works with every native tl;dv integration - Pipedrive, Slack, Notion, HubSpot, Salesforce, and the rest.
When to use it
Keep automation selective. Leave your workflows OFF and sync only the meetings you choose.
Retry a meeting that didn't match. If a meeting had no invitee data, add the participants (Part 7), then trigger the workflow manually.
Sync a meeting you didn't record. Automatic workflows only trigger for the person who created the recording. Trigger now also works on meetings recorded on someone else's tl;dv account that you have access to.
💡 The workflow must already exist on the Integrations page. Trigger now runs existing workflows; it doesn't create them.
Trigger now runs individual and team workflows alike, and the workflow's conditions still apply. You're running the same workflow you built for automation - manual triggering only changes when it runs, not what it checks. If the meeting doesn't match the workflow's conditions, nothing happens.
Triggering twice creates duplicates
🚨 tl;dv does not check whether a workflow has already run on a meeting.
If you trigger a workflow that already ran, automatically or manually, it runs again from scratch: a second activity is created on the record, and property values are written a second time. Nothing is skipped, matched up, or overwritten.
So before you re-run a workflow on a meeting, delete whatever the previous run wrote in Pipedrive. This matters most when you're fixing a bad CRM link (see Part 5).
Part 5: Check and update the Pipedrive CRM link
CRM Info shows which Pipedrive records a meeting is linked to, and lets you correct the link when the automatic match is wrong.
That link isn't only for reading. Once a meeting carries its CRM data, you can filter your meeting library by it and use it as a condition in AI template automation - so keeping the link accurate is worth the occasional manual fix.
ℹ️ Requires Tag meetings with the CRM info (Part 2).
The panel shows:
Field | What it shows |
Contact | The Pipedrive contact matched to an external invitee |
Company | The company linked to that contact |
Deal | The deal this meeting is linked to - searchable and changeable |
Pipeline | The pipeline the linked deal belongs to |
Dealstage - At the time of the meeting | The stage the deal was in when the meeting happened |
Dealstage - Current stage | The stage the deal is in right now |
Change the linked records
If the automatic match is wrong, or the meeting should be attached to a different deal, search for and select the right record directly in the panel.
🚨 Changing the link in tl;dv does not move data that has already synced. Activities, notes, and property values already written to Pipedrive stay where they are. To move them: delete the data in Pipedrive first, fix the link in CRM Info, then re-run the workflow with Trigger now. If you skip the deletion step you'll end up with the data in both places - re-running never cleans up after a previous run.
Deal stage: which one is stored, and what you can do with it
The CRM Info panel shows two stages, and the difference matters:
Stage | What it is |
At the time of the meeting | The stage the deal was in when the recording was synced to Pipedrive. This value is frozen - it doesn't change as the deal advances. |
Current stage | Where the deal sits in Pipedrive right now. |
💡 If you link or change the deal manually in CRM Info, the stored stage is the one from the moment you made that change — not the stage on the day the meeting happened. tl;dv describes it as "deal stage at the time of the meeting, or when the last synchronization with the CRM was performed."
Because the stage is stored with the meeting, you can use it in two places.
Filter your meeting library by deal stage
In your meeting library, open the Meeting deal stage filter, pick a pipeline, then pick a stage.
This pulls up every call that happened at a given point in the pipeline for example, every Discovery/Demo Completed conversation, so you can hear what tends to move deals forward from there.
Apply a notes template based on deal stage
Deal stage is also available as a condition in AI template automation, so the right template is applied automatically.
Open the notes template you want to automate.
Under Automate this template for future meetings, open the Any CRM Deal Stage dropdown.
Pick the stage that should trigger this template. Stages are listed with their pipeline in brackets, e.g. Sales Qualified (SMB + MM Pipeline).
Click Save and activate.
💡 For example: a discovery-focused template on Discovery/Demo Booked meetings, and an objection-and-pricing template on Trial Completed/Decision Pending meetings.
Part 6: Add missing participants to a recorded meeting
Meetings joined by share link, or recorded in person, often have no invitee data so there's nothing to match to Pipedrive, and nothing to filter by in your library.
You can add the participants yourself after the recording:
Open the meeting in tl;dv.
Hover over the information (ⓘ) button in the top-left of the meeting page. It shows the recording's creator and its invitees.
Click the pencil mark then enter an email address to add a participant.
Once the participants are correct:
the meeting appears under the right library filters;
the meeting can be matched to Pipedrive, so its CRM Info fills in; and
you can run the sync with Trigger now.
Use custom prompts to capture relevant CRM information
Custom prompts let you generate exactly the text you want for a property or activity. They are useful when a fixed variable mapping doesn't capture the nuance you need.
Example: Competitor info on a deal property
Extract information about the competitor that the customer mentioned in the meeting. Summarize in one sentence. If not mentioned, do not update anything.
Example: Next steps on a company property
Summarize the agreed-upon next step from the conversation in one sentence. If a date is mentioned, include it clearly.
Tips for writing prompts:
Be specific about format. Tell the prompt to write a single sentence, a bulleted list, or a specific template.
Handle empty cases. Tell tl;dv what to write when the topic isn't discussed (e.g., "If not mentioned, write 'Not discussed.'").
Constrain length. Without an instruction, output can run long. Add "no more than 2 sentences" or similar.
Troubleshooting
Why didn't my meeting sync to Pipedrive?
Check that:
The workflow toggle at the top right of the workflow page is ON.
The meeting matches the conditions you set.
The calendar event has at least one external invitee. Invitees from your own email domain are filtered out, so internal-only meetings never match.
That invitee's email matches a Pipedrive contact, or Create new Contact if no existing option is available is enabled.
The recording's creator is in scope for the workflow:
Individual workflows only trigger on meetings recorded by you.
Team workflows only trigger on meetings recorded by team members. They don't apply to team admins or billing group admins, so if you're an admin, your own meetings won't trigger a team workflow.
If the meeting simply had no invitees, add them manually (Part 7) and then use Trigger now.
If you still need support, please reach out to us at support@tldv.io and include the following information:
The link to the meeting that didn’t sync to Pipedrive. If several meetings are affected, send a few examples.
A screenshot of the calendar event for this meeting, with the invitee list clearly visible.
The email address of the person who recorded the meeting.
The name of the workflow that should have run, and whether it’s an individual or team workflow.
A screenshot of the workflow’s setup, including its conditions and action settings.
Whether you use a scheduling tool, such as Calendly, to book these meetings?
Common questions
The meeting is linked to the wrong deal. Can I fix it?
Yes , open CRM Info on the meeting page and select the correct deal. Note that data already synced to Pipedrive doesn't move: delete it in Pipedrive, fix the link, then re-run the workflow with Trigger now.
Can I sync a meeting that someone else recorded?
Automatic workflows only run for the person who created the recording. For meetings recorded on someone else's tl;dv account, open the meeting and use Trigger now.
I turned on CRM tagging. Why don't my older meetings show CRM Info?
Tag meetings with the CRM info applies to future meetings only. Meetings recorded before you enabled it aren't tagged retroactively.
Does Trigger now skip the workflow's conditions?
No. Manual triggering runs the same workflow with the same conditions — it only changes when the workflow runs. If the meeting doesn't match the conditions, nothing happens. It also works with team workflows, not just individual ones.
Can I have different workflows for different meeting types?
Yes. Create a separate workflow for each scenario and use Conditions to scope it. For example, one workflow for External — First call, another for External — Demo.
Does the activity link back to the original recording?
Yes. When you include the meeting URL or the meeting notes in the activity content, timestamps in the notes link back to the exact moment in the tl;dv recording.