Before you begin

  • Create a Pipedrive API token or OAuth app with permissions for people, organizations, and leads.
  • Decide whether to create or find a Person by email/phone before creating the Lead.
  • Create custom fields for InstaChime lead ID, source platform, score, and campaign if you want them in Pipedrive.
  • Choose a bridge, Zapier, or Make scenario to transform the InstaChime webhook into Pipedrive API calls.

Pipedrive flow

  • Find or create a Person using the lead email and phone.
  • Find or create an Organization if company information exists.
  • Create a Lead linked to the Person, Organization, or both.
  • Add notes for lead message, campaign, and response context.
  • Store the Pipedrive lead ID in the InstaChime delivery response.

Lead create shape

{
  "title": "Jamie Lee - Google Ads demo request",
  "person_id": 123,
  "organization_id": 456,
  "owner_id": 789
}

Verify

  • Send a sample InstaChime lead and confirm the Person is created or matched.
  • Confirm the Lead appears in Pipedrive Lead Inbox with the correct title and linked person.
  • Confirm notes or custom fields include the InstaChime lead ID.
  • Confirm API validation errors are visible in the InstaChime delivery history.

Exact Pipedrive setup

  • Create or choose an API token/OAuth app with access to people, organizations, leads, and notes.
  • Create custom fields for InstaChime lead ID, source platform, campaign, score, and sentiment if required.
  • Build a bridge, Zap, or Make scenario that receives `lead.created`.
  • Search for an existing Person by email or phone.
  • Create the Person if no match is found.
  • Search for or create an Organization if company data exists.
  • Create the Lead and link it to the Person, Organization, or both.
  • Add a note with the lead message and routing context.
  • Return the Pipedrive lead ID to InstaChime.

Pipedrive field decisions

  • Use a title pattern that sales users can scan, for example `Jamie Lee - Google Ads demo request`.
  • Set owner based on InstaChime assignment only if your Pipedrive account uses owner routing.
  • Keep source information in a custom field or note because Pipedrive API-created leads have API origin/source behavior.
  • Add labels only after confirming label IDs in the target account.
  • Do not create orphan leads; Pipedrive requires a person, organization, or both.

Pipedrive troubleshooting

  • If lead creation fails, confirm person or organization ID is present.
  • If duplicate people appear, search by both email and phone before creating a person.
  • If custom fields are blank, confirm you used Pipedrive field keys, not visible labels.
  • If owner assignment fails, confirm the owner ID exists in the target account.
  • If notes do not appear, confirm the note is linked to the correct person, organization, lead, or deal.

Official references

These vendor-owned pages explain the controls and requirements referenced in this guide.

  • Pipedrive Leads APIOfficial documentation used to verify this setup path and its current vendor requirements.
  • Pipedrive persons APIOfficial documentation used to verify this setup path and its current vendor requirements.
  • Pipedrive organizations APIOfficial documentation used to verify this setup path and its current vendor requirements.