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

Question

Our Appian application serves multiple geo regions (NA, EU, APAC). Each region uses a separate DocuSign account &mdash;and DocuSign&rsquo;s REST endpoints require the accountId in the path (e.g., &hellip;/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&rsquo;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?

Jesús Hormigos · Answer

I would recommend you to create one connected system per region. Yes, you'll have the same DocuSign integration several times (the only difference between them would be the connected system used) but at the end of the day it will be much easier to manage them in that way. In your process model you can define a rule to use the NA or EU integration