Blog

Instantly Generate Sales Contracts from Pipedrive

Blog

Instantly Generate Sales Contracts from Pipedrive

Blog

Instantly Generate Sales Contracts from Pipedrive

Blog

Instantly Generate Sales Contracts from Pipedrive

Blog

Instantly Generate Sales Contracts from Pipedrive

Download PDFDownload PDF
Blog

Instantly Generate Sales Contracts from Pipedrive

Formstack
/
August 13, 2015
Blog

Instantly Generate Sales Contracts from Pipedrive

MIN
/
August 13, 2015
About the Episode
Episode Highlights
Meet our Guest
Episode Transcript

We’ve all been there before. You finally go the “yes” and now it’s time to draw up the contracts and close the deal. So you open up your most recent contract, take out all the info specific to the last deal and replace it with this deal’s info. Yuck!

Did you ever played the game “Telephone” as a child? If you did, you’ll know that over time those contracts are going to be (drastically) different from how they started. That could be very costly to your business – especially if you have a team of sales reps all using their own versions of the contract.

You need a better way to manage your contracts and ensure everything goes according to plan. You need WebMerge! With WebMerge you can have every sales person use the exact same contract template every time and streamline the entire process.

In this example, we’re going to show you how you can automatically generate sales contracts when we update a Deal in Pipedrive to “Won”.This will all happen without the sales person having to search for a template, copy & paste the data, and then send it out for signature!

Let’s get started by setting up our contract in WebMerge. With WebMerge you have the option to upload a PDF or Word document, but we’re just going to use the online document builder for this contract template. From the Documents page in WebMerge click the New Document button. Type in a name for the contract, then pick the Build Your Own document type on the next step.


Click Next Step and you’ll be taken to the Document Builder. Here’s where you’re going to build your template and add all of the merge fields (where you want the data to be populated). The merge fields are just text and they look like this: {$Name}, {$Company}, {$PhoneNumber}, etc. For now, you can use any merge field names that you’d like. We’ll map them to the Pipedrive fields later.

Here’s what our contract template looks like:


Since this is a contract and we need to collect signatures, we’re going to utilize the DocuSign delivery option that will automatically send out the contract for signature through DocuSign. With this in mind, we need to define where the signature needs to go in the contract by using DocuSign’s Anchor Tags.

This article describes the anchor tags in more detail, but all you need to do is enter this in your document and DocuSign will detect it and overlay the signature: \s1\


Once you have your template setup, go ahead and save the document and you’ll be taken to the Settings tab. From here you can change the type of document that is generated and even the name of the file that is generated when a contract is populated. We’re going to add the company name to the file name so that we can easily search for the contract.

We’re also going to turn on Debug Mode (turn on Test Mode and then check the box below it) so that we can see the data that’s coming from Pipedrive as well as turn on the Field Map (under Advanced Settings) so we can map those fields later.


If you’ve made any changes to the settings, make sure you save those changes. Next, we’re going to hop over to the Deliver tab. Since we need to collect a signature for this contract, we’re going to send the populated contract to DocuSign for easy signature.

On the Deliver tab, click the New Delivery button and then pick DocuSign. You’ll be asked to login to your DocuSign account and then you’ll see the DocuSign settings. The “Subject” is the subject of the email that the customer will receive and then you’ll need to define the signer.


After you’ve saved your DocuSign delivery, we’ve got one more piece to setup in WebMerge. We’re going to be leveraging Pipedrive’s webhooks feature that allows us to automatically send data to WebMerge when certain events happen inside Pipedrive.

In order to only generate the contract when we’ve updated a Deal to “Won”, we need to add a little logic within WebMerge. To do this, we’re going to use the Data Routing feature. From the Data Routes page, click New Data Route then name it something like “Sales Contract”.


On the next step, you’ll be asked to define the “rules” of the data route. These rules are documents that you want to generate in the data route process (you can add multiple documents). We’re just going to add a single document (our contract), but then we’re going to add logic so that the document only fires when the “status” is “won”.

Now, you’re going to see a more detailed explanation of the Pipedrive fields shortly, but for now you’ll just want to use this field: {$current.status}


Once you’ve added the logic, save the rules and then jump over to the Merge tab for the Data Route. On this page, you’re going to see a Merge URL. This is a unique URL for your Data Route and we’re going to use that as the notification URL inside Pipedrive. Go ahead and save (copy) that.


Jump into Pipedrive and then go to Settings. You’ll see a link for Webhooks, click that. On the webhooks page, click the New Webhook button, then enter the Merge URL and then for the Events box, you’re going to enter “updated.deal”


Save that notification and now you’re ready to send data to WebMerge so we can map those merge fields in your document to the Pipedrive fields. Go ahead and go to one of your test deals and mark it as “Won”.

Inside WebMerge, go to the Overview tab for your document and you should see a line under the Recent Merges table. In that table, there is a View Data button. Click that and you’re going to see all of the fields coming over from Pipedrive and if you click on the name of the field, it will give you the name of the merge field.


Time to map the fields! Open up the Field Map tab in a new tab so you can flip back and forth. For each of the fields you see in the Field Map, you need to put in the merge field code (something like {$current.org_name} or {$current.person_name}) for that corresponding field from the Pipedrive data.

Here’s what our Field Map looks like:


Congrats, you’re all done! Once you have all of those fields mapped, you can go back into Pipedrive and update another Deal as “Won” and you’ll generate a file with all the data in it. Then check your DocuSign account and you should have a contract waiting for signature.

Here’s what our merged contract looks like ready for signature in DocuSign:


Now that you’ve got this process setup, how much time will your sales team save by automatically generating contracts from Pipedrive? Many of our customers save over an hour on every deal! Can you think of other ways you can use WebMerge to simplify your paperwork process?

Blog

Instantly Generate Sales Contracts from Pipedrive

Blog

Instantly Generate Sales Contracts from Pipedrive

Get the Report

Great, thank ya!

You can now access the content.
Oops! Something went wrong while submitting the form.
Blog

Instantly Generate Sales Contracts from Pipedrive

Panelists
No items found.
Introduction
Introduction

Great, thank ya!

You can now access the content.
Download NowDownload Now
Oops! Something went wrong while submitting the form.

We’ve all been there before. You finally go the “yes” and now it’s time to draw up the contracts and close the deal. So you open up your most recent contract, take out all the info specific to the last deal and replace it with this deal’s info. Yuck!

Did you ever played the game “Telephone” as a child? If you did, you’ll know that over time those contracts are going to be (drastically) different from how they started. That could be very costly to your business – especially if you have a team of sales reps all using their own versions of the contract.

You need a better way to manage your contracts and ensure everything goes according to plan. You need WebMerge! With WebMerge you can have every sales person use the exact same contract template every time and streamline the entire process.

In this example, we’re going to show you how you can automatically generate sales contracts when we update a Deal in Pipedrive to “Won”.This will all happen without the sales person having to search for a template, copy & paste the data, and then send it out for signature!

Let’s get started by setting up our contract in WebMerge. With WebMerge you have the option to upload a PDF or Word document, but we’re just going to use the online document builder for this contract template. From the Documents page in WebMerge click the New Document button. Type in a name for the contract, then pick the Build Your Own document type on the next step.


Click Next Step and you’ll be taken to the Document Builder. Here’s where you’re going to build your template and add all of the merge fields (where you want the data to be populated). The merge fields are just text and they look like this: {$Name}, {$Company}, {$PhoneNumber}, etc. For now, you can use any merge field names that you’d like. We’ll map them to the Pipedrive fields later.

Here’s what our contract template looks like:


Since this is a contract and we need to collect signatures, we’re going to utilize the DocuSign delivery option that will automatically send out the contract for signature through DocuSign. With this in mind, we need to define where the signature needs to go in the contract by using DocuSign’s Anchor Tags.

This article describes the anchor tags in more detail, but all you need to do is enter this in your document and DocuSign will detect it and overlay the signature: \s1\


Once you have your template setup, go ahead and save the document and you’ll be taken to the Settings tab. From here you can change the type of document that is generated and even the name of the file that is generated when a contract is populated. We’re going to add the company name to the file name so that we can easily search for the contract.

We’re also going to turn on Debug Mode (turn on Test Mode and then check the box below it) so that we can see the data that’s coming from Pipedrive as well as turn on the Field Map (under Advanced Settings) so we can map those fields later.


If you’ve made any changes to the settings, make sure you save those changes. Next, we’re going to hop over to the Deliver tab. Since we need to collect a signature for this contract, we’re going to send the populated contract to DocuSign for easy signature.

On the Deliver tab, click the New Delivery button and then pick DocuSign. You’ll be asked to login to your DocuSign account and then you’ll see the DocuSign settings. The “Subject” is the subject of the email that the customer will receive and then you’ll need to define the signer.


After you’ve saved your DocuSign delivery, we’ve got one more piece to setup in WebMerge. We’re going to be leveraging Pipedrive’s webhooks feature that allows us to automatically send data to WebMerge when certain events happen inside Pipedrive.

In order to only generate the contract when we’ve updated a Deal to “Won”, we need to add a little logic within WebMerge. To do this, we’re going to use the Data Routing feature. From the Data Routes page, click New Data Route then name it something like “Sales Contract”.


On the next step, you’ll be asked to define the “rules” of the data route. These rules are documents that you want to generate in the data route process (you can add multiple documents). We’re just going to add a single document (our contract), but then we’re going to add logic so that the document only fires when the “status” is “won”.

Now, you’re going to see a more detailed explanation of the Pipedrive fields shortly, but for now you’ll just want to use this field: {$current.status}


Once you’ve added the logic, save the rules and then jump over to the Merge tab for the Data Route. On this page, you’re going to see a Merge URL. This is a unique URL for your Data Route and we’re going to use that as the notification URL inside Pipedrive. Go ahead and save (copy) that.


Jump into Pipedrive and then go to Settings. You’ll see a link for Webhooks, click that. On the webhooks page, click the New Webhook button, then enter the Merge URL and then for the Events box, you’re going to enter “updated.deal”


Save that notification and now you’re ready to send data to WebMerge so we can map those merge fields in your document to the Pipedrive fields. Go ahead and go to one of your test deals and mark it as “Won”.

Inside WebMerge, go to the Overview tab for your document and you should see a line under the Recent Merges table. In that table, there is a View Data button. Click that and you’re going to see all of the fields coming over from Pipedrive and if you click on the name of the field, it will give you the name of the merge field.


Time to map the fields! Open up the Field Map tab in a new tab so you can flip back and forth. For each of the fields you see in the Field Map, you need to put in the merge field code (something like {$current.org_name} or {$current.person_name}) for that corresponding field from the Pipedrive data.

Here’s what our Field Map looks like:


Congrats, you’re all done! Once you have all of those fields mapped, you can go back into Pipedrive and update another Deal as “Won” and you’ll generate a file with all the data in it. Then check your DocuSign account and you should have a contract waiting for signature.

Here’s what our merged contract looks like ready for signature in DocuSign:


Now that you’ve got this process setup, how much time will your sales team save by automatically generating contracts from Pipedrive? Many of our customers save over an hour on every deal! Can you think of other ways you can use WebMerge to simplify your paperwork process?

Panelists
No items found.
Infographic

Instantly Generate Sales Contracts from Pipedrive

Follow these steps to start instantly generating sales contracts based on information in your Pipedrive account.
Download InfographicDownload Infographic

We’ve all been there before. You finally go the “yes” and now it’s time to draw up the contracts and close the deal. So you open up your most recent contract, take out all the info specific to the last deal and replace it with this deal’s info. Yuck!

Did you ever played the game “Telephone” as a child? If you did, you’ll know that over time those contracts are going to be (drastically) different from how they started. That could be very costly to your business – especially if you have a team of sales reps all using their own versions of the contract.

You need a better way to manage your contracts and ensure everything goes according to plan. You need WebMerge! With WebMerge you can have every sales person use the exact same contract template every time and streamline the entire process.

In this example, we’re going to show you how you can automatically generate sales contracts when we update a Deal in Pipedrive to “Won”.This will all happen without the sales person having to search for a template, copy & paste the data, and then send it out for signature!

Let’s get started by setting up our contract in WebMerge. With WebMerge you have the option to upload a PDF or Word document, but we’re just going to use the online document builder for this contract template. From the Documents page in WebMerge click the New Document button. Type in a name for the contract, then pick the Build Your Own document type on the next step.


Click Next Step and you’ll be taken to the Document Builder. Here’s where you’re going to build your template and add all of the merge fields (where you want the data to be populated). The merge fields are just text and they look like this: {$Name}, {$Company}, {$PhoneNumber}, etc. For now, you can use any merge field names that you’d like. We’ll map them to the Pipedrive fields later.

Here’s what our contract template looks like:


Since this is a contract and we need to collect signatures, we’re going to utilize the DocuSign delivery option that will automatically send out the contract for signature through DocuSign. With this in mind, we need to define where the signature needs to go in the contract by using DocuSign’s Anchor Tags.

This article describes the anchor tags in more detail, but all you need to do is enter this in your document and DocuSign will detect it and overlay the signature: \s1\


Once you have your template setup, go ahead and save the document and you’ll be taken to the Settings tab. From here you can change the type of document that is generated and even the name of the file that is generated when a contract is populated. We’re going to add the company name to the file name so that we can easily search for the contract.

We’re also going to turn on Debug Mode (turn on Test Mode and then check the box below it) so that we can see the data that’s coming from Pipedrive as well as turn on the Field Map (under Advanced Settings) so we can map those fields later.


If you’ve made any changes to the settings, make sure you save those changes. Next, we’re going to hop over to the Deliver tab. Since we need to collect a signature for this contract, we’re going to send the populated contract to DocuSign for easy signature.

On the Deliver tab, click the New Delivery button and then pick DocuSign. You’ll be asked to login to your DocuSign account and then you’ll see the DocuSign settings. The “Subject” is the subject of the email that the customer will receive and then you’ll need to define the signer.


After you’ve saved your DocuSign delivery, we’ve got one more piece to setup in WebMerge. We’re going to be leveraging Pipedrive’s webhooks feature that allows us to automatically send data to WebMerge when certain events happen inside Pipedrive.

In order to only generate the contract when we’ve updated a Deal to “Won”, we need to add a little logic within WebMerge. To do this, we’re going to use the Data Routing feature. From the Data Routes page, click New Data Route then name it something like “Sales Contract”.


On the next step, you’ll be asked to define the “rules” of the data route. These rules are documents that you want to generate in the data route process (you can add multiple documents). We’re just going to add a single document (our contract), but then we’re going to add logic so that the document only fires when the “status” is “won”.

Now, you’re going to see a more detailed explanation of the Pipedrive fields shortly, but for now you’ll just want to use this field: {$current.status}


Once you’ve added the logic, save the rules and then jump over to the Merge tab for the Data Route. On this page, you’re going to see a Merge URL. This is a unique URL for your Data Route and we’re going to use that as the notification URL inside Pipedrive. Go ahead and save (copy) that.


Jump into Pipedrive and then go to Settings. You’ll see a link for Webhooks, click that. On the webhooks page, click the New Webhook button, then enter the Merge URL and then for the Events box, you’re going to enter “updated.deal”


Save that notification and now you’re ready to send data to WebMerge so we can map those merge fields in your document to the Pipedrive fields. Go ahead and go to one of your test deals and mark it as “Won”.

Inside WebMerge, go to the Overview tab for your document and you should see a line under the Recent Merges table. In that table, there is a View Data button. Click that and you’re going to see all of the fields coming over from Pipedrive and if you click on the name of the field, it will give you the name of the merge field.


Time to map the fields! Open up the Field Map tab in a new tab so you can flip back and forth. For each of the fields you see in the Field Map, you need to put in the merge field code (something like {$current.org_name} or {$current.person_name}) for that corresponding field from the Pipedrive data.

Here’s what our Field Map looks like:


Congrats, you’re all done! Once you have all of those fields mapped, you can go back into Pipedrive and update another Deal as “Won” and you’ll generate a file with all the data in it. Then check your DocuSign account and you should have a contract waiting for signature.

Here’s what our merged contract looks like ready for signature in DocuSign:


Now that you’ve got this process setup, how much time will your sales team save by automatically generating contracts from Pipedrive? Many of our customers save over an hour on every deal! Can you think of other ways you can use WebMerge to simplify your paperwork process?

We’ve all been there before. You finally go the “yes” and now it’s time to draw up the contracts and close the deal. So you open up your most recent contract, take out all the info specific to the last deal and replace it with this deal’s info. Yuck!

Did you ever played the game “Telephone” as a child? If you did, you’ll know that over time those contracts are going to be (drastically) different from how they started. That could be very costly to your business – especially if you have a team of sales reps all using their own versions of the contract.

You need a better way to manage your contracts and ensure everything goes according to plan. You need WebMerge! With WebMerge you can have every sales person use the exact same contract template every time and streamline the entire process.

In this example, we’re going to show you how you can automatically generate sales contracts when we update a Deal in Pipedrive to “Won”.This will all happen without the sales person having to search for a template, copy & paste the data, and then send it out for signature!

Let’s get started by setting up our contract in WebMerge. With WebMerge you have the option to upload a PDF or Word document, but we’re just going to use the online document builder for this contract template. From the Documents page in WebMerge click the New Document button. Type in a name for the contract, then pick the Build Your Own document type on the next step.


Click Next Step and you’ll be taken to the Document Builder. Here’s where you’re going to build your template and add all of the merge fields (where you want the data to be populated). The merge fields are just text and they look like this: {$Name}, {$Company}, {$PhoneNumber}, etc. For now, you can use any merge field names that you’d like. We’ll map them to the Pipedrive fields later.

Here’s what our contract template looks like:


Since this is a contract and we need to collect signatures, we’re going to utilize the DocuSign delivery option that will automatically send out the contract for signature through DocuSign. With this in mind, we need to define where the signature needs to go in the contract by using DocuSign’s Anchor Tags.

This article describes the anchor tags in more detail, but all you need to do is enter this in your document and DocuSign will detect it and overlay the signature: \s1\


Once you have your template setup, go ahead and save the document and you’ll be taken to the Settings tab. From here you can change the type of document that is generated and even the name of the file that is generated when a contract is populated. We’re going to add the company name to the file name so that we can easily search for the contract.

We’re also going to turn on Debug Mode (turn on Test Mode and then check the box below it) so that we can see the data that’s coming from Pipedrive as well as turn on the Field Map (under Advanced Settings) so we can map those fields later.


If you’ve made any changes to the settings, make sure you save those changes. Next, we’re going to hop over to the Deliver tab. Since we need to collect a signature for this contract, we’re going to send the populated contract to DocuSign for easy signature.

On the Deliver tab, click the New Delivery button and then pick DocuSign. You’ll be asked to login to your DocuSign account and then you’ll see the DocuSign settings. The “Subject” is the subject of the email that the customer will receive and then you’ll need to define the signer.


After you’ve saved your DocuSign delivery, we’ve got one more piece to setup in WebMerge. We’re going to be leveraging Pipedrive’s webhooks feature that allows us to automatically send data to WebMerge when certain events happen inside Pipedrive.

In order to only generate the contract when we’ve updated a Deal to “Won”, we need to add a little logic within WebMerge. To do this, we’re going to use the Data Routing feature. From the Data Routes page, click New Data Route then name it something like “Sales Contract”.


On the next step, you’ll be asked to define the “rules” of the data route. These rules are documents that you want to generate in the data route process (you can add multiple documents). We’re just going to add a single document (our contract), but then we’re going to add logic so that the document only fires when the “status” is “won”.

Now, you’re going to see a more detailed explanation of the Pipedrive fields shortly, but for now you’ll just want to use this field: {$current.status}


Once you’ve added the logic, save the rules and then jump over to the Merge tab for the Data Route. On this page, you’re going to see a Merge URL. This is a unique URL for your Data Route and we’re going to use that as the notification URL inside Pipedrive. Go ahead and save (copy) that.


Jump into Pipedrive and then go to Settings. You’ll see a link for Webhooks, click that. On the webhooks page, click the New Webhook button, then enter the Merge URL and then for the Events box, you’re going to enter “updated.deal”


Save that notification and now you’re ready to send data to WebMerge so we can map those merge fields in your document to the Pipedrive fields. Go ahead and go to one of your test deals and mark it as “Won”.

Inside WebMerge, go to the Overview tab for your document and you should see a line under the Recent Merges table. In that table, there is a View Data button. Click that and you’re going to see all of the fields coming over from Pipedrive and if you click on the name of the field, it will give you the name of the merge field.


Time to map the fields! Open up the Field Map tab in a new tab so you can flip back and forth. For each of the fields you see in the Field Map, you need to put in the merge field code (something like {$current.org_name} or {$current.person_name}) for that corresponding field from the Pipedrive data.

Here’s what our Field Map looks like:


Congrats, you’re all done! Once you have all of those fields mapped, you can go back into Pipedrive and update another Deal as “Won” and you’ll generate a file with all the data in it. Then check your DocuSign account and you should have a contract waiting for signature.

Here’s what our merged contract looks like ready for signature in DocuSign:


Now that you’ve got this process setup, how much time will your sales team save by automatically generating contracts from Pipedrive? Many of our customers save over an hour on every deal! Can you think of other ways you can use WebMerge to simplify your paperwork process?

Collecting payments with online forms is easy, but first, you have to choose the right payment gateway. Browse the providers in our gateway credit card processing comparison chart to find the best option for your business. Then sign up for Formstack Forms, customize your payment forms, and start collecting profits in minutes.

Online Payment Gateway Comparison Chart

NOTE: These amounts reflect the monthly subscription for the payment provider. Formstack does not charge a fee to integrate with any of our payment partners.

FEATURES
Authorize.Net
Bambora
Chargify
First Data
PayPal
PayPal Pro
PayPal Payflow
Stripe
WePay
ProPay
Monthly Fees
$25
$25
$149+
Contact First Data
$0
$25
$0-$25
$0
$0
$4
Transaction Fees
$2.9% + 30¢
$2.9% + 30¢
N/A
Contact First Data
$2.9% + 30¢
$2.9% + 30¢
10¢
$2.9% + 30¢
$2.9% + 30¢
$2.6% + 30¢
Countries
5
8
Based on payment gateway
50+
203
3
4
25
USA
USA
Currencies
11
2
23
140
25
23
25
135+
1
1
Card Types
6
13
Based on payment gateway
5
9
9
5
6
4
4
Limits
None
None
Based on payment gateway
None
$10,000
None
None
None
None
$500 per transaction
Form Payments
Recurring Billing
Mobile Payments
PSD2 Compliant

We’ve all been there before. You finally go the “yes” and now it’s time to draw up the contracts and close the deal. So you open up your most recent contract, take out all the info specific to the last deal and replace it with this deal’s info. Yuck!

Did you ever played the game “Telephone” as a child? If you did, you’ll know that over time those contracts are going to be (drastically) different from how they started. That could be very costly to your business – especially if you have a team of sales reps all using their own versions of the contract.

You need a better way to manage your contracts and ensure everything goes according to plan. You need WebMerge! With WebMerge you can have every sales person use the exact same contract template every time and streamline the entire process.

In this example, we’re going to show you how you can automatically generate sales contracts when we update a Deal in Pipedrive to “Won”.This will all happen without the sales person having to search for a template, copy & paste the data, and then send it out for signature!

Let’s get started by setting up our contract in WebMerge. With WebMerge you have the option to upload a PDF or Word document, but we’re just going to use the online document builder for this contract template. From the Documents page in WebMerge click the New Document button. Type in a name for the contract, then pick the Build Your Own document type on the next step.


Click Next Step and you’ll be taken to the Document Builder. Here’s where you’re going to build your template and add all of the merge fields (where you want the data to be populated). The merge fields are just text and they look like this: {$Name}, {$Company}, {$PhoneNumber}, etc. For now, you can use any merge field names that you’d like. We’ll map them to the Pipedrive fields later.

Here’s what our contract template looks like:


Since this is a contract and we need to collect signatures, we’re going to utilize the DocuSign delivery option that will automatically send out the contract for signature through DocuSign. With this in mind, we need to define where the signature needs to go in the contract by using DocuSign’s Anchor Tags.

This article describes the anchor tags in more detail, but all you need to do is enter this in your document and DocuSign will detect it and overlay the signature: \s1\


Once you have your template setup, go ahead and save the document and you’ll be taken to the Settings tab. From here you can change the type of document that is generated and even the name of the file that is generated when a contract is populated. We’re going to add the company name to the file name so that we can easily search for the contract.

We’re also going to turn on Debug Mode (turn on Test Mode and then check the box below it) so that we can see the data that’s coming from Pipedrive as well as turn on the Field Map (under Advanced Settings) so we can map those fields later.


If you’ve made any changes to the settings, make sure you save those changes. Next, we’re going to hop over to the Deliver tab. Since we need to collect a signature for this contract, we’re going to send the populated contract to DocuSign for easy signature.

On the Deliver tab, click the New Delivery button and then pick DocuSign. You’ll be asked to login to your DocuSign account and then you’ll see the DocuSign settings. The “Subject” is the subject of the email that the customer will receive and then you’ll need to define the signer.


After you’ve saved your DocuSign delivery, we’ve got one more piece to setup in WebMerge. We’re going to be leveraging Pipedrive’s webhooks feature that allows us to automatically send data to WebMerge when certain events happen inside Pipedrive.

In order to only generate the contract when we’ve updated a Deal to “Won”, we need to add a little logic within WebMerge. To do this, we’re going to use the Data Routing feature. From the Data Routes page, click New Data Route then name it something like “Sales Contract”.


On the next step, you’ll be asked to define the “rules” of the data route. These rules are documents that you want to generate in the data route process (you can add multiple documents). We’re just going to add a single document (our contract), but then we’re going to add logic so that the document only fires when the “status” is “won”.

Now, you’re going to see a more detailed explanation of the Pipedrive fields shortly, but for now you’ll just want to use this field: {$current.status}


Once you’ve added the logic, save the rules and then jump over to the Merge tab for the Data Route. On this page, you’re going to see a Merge URL. This is a unique URL for your Data Route and we’re going to use that as the notification URL inside Pipedrive. Go ahead and save (copy) that.


Jump into Pipedrive and then go to Settings. You’ll see a link for Webhooks, click that. On the webhooks page, click the New Webhook button, then enter the Merge URL and then for the Events box, you’re going to enter “updated.deal”


Save that notification and now you’re ready to send data to WebMerge so we can map those merge fields in your document to the Pipedrive fields. Go ahead and go to one of your test deals and mark it as “Won”.

Inside WebMerge, go to the Overview tab for your document and you should see a line under the Recent Merges table. In that table, there is a View Data button. Click that and you’re going to see all of the fields coming over from Pipedrive and if you click on the name of the field, it will give you the name of the merge field.


Time to map the fields! Open up the Field Map tab in a new tab so you can flip back and forth. For each of the fields you see in the Field Map, you need to put in the merge field code (something like {$current.org_name} or {$current.person_name}) for that corresponding field from the Pipedrive data.

Here’s what our Field Map looks like:


Congrats, you’re all done! Once you have all of those fields mapped, you can go back into Pipedrive and update another Deal as “Won” and you’ll generate a file with all the data in it. Then check your DocuSign account and you should have a contract waiting for signature.

Here’s what our merged contract looks like ready for signature in DocuSign:


Now that you’ve got this process setup, how much time will your sales team save by automatically generating contracts from Pipedrive? Many of our customers save over an hour on every deal! Can you think of other ways you can use WebMerge to simplify your paperwork process?

We’ve all been there before. You finally go the “yes” and now it’s time to draw up the contracts and close the deal. So you open up your most recent contract, take out all the info specific to the last deal and replace it with this deal’s info. Yuck!

Did you ever played the game “Telephone” as a child? If you did, you’ll know that over time those contracts are going to be (drastically) different from how they started. That could be very costly to your business – especially if you have a team of sales reps all using their own versions of the contract.

You need a better way to manage your contracts and ensure everything goes according to plan. You need WebMerge! With WebMerge you can have every sales person use the exact same contract template every time and streamline the entire process.

In this example, we’re going to show you how you can automatically generate sales contracts when we update a Deal in Pipedrive to “Won”.This will all happen without the sales person having to search for a template, copy & paste the data, and then send it out for signature!

Let’s get started by setting up our contract in WebMerge. With WebMerge you have the option to upload a PDF or Word document, but we’re just going to use the online document builder for this contract template. From the Documents page in WebMerge click the New Document button. Type in a name for the contract, then pick the Build Your Own document type on the next step.


Click Next Step and you’ll be taken to the Document Builder. Here’s where you’re going to build your template and add all of the merge fields (where you want the data to be populated). The merge fields are just text and they look like this: {$Name}, {$Company}, {$PhoneNumber}, etc. For now, you can use any merge field names that you’d like. We’ll map them to the Pipedrive fields later.

Here’s what our contract template looks like:


Since this is a contract and we need to collect signatures, we’re going to utilize the DocuSign delivery option that will automatically send out the contract for signature through DocuSign. With this in mind, we need to define where the signature needs to go in the contract by using DocuSign’s Anchor Tags.

This article describes the anchor tags in more detail, but all you need to do is enter this in your document and DocuSign will detect it and overlay the signature: \s1\


Once you have your template setup, go ahead and save the document and you’ll be taken to the Settings tab. From here you can change the type of document that is generated and even the name of the file that is generated when a contract is populated. We’re going to add the company name to the file name so that we can easily search for the contract.

We’re also going to turn on Debug Mode (turn on Test Mode and then check the box below it) so that we can see the data that’s coming from Pipedrive as well as turn on the Field Map (under Advanced Settings) so we can map those fields later.


If you’ve made any changes to the settings, make sure you save those changes. Next, we’re going to hop over to the Deliver tab. Since we need to collect a signature for this contract, we’re going to send the populated contract to DocuSign for easy signature.

On the Deliver tab, click the New Delivery button and then pick DocuSign. You’ll be asked to login to your DocuSign account and then you’ll see the DocuSign settings. The “Subject” is the subject of the email that the customer will receive and then you’ll need to define the signer.


After you’ve saved your DocuSign delivery, we’ve got one more piece to setup in WebMerge. We’re going to be leveraging Pipedrive’s webhooks feature that allows us to automatically send data to WebMerge when certain events happen inside Pipedrive.

In order to only generate the contract when we’ve updated a Deal to “Won”, we need to add a little logic within WebMerge. To do this, we’re going to use the Data Routing feature. From the Data Routes page, click New Data Route then name it something like “Sales Contract”.


On the next step, you’ll be asked to define the “rules” of the data route. These rules are documents that you want to generate in the data route process (you can add multiple documents). We’re just going to add a single document (our contract), but then we’re going to add logic so that the document only fires when the “status” is “won”.

Now, you’re going to see a more detailed explanation of the Pipedrive fields shortly, but for now you’ll just want to use this field: {$current.status}


Once you’ve added the logic, save the rules and then jump over to the Merge tab for the Data Route. On this page, you’re going to see a Merge URL. This is a unique URL for your Data Route and we’re going to use that as the notification URL inside Pipedrive. Go ahead and save (copy) that.


Jump into Pipedrive and then go to Settings. You’ll see a link for Webhooks, click that. On the webhooks page, click the New Webhook button, then enter the Merge URL and then for the Events box, you’re going to enter “updated.deal”


Save that notification and now you’re ready to send data to WebMerge so we can map those merge fields in your document to the Pipedrive fields. Go ahead and go to one of your test deals and mark it as “Won”.

Inside WebMerge, go to the Overview tab for your document and you should see a line under the Recent Merges table. In that table, there is a View Data button. Click that and you’re going to see all of the fields coming over from Pipedrive and if you click on the name of the field, it will give you the name of the merge field.


Time to map the fields! Open up the Field Map tab in a new tab so you can flip back and forth. For each of the fields you see in the Field Map, you need to put in the merge field code (something like {$current.org_name} or {$current.person_name}) for that corresponding field from the Pipedrive data.

Here’s what our Field Map looks like:


Congrats, you’re all done! Once you have all of those fields mapped, you can go back into Pipedrive and update another Deal as “Won” and you’ll generate a file with all the data in it. Then check your DocuSign account and you should have a contract waiting for signature.

Here’s what our merged contract looks like ready for signature in DocuSign:


Now that you’ve got this process setup, how much time will your sales team save by automatically generating contracts from Pipedrive? Many of our customers save over an hour on every deal! Can you think of other ways you can use WebMerge to simplify your paperwork process?

We’ve all been there before. You finally go the “yes” and now it’s time to draw up the contracts and close the deal. So you open up your most recent contract, take out all the info specific to the last deal and replace it with this deal’s info. Yuck!

Did you ever played the game “Telephone” as a child? If you did, you’ll know that over time those contracts are going to be (drastically) different from how they started. That could be very costly to your business – especially if you have a team of sales reps all using their own versions of the contract.

You need a better way to manage your contracts and ensure everything goes according to plan. You need WebMerge! With WebMerge you can have every sales person use the exact same contract template every time and streamline the entire process.

In this example, we’re going to show you how you can automatically generate sales contracts when we update a Deal in Pipedrive to “Won”.This will all happen without the sales person having to search for a template, copy & paste the data, and then send it out for signature!

Let’s get started by setting up our contract in WebMerge. With WebMerge you have the option to upload a PDF or Word document, but we’re just going to use the online document builder for this contract template. From the Documents page in WebMerge click the New Document button. Type in a name for the contract, then pick the Build Your Own document type on the next step.


Click Next Step and you’ll be taken to the Document Builder. Here’s where you’re going to build your template and add all of the merge fields (where you want the data to be populated). The merge fields are just text and they look like this: {$Name}, {$Company}, {$PhoneNumber}, etc. For now, you can use any merge field names that you’d like. We’ll map them to the Pipedrive fields later.

Here’s what our contract template looks like:


Since this is a contract and we need to collect signatures, we’re going to utilize the DocuSign delivery option that will automatically send out the contract for signature through DocuSign. With this in mind, we need to define where the signature needs to go in the contract by using DocuSign’s Anchor Tags.

This article describes the anchor tags in more detail, but all you need to do is enter this in your document and DocuSign will detect it and overlay the signature: \s1\


Once you have your template setup, go ahead and save the document and you’ll be taken to the Settings tab. From here you can change the type of document that is generated and even the name of the file that is generated when a contract is populated. We’re going to add the company name to the file name so that we can easily search for the contract.

We’re also going to turn on Debug Mode (turn on Test Mode and then check the box below it) so that we can see the data that’s coming from Pipedrive as well as turn on the Field Map (under Advanced Settings) so we can map those fields later.


If you’ve made any changes to the settings, make sure you save those changes. Next, we’re going to hop over to the Deliver tab. Since we need to collect a signature for this contract, we’re going to send the populated contract to DocuSign for easy signature.

On the Deliver tab, click the New Delivery button and then pick DocuSign. You’ll be asked to login to your DocuSign account and then you’ll see the DocuSign settings. The “Subject” is the subject of the email that the customer will receive and then you’ll need to define the signer.


After you’ve saved your DocuSign delivery, we’ve got one more piece to setup in WebMerge. We’re going to be leveraging Pipedrive’s webhooks feature that allows us to automatically send data to WebMerge when certain events happen inside Pipedrive.

In order to only generate the contract when we’ve updated a Deal to “Won”, we need to add a little logic within WebMerge. To do this, we’re going to use the Data Routing feature. From the Data Routes page, click New Data Route then name it something like “Sales Contract”.


On the next step, you’ll be asked to define the “rules” of the data route. These rules are documents that you want to generate in the data route process (you can add multiple documents). We’re just going to add a single document (our contract), but then we’re going to add logic so that the document only fires when the “status” is “won”.

Now, you’re going to see a more detailed explanation of the Pipedrive fields shortly, but for now you’ll just want to use this field: {$current.status}


Once you’ve added the logic, save the rules and then jump over to the Merge tab for the Data Route. On this page, you’re going to see a Merge URL. This is a unique URL for your Data Route and we’re going to use that as the notification URL inside Pipedrive. Go ahead and save (copy) that.


Jump into Pipedrive and then go to Settings. You’ll see a link for Webhooks, click that. On the webhooks page, click the New Webhook button, then enter the Merge URL and then for the Events box, you’re going to enter “updated.deal”


Save that notification and now you’re ready to send data to WebMerge so we can map those merge fields in your document to the Pipedrive fields. Go ahead and go to one of your test deals and mark it as “Won”.

Inside WebMerge, go to the Overview tab for your document and you should see a line under the Recent Merges table. In that table, there is a View Data button. Click that and you’re going to see all of the fields coming over from Pipedrive and if you click on the name of the field, it will give you the name of the merge field.


Time to map the fields! Open up the Field Map tab in a new tab so you can flip back and forth. For each of the fields you see in the Field Map, you need to put in the merge field code (something like {$current.org_name} or {$current.person_name}) for that corresponding field from the Pipedrive data.

Here’s what our Field Map looks like:


Congrats, you’re all done! Once you have all of those fields mapped, you can go back into Pipedrive and update another Deal as “Won” and you’ll generate a file with all the data in it. Then check your DocuSign account and you should have a contract waiting for signature.

Here’s what our merged contract looks like ready for signature in DocuSign:


Now that you’ve got this process setup, how much time will your sales team save by automatically generating contracts from Pipedrive? Many of our customers save over an hour on every deal! Can you think of other ways you can use WebMerge to simplify your paperwork process?

We’ve all been there before. You finally go the “yes” and now it’s time to draw up the contracts and close the deal. So you open up your most recent contract, take out all the info specific to the last deal and replace it with this deal’s info. Yuck!

Did you ever played the game “Telephone” as a child? If you did, you’ll know that over time those contracts are going to be (drastically) different from how they started. That could be very costly to your business – especially if you have a team of sales reps all using their own versions of the contract.

You need a better way to manage your contracts and ensure everything goes according to plan. You need WebMerge! With WebMerge you can have every sales person use the exact same contract template every time and streamline the entire process.

In this example, we’re going to show you how you can automatically generate sales contracts when we update a Deal in Pipedrive to “Won”.This will all happen without the sales person having to search for a template, copy & paste the data, and then send it out for signature!

Let’s get started by setting up our contract in WebMerge. With WebMerge you have the option to upload a PDF or Word document, but we’re just going to use the online document builder for this contract template. From the Documents page in WebMerge click the New Document button. Type in a name for the contract, then pick the Build Your Own document type on the next step.


Click Next Step and you’ll be taken to the Document Builder. Here’s where you’re going to build your template and add all of the merge fields (where you want the data to be populated). The merge fields are just text and they look like this: {$Name}, {$Company}, {$PhoneNumber}, etc. For now, you can use any merge field names that you’d like. We’ll map them to the Pipedrive fields later.

Here’s what our contract template looks like:


Since this is a contract and we need to collect signatures, we’re going to utilize the DocuSign delivery option that will automatically send out the contract for signature through DocuSign. With this in mind, we need to define where the signature needs to go in the contract by using DocuSign’s Anchor Tags.

This article describes the anchor tags in more detail, but all you need to do is enter this in your document and DocuSign will detect it and overlay the signature: \s1\


Once you have your template setup, go ahead and save the document and you’ll be taken to the Settings tab. From here you can change the type of document that is generated and even the name of the file that is generated when a contract is populated. We’re going to add the company name to the file name so that we can easily search for the contract.

We’re also going to turn on Debug Mode (turn on Test Mode and then check the box below it) so that we can see the data that’s coming from Pipedrive as well as turn on the Field Map (under Advanced Settings) so we can map those fields later.


If you’ve made any changes to the settings, make sure you save those changes. Next, we’re going to hop over to the Deliver tab. Since we need to collect a signature for this contract, we’re going to send the populated contract to DocuSign for easy signature.

On the Deliver tab, click the New Delivery button and then pick DocuSign. You’ll be asked to login to your DocuSign account and then you’ll see the DocuSign settings. The “Subject” is the subject of the email that the customer will receive and then you’ll need to define the signer.


After you’ve saved your DocuSign delivery, we’ve got one more piece to setup in WebMerge. We’re going to be leveraging Pipedrive’s webhooks feature that allows us to automatically send data to WebMerge when certain events happen inside Pipedrive.

In order to only generate the contract when we’ve updated a Deal to “Won”, we need to add a little logic within WebMerge. To do this, we’re going to use the Data Routing feature. From the Data Routes page, click New Data Route then name it something like “Sales Contract”.


On the next step, you’ll be asked to define the “rules” of the data route. These rules are documents that you want to generate in the data route process (you can add multiple documents). We’re just going to add a single document (our contract), but then we’re going to add logic so that the document only fires when the “status” is “won”.

Now, you’re going to see a more detailed explanation of the Pipedrive fields shortly, but for now you’ll just want to use this field: {$current.status}


Once you’ve added the logic, save the rules and then jump over to the Merge tab for the Data Route. On this page, you’re going to see a Merge URL. This is a unique URL for your Data Route and we’re going to use that as the notification URL inside Pipedrive. Go ahead and save (copy) that.


Jump into Pipedrive and then go to Settings. You’ll see a link for Webhooks, click that. On the webhooks page, click the New Webhook button, then enter the Merge URL and then for the Events box, you’re going to enter “updated.deal”


Save that notification and now you’re ready to send data to WebMerge so we can map those merge fields in your document to the Pipedrive fields. Go ahead and go to one of your test deals and mark it as “Won”.

Inside WebMerge, go to the Overview tab for your document and you should see a line under the Recent Merges table. In that table, there is a View Data button. Click that and you’re going to see all of the fields coming over from Pipedrive and if you click on the name of the field, it will give you the name of the merge field.


Time to map the fields! Open up the Field Map tab in a new tab so you can flip back and forth. For each of the fields you see in the Field Map, you need to put in the merge field code (something like {$current.org_name} or {$current.person_name}) for that corresponding field from the Pipedrive data.

Here’s what our Field Map looks like:


Congrats, you’re all done! Once you have all of those fields mapped, you can go back into Pipedrive and update another Deal as “Won” and you’ll generate a file with all the data in it. Then check your DocuSign account and you should have a contract waiting for signature.

Here’s what our merged contract looks like ready for signature in DocuSign:


Now that you’ve got this process setup, how much time will your sales team save by automatically generating contracts from Pipedrive? Many of our customers save over an hour on every deal! Can you think of other ways you can use WebMerge to simplify your paperwork process?

We’ve all been there before. You finally go the “yes” and now it’s time to draw up the contracts and close the deal. So you open up your most recent contract, take out all the info specific to the last deal and replace it with this deal’s info. Yuck!

Did you ever played the game “Telephone” as a child? If you did, you’ll know that over time those contracts are going to be (drastically) different from how they started. That could be very costly to your business – especially if you have a team of sales reps all using their own versions of the contract.

You need a better way to manage your contracts and ensure everything goes according to plan. You need WebMerge! With WebMerge you can have every sales person use the exact same contract template every time and streamline the entire process.

In this example, we’re going to show you how you can automatically generate sales contracts when we update a Deal in Pipedrive to “Won”.This will all happen without the sales person having to search for a template, copy & paste the data, and then send it out for signature!

Let’s get started by setting up our contract in WebMerge. With WebMerge you have the option to upload a PDF or Word document, but we’re just going to use the online document builder for this contract template. From the Documents page in WebMerge click the New Document button. Type in a name for the contract, then pick the Build Your Own document type on the next step.


Click Next Step and you’ll be taken to the Document Builder. Here’s where you’re going to build your template and add all of the merge fields (where you want the data to be populated). The merge fields are just text and they look like this: {$Name}, {$Company}, {$PhoneNumber}, etc. For now, you can use any merge field names that you’d like. We’ll map them to the Pipedrive fields later.

Here’s what our contract template looks like:


Since this is a contract and we need to collect signatures, we’re going to utilize the DocuSign delivery option that will automatically send out the contract for signature through DocuSign. With this in mind, we need to define where the signature needs to go in the contract by using DocuSign’s Anchor Tags.

This article describes the anchor tags in more detail, but all you need to do is enter this in your document and DocuSign will detect it and overlay the signature: \s1\


Once you have your template setup, go ahead and save the document and you’ll be taken to the Settings tab. From here you can change the type of document that is generated and even the name of the file that is generated when a contract is populated. We’re going to add the company name to the file name so that we can easily search for the contract.

We’re also going to turn on Debug Mode (turn on Test Mode and then check the box below it) so that we can see the data that’s coming from Pipedrive as well as turn on the Field Map (under Advanced Settings) so we can map those fields later.


If you’ve made any changes to the settings, make sure you save those changes. Next, we’re going to hop over to the Deliver tab. Since we need to collect a signature for this contract, we’re going to send the populated contract to DocuSign for easy signature.

On the Deliver tab, click the New Delivery button and then pick DocuSign. You’ll be asked to login to your DocuSign account and then you’ll see the DocuSign settings. The “Subject” is the subject of the email that the customer will receive and then you’ll need to define the signer.


After you’ve saved your DocuSign delivery, we’ve got one more piece to setup in WebMerge. We’re going to be leveraging Pipedrive’s webhooks feature that allows us to automatically send data to WebMerge when certain events happen inside Pipedrive.

In order to only generate the contract when we’ve updated a Deal to “Won”, we need to add a little logic within WebMerge. To do this, we’re going to use the Data Routing feature. From the Data Routes page, click New Data Route then name it something like “Sales Contract”.


On the next step, you’ll be asked to define the “rules” of the data route. These rules are documents that you want to generate in the data route process (you can add multiple documents). We’re just going to add a single document (our contract), but then we’re going to add logic so that the document only fires when the “status” is “won”.

Now, you’re going to see a more detailed explanation of the Pipedrive fields shortly, but for now you’ll just want to use this field: {$current.status}


Once you’ve added the logic, save the rules and then jump over to the Merge tab for the Data Route. On this page, you’re going to see a Merge URL. This is a unique URL for your Data Route and we’re going to use that as the notification URL inside Pipedrive. Go ahead and save (copy) that.


Jump into Pipedrive and then go to Settings. You’ll see a link for Webhooks, click that. On the webhooks page, click the New Webhook button, then enter the Merge URL and then for the Events box, you’re going to enter “updated.deal”


Save that notification and now you’re ready to send data to WebMerge so we can map those merge fields in your document to the Pipedrive fields. Go ahead and go to one of your test deals and mark it as “Won”.

Inside WebMerge, go to the Overview tab for your document and you should see a line under the Recent Merges table. In that table, there is a View Data button. Click that and you’re going to see all of the fields coming over from Pipedrive and if you click on the name of the field, it will give you the name of the merge field.


Time to map the fields! Open up the Field Map tab in a new tab so you can flip back and forth. For each of the fields you see in the Field Map, you need to put in the merge field code (something like {$current.org_name} or {$current.person_name}) for that corresponding field from the Pipedrive data.

Here’s what our Field Map looks like:


Congrats, you’re all done! Once you have all of those fields mapped, you can go back into Pipedrive and update another Deal as “Won” and you’ll generate a file with all the data in it. Then check your DocuSign account and you should have a contract waiting for signature.

Here’s what our merged contract looks like ready for signature in DocuSign:


Now that you’ve got this process setup, how much time will your sales team save by automatically generating contracts from Pipedrive? Many of our customers save over an hour on every deal! Can you think of other ways you can use WebMerge to simplify your paperwork process?

Formstack
Formstack is a SaaS company with a mission to help organizations digitize what matters, automate workflows, and fix processes—all without code. A variety of team members come together to compile posts under Formstack's authorship.
More Articles
Meet The Host
CEO of
Connect
Chris is on a mission to turn people into great leaders. He's passionate about helping problem solvers see more value in the work they do every day.