Appian + DocuSign: Multi‑region setup using HTTP CS with dynamic accountIdhttps://community.appian.com/discussions/f/integrations/40055/appian-docusign-multi-region-setup-using-http-cs-with-dynamic-accountidOur 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 correcten-USTelligent Community 12RE: Appian + DocuSign: Multi‑region setup using HTTP CS with dynamic accountIdhttps://community.appian.com/thread/152931?ContentTypeID=1Mon, 29 Dec 2025 20:33:06 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:4bab9f22-2f62-4136-aaf3-4d982e1034deJes&#250;s Hormigos<p>I would recommend you to create one connected system per region. Yes, you&#39;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&nbsp;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</p><div style="clear:both;"></div>