Salesforce flow - http callout to DocuSign

I have a working proof-of-concept that is executing a custom Apex class that makes the HttpCallout to DocuSign CLM API (using an External/Named Credential in Salesforce) but that’s it so far.

I can trigger a Flow which uses an Apex action to make a POST:https://apiuatna11.springcm.com/v2/[myAccountId]/folders/path?path=Other%20Sources\Salesforce\[myFolderName]&expand=Path,ParentFolder call and get a response then writes a log entry out to a custom logging object (I had to create the record within the Apex class itself to get around the “uncommited transaction” errors in the flow)

What I’d ultimately like to do is to write some automation to send/upload attachments (ContentDocuments) into CLM folders with a Salesforce Flow.  Any suggestions on making that next step?  I’m not a developer; more like a solutions designer trying to get a POC demo to work at this point.

I’d probably keep the Flow responsible for the business trigger and let Apex handle the parts that need more control over the HTTP request. The proof of concept mentioned here, using an External/Named Credential and an Apex action from Flow, seems like a sensible pattern, especially when authentication and callout handling start getting more involved.

For the attachment piece, I’d treat ContentDocument handling separately from the initial API call. First confirm the Flow can reliably identify the file and the target DocuSign/CLM folder, then handle the upload and logging as a separate step. That also makes troubleshooting much easier when something fails.

This is where call-flow design can make a difference beyond just the API connection. I’ve been looking at Salesforce Call Flow Management for a similar idea: keeping individual workflow decisions and actions clearly separated makes the overall Salesforce process easier to manage when it grows.