Skip to main content

Send commercial briefs from Google Calendar meetings to Pipedrive via Gmail

Workflow preview

Workflow preview
100%
Send commercial briefs from Google Calendar meetings to Pipedrive via Gmail preview
Open on n8n.io

1. Workflow Overview

Who it's for This workflow is designed for sales teams and business development managers who use Pipedrive to track leads and Google Calendar to schedule discovery calls. It automates the sending o...

Best for

  • Lead Nurturing automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.stickynote, n8n-nodes-base.scheduletrigger, n8n-nodes-base.code, n8n-nodes-base.httprequest, n8n-nodes-base.pipedrive, n8n-nodes-base.googlecalendar, n8n-nodes-base.filter, n8n-nodes-base.gmail

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Allan Vaccarizi.

Original n8n.io source

1.1 Workflow description

Title
Send commercial briefs from Google Calendar meetings to Pipedrive via Gmail
Workflow name
Send commercial briefs from Google Calendar meetings to Pipedrive via Gmail

Who it's for

This workflow is designed for sales teams and business development managers who use Pipedrive to track leads and Google Calendar to schedule discovery calls. It automates the sending of commercial briefs before meetings, eliminating manual follow-up steps.

How it works

  1. A schedule trigger fires every 30 minutes and fetches upcoming appointments from a Google Calendar.
  2. A JavaScript code node filters events matching a specific meeting title and extracts attendee emails, excluding internal team members.
  3. Each attendee email is looked up in Pipedrive to retrieve the matching contact person.
  4. The workflow fetches the associated lead in Pipedrive and filters out leads that don't exist or already have the "brief sent" label.
  5. Existing notes on the lead are retrieved, and leads with at least one note are filtered out to prevent duplicate sends.
  6. A commercial brief email is sent via Gmail to qualifying leads, and the Pipedrive lead label is updated to mark the brief as sent.

How to set up

  • Connect your Google Calendar account and set the correct calendar ID in the "Fetch Calendar Appointments" node
  • Update the JavaScript filter in "Parse Calendar Events" with your meeting title and internal team emails
  • Connect your Pipedrive account and verify API credentials in all Pipedrive and HTTP Request nodes
  • Connect your Gmail account and customize the email subject, body, and recipient field
  • Review the filter conditions to match your Pipedrive label IDs for the brief-sent flag

Requirements

  • Google Calendar account (OAuth2)
  • Pipedrive account with API access
  • Gmail account (OAuth2)

How to customize

  • Adjust the schedule trigger interval (e.g., once per day in the morning) to better match your meeting cadence
  • Replace Gmail with an SMTP or Outlook node if your team uses a different email provider
  • Extend the workflow to also create a Pipedrive activity or note after sending the brief, for full CRM traceability

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Sticky Note

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 2 - Sticky Note1

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 3 - Sticky Note2

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 4 - Sticky Note3

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 5 - Sticky Note4

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 6 - Sticky Note5

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 7 - Every 30 Minutes

Type / Role
n8n-nodes-base.scheduleTrigger - scheduleTrigger
Config choices
Version 1.3

Block 8 - Parse Calendar Events

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 9 - Fetch Pipedrive Notes

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.3

Block 10 - Fetch Lead from Pipedrive

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.4

Block 11 - Fetch Person from Pipedrive

Type / Role
n8n-nodes-base.pipedrive - pipedrive
Config choices
Version 1

Block 12 - Fetch Calendar Appointments

Type / Role
n8n-nodes-base.googleCalendar - googleCalendar
Config choices
Version 1.3

Block 13 - Filter Lead Exists and Brief Sent

Type / Role
n8n-nodes-base.filter - filter
Config choices
Version 2.3

Block 14 - Filter Note Exists

Type / Role
n8n-nodes-base.filter - filter
Config choices
Version 2.3

Block 15 - Send Commercial Brief Email

Type / Role
n8n-nodes-base.gmail - gmail
Config choices
Version 2.2

Block 16 - Update Lead Label in Pipedrive

Type / Role
n8n-nodes-base.pipedrive - pipedrive
Config choices
Version 1

Block 17 - Sticky Note13

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 18 - Sticky Note16

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

3. Summary Table

Workflow Send commercial briefs from Google Calendar meetings to Pipedrive via Gmail
Complexity advanced
Nodes 18
Categories Lead Nurturing
Author Allan Vaccarizi
Published 19 May 2026

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/15819/15819.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does Send commercial briefs from Google Calendar meetings to Pipedrive via Gmail do?

Who it's for This workflow is designed for sales teams and business development managers who use Pipedrive to track leads and Google Calendar to schedule discovery calls. It automates the sending o...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Lead Nurturing use case.