How to Resolve Pipedream App Not Configured Error While Accessing DocuSign Envelope Documents through Connect Proxy API?

Help
1

This topic was automatically generated from Slack. You can find the original thread here.

Hello! I am working on a project that uses the Pipedream trigger for when a DocuSign envelope is completed. I am trying to use the Pipedream Connect Proxy API to get the envelope documents from DocuSign. I am getting the following error: {"error"=>{"domain"=>["not allowed for this app"]}}. The problem is that the Pipedream app is not configured to allow the DocuSign REST API’s domains. For DocuSign Developer accounts, the API domain is demo.docusign.net. For DocuSign accounts, the API domain varies depending on the data center location, i.e. na2.docusign.net, na3.docusign.net, etc. Is there any known workaround for this? Is this on the team’s radar to fix?

2

Do you know how the relevant domain / data center is defined for a given account? I don’t see that configured in the integration from a quick glance, but it’s not a totally novel approach from other integrations. We should theoretically be able to support it. cc

3

Not sure if this answers your question but you can get the base_uri from the get user info endpoint User info endpoint reference | Docusign
You can currently call the get user info endpoint via a proxy request because that endpoint uses the domain [account-d.docusign.com](http://account-d.docusign.com) / [account.docusign.com](http://account.docusign.com).

4

Hey Haley, this should be working now — can you give it another try?

5

I can see that the docusign app was updated but I am only able to test with a docusign developer account. Would you be able to make the change to the docusign_developer app as well please?

6

I think the app would have to be set up similar to adobe_sign, which has:

 "connect"=>{"allowed_domains"=>["[api.na1.adobesign.com](http://api.na1.adobesign.com)", "[api.na2.adobesign.com](http://api.na2.adobesign.com)"], "base_proxy_target_url"=>"https://{{custom_fields.api_access_point}}api", "proxy_enabled"=>true}}}

docusign_developer app needs:
• allowed_domains: account-d.docusign.com, demo.docusign.net
• base_proxy_target_url: https://{{custom_fields.base_uri}}
docusign app needs:
• allowed_domains: account.docusign.com, and the list of domains here Docusign Support Center
• base_proxy_target_url: https://{{custom_fields.base_uri}}

7

Hey Haley, we should be be able to support this. I’ll look into making the update.

8
  • You’re all set now. Try again and it should work.