Coworker Product and Developer Docs
  • 📘Welcome to Coworker.ai
    • Welcome to Coworker
    • Self Service Onboarding
    • Village Assistant
      • Github PR Review Tool
    • Security & Compliance
    • Data Privacy & Permissions
  • 🔌Data Connections
    • Airtable
    • Ashby
    • Clickup
      • Finding ClickUp User IDs
    • Figma
    • Github
      • Finding GitHub User IDs
    • Gitlab
    • Google - OAuth (Recommended)
    • Google - Manual Connection
    • Hubspot
    • Jira
      • Finding Jira User IDs
    • Confluence
      • Finding Confluence / Jira User IDs
    • Linear
    • Asana
    • Monday
    • Notion
    • Pipedrive
    • Slack
    • Basecamp
    • Zoom
  • 👩‍💻Legacy Developer Docs
    • Developer Quickstart
    • Village APIs: Introduction
      • Activity API
      • User Status API
      • Patch User API
      • Segments API
      • Redemption API
      • Master Award Controls
      • Connections (Referrals) APIs
      • GET APIs
    • 3rd Party Payments Integrations
    • Embedding Village Dashboards
  • 🕵️LEGACY Knowledge Base
    • Admin Quickstart
    • Referrals Support
    • The Basics of Village in 15 Minutes
    • Programs & Rules
      • Triggers
        • Activities
        • Goals
      • Conditions
        • Segment Conditions
        • Time Conditions
        • Max Budget Conditions
        • Conditional Multipliers
    • Awards
      • Monetary (Cash) Awards
      • Non-Monetary Awards
        • Funding
          • In-depth use cases for funding pools
      • Badges & Statuses
      • Award Expiration
    • Segments
      • Segmentation Use Cases
    • Rule Evaluation Logic Deep-dive
    • The Village Dashboards
      • Admin Account Creation
      • User Access Management
      • Network Settings
      • User Dashboard
    • BigQuery
    • Managing Payment Integrations
    • Referrals (Connections)
      • Pre-populating Users' Unique Referral Codes In Signup Flows & Forms
  • No and Low Code Solutions
    • No and Low Code Solutions
      • No & Low Code Solutions
  • Feedback
    • Village Docs Feedback Form
    • Feature Requests
    • Talk to our Team
Powered by GitBook
On this page
  • Prequisites
  • Generating the credentials
  • Information required for the Coworker connection:

Was this helpful?

  1. Data Connections

Pipedrive

How to connect your Pipedrive instance to Coworker

PreviousNotionNextSlack

Last updated 8 days ago

Was this helpful?

Prequisites

  • A Pipedrive account with sufficient permissions

Important note: the scope of the data which will be synchronized to Coworker is defined by the user behind the API key. We recommend that you create a service account which will have the right permissions, ie. no access to sensitive deals/data.

Generating the credentials

Log in as the service account which will make the API key, and go to the API settings page (/settings/api).

Click on "Generate" to make a new API key.

Although Pipedrive does not offer granularity on the permissions associated to a token, Coworker will not be making any write operation on your data. In order to sync your data in real time, webhooks will be configured, this is the only write action which will be done.

Information required for the Coworker connection:

  • api_key: the API key generated above

  • start_date: the date of the first document that should be synchronized. No document updated before that will be synchronized. Format: ISO8601 date, ie. 2024-05-01T00:00:00Z

🔌