DocuSign to Pipedrive Integration

This Zap demonstrates an integration between DocuSign and Pipedrive. When a document is completed in DocuSign, the workflow automatically creates the appropriate records in Pipedrive and uploads the primary signed application along with any statements the client included.

AI is used in a key step to accurately separate the file URLs, ensuring each document is attached individually and mapped correctly within Pipedrive.

svg+xml;charset=utf

1. Trigger: Envelope Completed in DocuSign

The Zap begins when an envelope is marked as completed in DocuSign. 

2. Filter: Confirm the Correct Envelope Type

A filter step checks that the completed envelope matches the specific application type this workflow is designed for. 

3. Create Organization in Pipedrive

4. Create Person in Pipedrive

5. Create Deal in Pipedrive

6. AI Step: Separate Document URLs

DocuSign returns the signed document links as a single string of URLs. The built-in Zapier formatter module was not reliably separating them, so an AI step is used to analyze the string and split it into individual URLs.

This allows each document—Statement 1, Statement 2, Statement 3, and the Application—to be handled separately in the next steps.

7. Paths: Route Each Document

The Zap uses Paths to determine which documents are present and where they should be uploaded. Each document type is handled individually:

  • Statement 1
  • Statement 2
  • Statement 3
  • Application

This ensures each file is stored properly and clearly labeled inside Pipedrive.

Result

Once the envelope is completed, the entire record structure—Organization, Person, Deal, and all associated signed documents—is automatically created and organized in Pipedrive.

This screenshot highlights one focused aspect of the broader integration: using automation (and a small AI assist) to move finalized DocuSign agreements directly into a structured Pipedrive workflow without manual data entry.