Skip to main content

Connect Pipedrive to Flex through Zapier

Create leads, deals and activities automatically between Pipedrive and Flex, so your sales pipeline and your member records stay in step without manual entry.

Written by Yasen Marinov

Your sales team tracks deals in Pipedrive while your operations team manages members and contracts in Flex. Keeping both updated by hand means a signed contract or a won deal sits unprocessed until someone remembers to act on it. Connecting the two through Zapier creates a matching record automatically the moment a deal closes, a contract is signed, or a prospect tours your space.

This works through Zapier's official Flex app. The app supports a fixed set of triggers and actions, so each workflow you build runs as its own one-directional Zap, not a continuous two-way sync.


Prerequisites

Before you connect Pipedrive and Flex, confirm the following:

  • An active Pipedrive account, on any plan that includes a free trial.

  • Pipedrive API access enabled for your user account. This is on by default but can be turned off by an admin.

  • Admin access in Flex, using your Flex admin credentials or a Client ID and Client Secret if your organization uses SSO.


Important notes

Flex triggers in Zapier check for changes on a polling cycle, typically every 15 minutes, not instantly. Custom properties of type date or multi-select aren't supported in Flex triggers or actions.

Pipedrive is retiring its V1 API on July 31, 2026. Zapier is renaming any affected trigger, action, or search to include "[DEPRECATING JULY 31 2026]" in its name so it's identifiable inside the Zap editor. If you build any of the workflows below and see that label on a step, select the identically named step without the label instead. Steps still on the deprecated version stop working after that date.


Example workflows

These five Zaps follow a prospect from their first tour through to onboarding, and cover what to do when a deal closes or a member leaves.

Send new Flex opportunities to Pipedrive as deals

When your team logs a new opportunity in Flex, this Zap creates a matching deal in Pipedrive so sales can track it through their existing pipeline stages.

Trigger

Action

OfficeRnD triggers, actions, and search

New Opportunity

Triggers when a new opportunity is added.


Filter it by organization and status.

Pipedrive triggers, actions, and search

Create Deal

Creates a new deal.

Create a Pipedrive activity when a new contract appears in Flex

When a member signs a contract in Flex, this Zap creates a follow-up activity in Pipedrive, so the account owner has a task to check in rather than relying on memory. This is the most commonly used Zap for this integration.

Trigger

Action

OfficeRnD triggers, actions, and search

New Contract

Triggers when a new contract is added.


Filter it by organization, location, and status.

Pipedrive triggers, actions, and search

Create Activity

Creates a new activity in Pipedrive with comprehensive options for scheduling, participants, and associations.

Onboard a new Flex member when a Pipedrive deal is won

When a deal moves to Won in Pipedrive, this Zap creates the member in Flex, so operations can start onboarding without waiting for a handoff email.

Trigger

Action

Pipedrive triggers, actions, and search

Updated Deal

Triggers when an existing deal is updated.


Watch the Status field for a change to 'Won'.

OfficeRnD triggers, actions, and search

Create Member

Creates a new member.

Log a follow-up activity when a member cancels

When a member's status changes to canceled or terminated, this Zap creates an activity in Pipedrive for the account owner, so churn turns into a scheduled win-back call instead of a line in a monthly report.

Trigger

Action

OfficeRnD triggers, actions, and search

New Member/Member Status Updated

Triggers when a new member is added or when a member's status is changed.


Filter by 'Status'.

Pipedrive triggers, actions, and search

Create Activity

Creates a new activity in Pipedrive with comprehensive options for scheduling, participants, and associations.

Note: This Zap uses the same Flex trigger as the contract-to-activity Zap above, filtered on a different value. Setting up both is fine. They run independently.

Did this answer your question?