Configure Gyaan's Docsend Collateral integration

Created by Sunny Rai, Modified on Mon, 11 Jul, 2022 at 10:14 AM by Sunny Rai

Zapier lets you connect DocSend with thousands of the most popular apps, so you can automate your work and have more time for what matters most—no code required. Gyaan leverages this functionality to track the DocSend link visits by configuring Gyaan Webhook in Zapier. The below steps walk you through setting up DocSend and GyaanAI Integration via Zapier.

Setup Zapier to track Link Creation in DocSend

  1. Login to zapier.com
  2. Click on Create Zap and choose Docsend as an App event.
  3. Choose New Link Created as event and click on continue
  4. Choose New Link Created as event and click on continue.
  5. Choose your Docsend account. You might require to log in to Docsend at this step and click on continue
  6. Test the trigger by clicking on Test Trigger. This will load an example link from your Docsend account. Verify and click on continue
  7. This should open the Action Panel. Choose Webhooks by Zapier as an App event.
  8. Choose POST as the event and click on continue.
  9. Update URL, Headers, and Payload fields with the following fields
    1. URLhttps://api.app.gyaan.ai/api/v1/collateral/webhook
    2. Payload Type: json
    3. Update Data Fields
      1. doc_management_url: (Selection) Document Management Url
      2. link: (Selection) Link URL
      3. link_creator: (Selection) Link Creator
      4. name: (Selection) Document Name
      5. collateral_provider: docsend
      6. webhook_provider: zapier
      7. webhook_type: new_link_created
    4. Header
      1. X-Tenant-Gid: <YOUR-TENANT-GID-HERE>

  10. Once the data is filled up the form would look like
  11. Verify the information in the Test Action Panel and click on Test and Continue
  12. For a successful test, the Panel will show data as follows. Click on Publish Zap.
  13. You have successfully created a Zapier trigger for New Link Created.


Setup Zapier trigger for New Link Created

  1. Choose New visit as an event and click on continue.


  2. Choose your Docsend account (you might need to log in to Docsend at this step) and click on continue.
  3. Select YES or NO in the 100% completion field according to your requirements in Setup a trigger panel and click on continue.


  4. Click on Test Trigger in the Test Trigger panel



  5. This will load a test document visit from your docsend account, verify and click continue


  6. This should Open the Action Panel. Choose Webhooks by Zapier as an App event.

  7. Choose POST as the event and click on continue
  8. Update URL, Headers, and Payload fields with the following fields
    1. URLhttps://api.app.gyaan.ai/api/v1/collateral/webhook
    2. Payload Type: json
    3. Update Data Fields
      1. doc_management_url: (Selection) Document Management Url
      2. link: (Selection) Link URL
      3. name: (Selection) Document Name
      4. visit_time: (Selection) Visit Time
      5. visitor_email: (Selection) Visitor Email
      6. visitor_name: (Selection) Visitor Name
      7. collateral_provider: docsend
      8. webhook_provider: zapier
      9. webhook_type: new_link_created
    4. Header
      1. X-Tenant-Gid: <YOUR-TENANT-GID-HERE>

  9. Once the data is filled up the form would look like


 

  • Verify the information in Test Action Panel and Click on Test and Continue.

  • For a successful test, the panel should show data as following, Click on Publish Zap.

  • You have successfully created a zapier trigger For a New Visit to the Link.


Create a Docsend link

  • Click on the document for which the link needs to be created

  • Click on create link button and choose appropriate options for the link and click on
    “Create link” at the bottom of the form.

  • This should create a link and trigger the zapier zap for link creation and the result should be reflected in the app


  • Visiting the above-created link should trigger the zapier zap for someone visited the link and the result should be reflected in the app. 

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article