Appian Community and Appian Academy are being upgraded. As a part of the upgrade, Appian Community is currently in read-only mode, and user registration is disabled until August 3. We apologize for any inconvenience this may cause, but a more secure, stable, and performant Community experience is coming soon!

The new Appian Community launches August 3, followed by Appian Academy on August 7. During the migration, Appian Community Edition, Appian Academy, Documentation, Certifications, Instructor-led Customer Training, Partner Sales Training & Accreditation, and Forum (for Appian Partners and Customers only) will remain available.
  • State Suggested Answer
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 6 subscribers
  • Views 568 views
  • Users 0 members are here
Related Discussions
Home » Discussions » Integrations

Appian + DocuSign: Multi‑region setup using HTTP CS with dynamic accountId

devanshum749680
Our Appian application serves multiple geo regions (NA, EU, APAC). Each region uses a separate DocuSign account—and DocuSign’s REST endpoints require the accountId in the path (e.g., …/accounts/{accountId}/envelopes). We also need to route to the correct base URI for each account/region.

Goal: Make the integration scalable and configurable by:

  • Using an HTTP Connected System so we can manage auth/base URL centrally and pass accountId as a rule input in each Integration.
  • Dynamically selecting the correct base URI (per account/region) via DocuSign’s /oauth/userinfo (then cache it) or from the Apps & Keys page. \
  • Planning a future switch to JWT Grant so the integration runs with a service account (no interactive login), impersonating a user with consent. 

Is it possible to implement the solution. If yes what are the limitation?

  Discussion posts and replies are publicly visible

© 2026 Appian. All rights reserved.
We want to hear from you! Submit a review on Gartner or G2.