Use the Pipedrive Activities API to bulk-create follow-up activities tied to deals, filtering by deal stage and owner, and handle the per-user rate limit
GET /api/v1/deals with filter_id or status/stage_id query params to retrieve the set of target deals, paginating with start and limit params
For each deal, POST /api/v1/activities with a body containing 'deal_id', 'user_id' (owner), 'type', 'due_date', 'due_time', and 'subject' to create the activity
Inspect the response 'success' boolean and 'data' object; on failure parse the 'error' and 'error_info' fields to determine the cause
Track the X-RateLimit-Remaining and X-RateLimit-Reset headers on each response and back off when remaining approaches zero
Use the Pipedrive Recents endpoint GET /api/v1/recents?items=activity to verify recently created activities appear in the audit trail
Known gotchas
Pipedrive rate limits are per-API-token, not per-IP; if multiple integration services share the same token their requests pool against the same limit, causing unexpected throttling
The 'user_id' on a created activity must correspond to a user who has access to the deal; assigning an activity to a user outside the deal's visibility scope creates the activity but it may not appear in that user's calendar view
Pipedrive does not provide a bulk activity creation endpoint; each activity requires an individual POST, making large backfills slow and rate-limit-sensitive
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp