Workflow Builder API

Hi everyone,I'm facing a strange issue with DocuSign Demo connector in Power Automate.Everything was working perfectly fine, and suddenly, without any changes on my end, I'm getting this error when trying to send an envelope:❌ RECIPIENT_LIMIT_EXCEEDED - "You have reached the maximum number of recipients permitted for a single transaction in your account."The weird part is that my template only has 2 recipients:- 1 signer (Responsable)- 1 receives a copy (Demandeur)I ran the exact same flow twice within the same hour. The first run at 13:12 succeeded (status 200), and the second run at 13:57 failed with this error — same template, same configuration, nothing changed.I've already checked:✅ Admin settings → no recipient limit configured✅ Sending Settings → no restriction found✅ Monthly envelope usage → 26 envelopes, limit is UnlimitedHas anyone experienced this issue? Could it be a temporary throttling on Demo accounts after sending many test envelopes in one day?Any help would be appreci

Hi,I need help to figure out how to automate the process of uploading all completed envelopes (pdfs) into Google drive as soon as they are completed? So as I understand first step(start) of the workflow will be Event -  Completed envelope. Btw, I don’t need all the envelopes, just from certain templates. Would appreciate any tips on thatThank you

I’m working with DocuSign Workflow Builder (formerly Maestro) Designer and need to get the value of a webform field/description that was filled in during a workflow run. Specifically, I want to retrieve the field values via the WorkflowInstanceManagement: getWorkflowInstance API.Currently, I have access to: accountId workflowId instanceId But when I call getWorkflowInstance, I only see general instance metadata and status details. I don’t see how to extract the actual webform responses that were submitted.

Hello everyone,We’re currently working on passing values from our website into a DocuSign Workflow Builder (formerly Maestro) webform via API trigger_inputs, and while we’ve had success with text fields and date fields, we’re running into challenges with other field types.Specifically, we want to pre-select a radio button option so that when the webform loads, the correct option is already chosen. For example: Gender field (radio buttons): Options are Male, Female, Others. We’d like to pre-select Male. We suspect this challenge may apply similarly to dropdowns, checkboxes, and phone number fields as well.Has anyone implemented this successfully? Could you please share examples of the correct variable types or payload structure required to map these field types (radio buttons, checkboxes, dropdowns, phone)?I’ve attached screenshots for reference. Any guidance or working examples would be greatly appreciated!Thanks in advance.

Hello — I’m working with a DocuSign Workflow Builder (formerly Maestro) template where I’d like a signer to enter a “whole dollar” value (e.g., 100) and have it automatically display or format as currency (e.g., $100.00).In the template designer, using a Currency / Number field works perfectly when setup so the signer enters the value manually on the contract. However, when that same field is prefilled via a Web Form and Workflow Builder (formerly Maestro) Workflow, the formatting (dollar sign, decimal places) doesn’t carry through — it just outputs the raw number.I’m trying to determine if there’s a way to apply or trigger that formatting on prefilled values.The only workaround I’ve found so far is hard-coding the “$” before the field and “.00” after it, leaving space for the user to type the number — but that feels like a fragile solution.Has anyone found a cleaner approach? Can a Web Form / Workflow Builder (formerly Maestro) prefill override or trigger the formatting rules of a cur

Hello,I’ve been working in Workflow Builder (formerly Maestro) Workflows using webforms to build them out. The goal being so that the webforms speak with the workflow so that people on my team can use a link to send out and fill out contracts versus needing to sign into DocuSign. Currently I have set up all my webforms reflected off my contract templates, and then I built out my workflows reflecting the needs of my departments and the flow of my contracts. For example Department X needs 4 types of contracts and so they branch out in different ways. Here’s an example of what a workflow would look like:LinkWebformBranching question 1: Are they A or B?A:Are they B or C? → contracts 1 & 2 B: Are they D or E? → contracts 3 & 4Right now when I test the webform it works perfectly but the branching question 1 is always leading to option B, even though I select all the options for option A. So I’m always getting the wrong contract as a result. When I check my Instances it looks like thi

Hi all,I’m using a JWT Grant flow in PHP (RS256).The token works perfectly against the sandbox endpoint:https://demo.docusign.net/restapi/v2.1/accounts But when I send the exact same JWT to the Workflow Builder (formerly Maestro) (developer) endpoint:https://api-d.docusign.com/v1/accounts DocuSign returns:“Jwt payload is an invalid JSON”Does anyone know why the payload is accepted in demo but rejected in Workflow Builder (formerly Maestro)/API-D?What’s different ?Thanks in advance for any help 🙏

I have a use case below. What do you advise in regards to the best workflow. Im particularly interested in when to use Webform and Powerform in this case.Use Case:I want the below to be the beginning of a Workflow Builder (formerly Maestro) workflow, automating a full contract lifecycle:David completes a form via a shared link and uploads three attachments within the completion. The form data auto-populates a contract template. The contract is then routed to John (internal user), who completes the remaining fields not included in the original form. David’s is able to see all the entries inputted by David, and ideally can edit them, and receives the attachments. Once John finishes the form, the fully completed contract triggers the generation of: An Executive Summary (static template) A Business Terms Summary (static template) One of four Contract Agreements (all dynamic templates with conditional content). As to which one is populated, this depends on which entity is indicated in the

Hi All,I am implementing Workflow Builder (formerly Maestro) Workflow and it throws errors for various reasons, but error descriptions are not developer friendly to fix those errors easily. For e,g mentioned below error { "name": "Execute_eSign_Scope_47ac200c-b553-4ad9-a1bc-d55afa5d28b4", "startTime": "2025-06-06T19:30:13.7287018Z", "endTime": "2025-06-06T19:30:15.4834359Z", "code": "BadRequest", "status": "Failed", "apiError": { "message": "Error creating envelope for the Esign scope", "internalErrorCode": "ERR_10999", "internalTraceId": "047e235f919f7c23850e780df4eb6b0b", "apiError": "{\"errorCode\":\"UNSPECIFIED_ERROR\",\"message\":\"Object reference not set to an instance of an object.\"}" -- This error does not tell me what is missing to pass into workflow for e.g. whether I am missing to pass any recipient details, or mandatory fields info, then what mandatory field is throwing this error. Without knowing exact errors, it is very difficult to fix quickly, it bec

Hey DocuSign Community!I'm developing a file archive extension and see that the Google Drive and Dropbox extensions in the App Center allow users to select specific storage locations (folders/drives) during the Workflow Builder (formerly Maestro) workflow configuration. (see screenshots) However, looking at the File Archive Extension documentation and reference implementation, I don't see how to implement this functionality. The action definition only shows a single URI parameter: "params": {"uri": "https://example.app/api/archive"}Any guidance on what needs to happen in the file archive extension to allow users to select storage locations would be great. Thanks in advance!   

Salesforce fields are not being displayed in Workflow Builder (formerly Maestro) WorkflowsHow can I add them?

We’re trying to trigger a workflow using the Workflow Builder (formerly Maestro) API in our app. We’re following the documentation on DocuSign website. We started with the documentation on How to trigger a Workflow Builder (formerly Maestro) workflow. Here, we:Are able to the authentication token Are able to construct your API headersThe problem starts with step 3 onwards. We couldn’t retrieve the triggerURL using the server code, however we can get the workflow definitions using the getWorkflowDefinitions API reference. Then we tried to trigger the workflow using the triggerWorkflow API reference, and we ran into errors. We used the following payload: { "instanceName": "New Docusign Instance", "payload": { "abcEmail": "abc@example.com", "abcName": "ABC", "xyzEmail": "xyz@example.com", "xyzName": "XYZ", "xyzCode": "IN11" }} Please let me know of any extra details you require

Can we combine the Workflow Builder (formerly Maestro) Low Code Workflow Designer with the Workflow Builder (formerly Maestro) APIs when creating and managing Workflow Builder (formerly Maestro) Workflows?

What does it mean if Workflow Builder (formerly Maestro) APIs are under Beta?

Will Workflow Builder (formerly Maestro) APIs used in my applications during the Beta phase be available in the Docusign production environment?

What can you do using Workflow Builder (formerly Maestro) API?

How do I gain access to the Workflow Builder (formerly Maestro) APIs during Beta?