Integration reference

Pipedrive Trigger and Action reference

React to deal, person, organization, and activity changes and automate CRM records.

14 Triggers7 ActionsManifests: Trigger v1 · Action v1

Authentication

Authorize FastHook through Pipedrive OAuth. The integration requests access to deals, contacts, activities, and webhooks.

  • Trigger account type: oauth2; reconnect by oauth.
  • Action connection type: oauth2; available modes: Connected Pipedrive account.

Create or reuse the account from a Trigger or Action dialog, or manage it under Settings → Connected accounts. See Authentication and permissions for scopes and access diagnostics, or Connected accounts for reuse, reconnect, revocation, and credential rotation.

Scopes and permissions

Base Trigger authorization requests: base, deals:full, contacts:full, activities:full, webhooks:full.

Operation-specific requirements appear in the tables below. Custom event selections can add scopes dynamically, so the current Trigger or Action dialog remains authoritative for the exact consent request.

Use Pipedrive as a Trigger

The current provider manifest contains 14 available Trigger definitions. Representative definitions include:

  • Create Deal
  • Change Person
  • Delete Organization
  • Create Activity
View all 14 available Trigger definitions
TriggerManifest keyDeliveryAdditional scopes
Create Dealpipedrive.create_deal.instantinstantNone declared
Change Dealpipedrive.change_deal.instantinstantNone declared
Delete Dealpipedrive.delete_deal.instantinstantNone declared
Create Personpipedrive.create_person.instantinstantNone declared
Change Personpipedrive.change_person.instantinstantNone declared
Delete Personpipedrive.delete_person.instantinstantNone declared
Create Organizationpipedrive.create_organization.instantinstantNone declared
Change Organizationpipedrive.change_organization.instantinstantNone declared
Delete Organizationpipedrive.delete_organization.instantinstantNone declared
Create Activitypipedrive.create_activity.instantinstantNone declared
Change Activitypipedrive.change_activity.instantinstantNone declared
Delete Activitypipedrive.delete_activity.instantinstantNone declared
Any Pipedrive Eventspipedrive.any_event.instantinstantNone declared
Custom Pipedrive Eventspipedrive.custom_webhook_events.instantinstantNone declared

Choose the narrowest event definition that fits the Workflow. Configure provider-specific resource and event filters in the Source dialog before adding broader Workflow Filters.

Use Pipedrive Actions

The current Action manifest contains 7 operations. Representative Actions include:

  • Create Deal
  • Update Deal
  • Create Person
  • Create Activity
View all 7 available Action definitions
ActionManifest keyAccess and authManifest rate limit
Create Dealpipedrive.create_dealNone declared
FastHook-managed account
1/second
Update Dealpipedrive.update_dealNone declared
FastHook-managed account
1/second
Get Dealpipedrive.get_dealNone declared
FastHook-managed account
1/second
Create Personpipedrive.create_personNone declared
FastHook-managed account
1/second
Create Organizationpipedrive.create_organizationNone declared
FastHook-managed account
1/second
Create Activitypipedrive.create_activityNone declared
FastHook-managed account
1/second
Custom API Requestpipedrive.custom_api_requestNone declared
FastHook-managed account
1/second

The Action editor reads its required permissions, fields, remote resource pickers, output schema, and rate limit from the provider manifest. Available fields can change with the selected operation and authentication mode.

Build a Workflow

  1. Create a Source using a Pipedrive Trigger definition.
  2. Create a Workflow with that Source as its Trigger.
  3. Add the required Pipedrive Action and select the connected account.
  4. Map Trigger or earlier-Step data into the Action fields with the field picker.
  5. Add a Filter, Paths, Delay, or Transformation when the route needs it.
  6. Activate the Workflow, produce a controlled event, and verify the run in Audit and in Pipedrive.

Troubleshooting Pipedrive

The account is missing or cannot be selected
Confirm the active FastHook team, provider, account status, and authentication mode. A disabled or revoked account cannot execute an Action.
A resource picker is empty
Verify that the connected provider identity can access the resource itself. OAuth consent does not add workspace, repository, channel, drive, project, base, or record permissions.
The editor asks for additional scopes
Reconnect the same account from the affected Trigger or Action so FastHook can request its current manifest scopes. Then reopen the editor and select the resource again.
An active Workflow returns 401, 403, or a permission error
Compare the selected operation’s access requirements below with the account recorded in Audit. Check provider-side membership and object access before repeating the Action.
The provider returns 429 or a temporary 5xx
Inspect the Step attempt and retryability in Audit. FastHook can retry temporary failures, but provider quotas and idempotency rules still apply.

Provider-specific checks

  • The OAuth app is available through a direct installation flow; a Pipedrive Marketplace listing is not required.
  • Triggers use Webhooks v2; actions use the v2 CRM API. Deleted events contain the last state under previous, with data set to null.
  • Webhook delivery follows the connected user permissions. Use Get Deal when subsequent steps need the current full record.

Next