@keystrokehq/docusign 0.0.16-integration-id-canonicalization.1 → 0.1.0

package/dist/actions/add-email-overrides-to-envelope.cjs

@@ -0,0 +1,33 @@
+const require_action = require("../action.cjs");
+let zod = require("zod");
+//#region src/actions/add-email-overrides-to-envelope.ts
+const DocusignAddEmailOverridesToEnvelopeInput = zod.z.object({
+	accountId: zod.z.string().describe("The unique identifier for the DocuSign account. This can be either the account number (integer) or the account ID GUID. It is required to specify which account the envelope belongs to. Format: string.").optional(),
+	envelopeId: zod.z.string().describe("The unique identifier for the specific envelope to which the email settings will be applied. This is a GUID (Globally Unique Identifier) that uniquely identifies the envelope within the DocuSign system. Format: string. Example: \"93be49ab-xxxx-xxxx-xxxx-f752070d71ec\"."),
+	bccEmailAddresses: zod.z.array(zod.z.object({
+		email: zod.z.string().describe("Specifies the BCC email address. DocuSign verifies that the email format is correct, but does not verify that the email is active. Using this overrides the BCC for Email Archive information setting for this envelope. Maximum length: 100 characters.").optional(),
+		bccEmailAddressId: zod.z.string().describe("Unique identifier for the BCC email address entry. This is typically assigned by DocuSign when a BCC email address is added to the account settings. Optional field used to reference specific BCC configuration.").optional()
+	}).describe("Request schema for `BccEmailAddresses`")).describe("An array containing the email address that should receive a copy of all email communications related to an envelope for archiving purposes. Maximum Length: 100 characters. While this property is an array, note that it takes only a single email address. **Note:** Only users with the `canManageAccount` setting set to **true** can use this option.  Docusign verifies that the email format is correct, but does not verify that the email address is active. You can use this for archiving purposes. However, using this property overrides the BCC for Email Archive information setting for this envelope.  **Example:** if your account has BCC for Email Archive set up for the email address archive@mycompany.com and you send an envelope using the BCC Email Override to send a BCC email to salesarchive@mycompany.com, then a copy of the envelope is only sent to the salesarchive@mycompany.com email address.").optional(),
+	replyEmailNameOverride: zod.z.string().describe("The name to associate with the Reply To email address, instead of the name that is configured at the account level. Maximum Length: 100 characters.").optional(),
+	replyEmailAddressOverride: zod.z.string().describe("The Reply To email address to use for email replies, instead of the one that is configured at the account level. Docusign verifies that the email address is in a correct format, but does not verify that it is active. Maximum Length: 100 characters.").optional()
+}).describe("Request schema for `AddEmailOverridesToEnvelope`");
+const DocusignAddEmailOverridesToEnvelope_BccEmailAddressesResponseSchema = zod.z.object({
+	email: zod.z.string().describe("The BCC email address").nullable().optional(),
+	bccEmailAddressId: zod.z.string().describe("Unique identifier for the BCC email address entry").nullable().optional()
+}).describe("Response schema for BCC email address");
+const DocusignAddEmailOverridesToEnvelopeOutput = zod.z.object({
+	bccEmailAddresses: zod.z.array(DocusignAddEmailOverridesToEnvelope_BccEmailAddressesResponseSchema).describe("Array of BCC email addresses configured for the envelope").nullable().optional(),
+	replyEmailNameOverride: zod.z.string().describe("The Reply To name override for the envelope").nullable().optional(),
+	replyEmailAddressOverride: zod.z.string().describe("The Reply To email address override for the envelope").nullable().optional()
+}).describe("Response schema for `AddEmailOverridesToEnvelope`");
+const docusignAddEmailOverridesToEnvelope = require_action.action("DOCUSIGN_ADD_EMAIL_OVERRIDES_TO_ENVELOPE", {
+	slug: "docusign-add-email-overrides-to-envelope",
+	name: "Add Email Overrides To Envelope",
+	description: "Adds or modifies email override settings for a specific DocuSign envelope, allowing customization of the reply-to email address and name, as well as BCC email addresses for archiving purposes. This endpoint should be used when you need to change email settings for an individual envelope, overriding the account-level configurations. It's particularly useful for setting up specialized archiving or customizing the reply-to information for specific envelopes. Note that these changes only affect email communications that occur after the addition is made, and the BCC feature is limited to users with appropriate permissions. For security reasons, additional signer authentication is recommended when using the BCC for Email Archive feature.",
+	input: DocusignAddEmailOverridesToEnvelopeInput,
+	output: DocusignAddEmailOverridesToEnvelopeOutput
+});
+//#endregion
+exports.docusignAddEmailOverridesToEnvelope = docusignAddEmailOverridesToEnvelope;
+
+//# sourceMappingURL=add-email-overrides-to-envelope.cjs.map

package/dist/actions/add-email-overrides-to-envelope.cjs.map

@@ -0,0 +1 @@
+{"version":3,"file":"add-email-overrides-to-envelope.cjs","names":["z","action"],"sources":["../../src/actions/add-email-overrides-to-envelope.ts"],"sourcesContent":["import { z } from \"zod\";\n\nimport { action } from \"../action\";\n\nexport const DocusignAddEmailOverridesToEnvelopeInput: z.ZodTypeAny = z.object({\n  accountId: z.string().describe(\"The unique identifier for the DocuSign account. This can be either the account number (integer) or the account ID GUID. It is required to specify which account the envelope belongs to. Format: string.\").optional(),\n  envelopeId: z.string().describe(\"The unique identifier for the specific envelope to which the email settings will be applied. This is a GUID (Globally Unique Identifier) that uniquely identifies the envelope within the DocuSign system. Format: string. Example: \\\"93be49ab-xxxx-xxxx-xxxx-f752070d71ec\\\".\"),\n  bccEmailAddresses: z.array(z.object({\n  email: z.string().describe(\"Specifies the BCC email address. DocuSign verifies that the email format is correct, but does not verify that the email is active. Using this overrides the BCC for Email Archive information setting for this envelope. Maximum length: 100 characters.\").optional(),\n  bccEmailAddressId: z.string().describe(\"Unique identifier for the BCC email address entry. This is typically assigned by DocuSign when a BCC email address is added to the account settings. Optional field used to reference specific BCC configuration.\").optional(),\n}).describe(\"Request schema for `BccEmailAddresses`\")).describe(\"An array containing the email address that should receive a copy of all email communications related to an envelope for archiving purposes. Maximum Length: 100 characters. While this property is an array, note that it takes only a single email address. **Note:** Only users with the `canManageAccount` setting set to **true** can use this option.  Docusign verifies that the email format is correct, but does not verify that the email address is active. You can use this for archiving purposes. However, using this property overrides the BCC for Email Archive information setting for this envelope.  **Example:** if your account has BCC for Email Archive set up for the email address archive@mycompany.com and you send an envelope using the BCC Email Override to send a BCC email to salesarchive@mycompany.com, then a copy of the envelope is only sent to the salesarchive@mycompany.com email address.\").optional(),\n  replyEmailNameOverride: z.string().describe(\"The name to associate with the Reply To email address, instead of the name that is configured at the account level. Maximum Length: 100 characters.\").optional(),\n  replyEmailAddressOverride: z.string().describe(\"The Reply To email address to use for email replies, instead of the one that is configured at the account level. Docusign verifies that the email address is in a correct format, but does not verify that it is active. Maximum Length: 100 characters.\").optional(),\n}).describe(\"Request schema for `AddEmailOverridesToEnvelope`\");\nconst DocusignAddEmailOverridesToEnvelope_BccEmailAddressesResponseSchema: z.ZodTypeAny = z.object({\n  email: z.string().describe(\"The BCC email address\").nullable().optional(),\n  bccEmailAddressId: z.string().describe(\"Unique identifier for the BCC email address entry\").nullable().optional(),\n}).describe(\"Response schema for BCC email address\");\nexport const DocusignAddEmailOverridesToEnvelopeOutput: z.ZodTypeAny = z.object({\n  bccEmailAddresses: z.array(DocusignAddEmailOverridesToEnvelope_BccEmailAddressesResponseSchema).describe(\"Array of BCC email addresses configured for the envelope\").nullable().optional(),\n  replyEmailNameOverride: z.string().describe(\"The Reply To name override for the envelope\").nullable().optional(),\n  replyEmailAddressOverride: z.string().describe(\"The Reply To email address override for the envelope\").nullable().optional(),\n}).describe(\"Response schema for `AddEmailOverridesToEnvelope`\");\n\nexport const docusignAddEmailOverridesToEnvelope = action(\"DOCUSIGN_ADD_EMAIL_OVERRIDES_TO_ENVELOPE\", {\n  slug: \"docusign-add-email-overrides-to-envelope\",\n  name: \"Add Email Overrides To Envelope\",\n  description: \"Adds or modifies email override settings for a specific DocuSign envelope, allowing customization of the reply-to email address and name, as well as BCC email addresses for archiving purposes. This endpoint should be used when you need to change email settings for an individual envelope, overriding the account-level configurations. It's particularly useful for setting up specialized archiving or customizing the reply-to information for specific envelopes. Note that these changes only affect email communications that occur after the addition is made, and the BCC feature is limited to users with appropriate permissions. For security reasons, additional signer authentication is recommended when using the BCC for Email Archive feature.\",\n  input: DocusignAddEmailOverridesToEnvelopeInput,\n  output: DocusignAddEmailOverridesToEnvelopeOutput,\n});\n"],"mappings":";;;AAIA,MAAa,2CAAyDA,IAAAA,EAAE,OAAO;CAC7E,WAAWA,IAAAA,EAAE,OAAO,CAAC,CAAC,SAAS,0MAA0M,CAAC,CAAC,SAAS;CACpP,YAAYA,IAAAA,EAAE,OAAO,CAAC,CAAC,SAAS,+QAA+Q;CAC/S,mBAAmBA,IAAAA,EAAE,MAAMA,IAAAA,EAAE,OAAO;EACpC,OAAOA,IAAAA,EAAE,OAAO,CAAC,CAAC,SAAS,0PAA0P,CAAC,CAAC,SAAS;EAChS,mBAAmBA,IAAAA,EAAE,OAAO,CAAC,CAAC,SAAS,mNAAmN,CAAC,CAAC,SAAS;CACvQ,CAAC,CAAC,CAAC,SAAS,wCAAwC,CAAC,CAAC,CAAC,SAAS,s4BAAs4B,CAAC,CAAC,SAAS;CAC/8B,wBAAwBA,IAAAA,EAAE,OAAO,CAAC,CAAC,SAAS,qJAAqJ,CAAC,CAAC,SAAS;CAC5M,2BAA2BA,IAAAA,EAAE,OAAO,CAAC,CAAC,SAAS,0PAA0P,CAAC,CAAC,SAAS;AACtT,CAAC,CAAC,CAAC,SAAS,kDAAkD;AAC9D,MAAM,sEAAoFA,IAAAA,EAAE,OAAO;CACjG,OAAOA,IAAAA,EAAE,OAAO,CAAC,CAAC,SAAS,uBAAuB,CAAC,CAAC,SAAS,CAAC,CAAC,SAAS;CACxE,mBAAmBA,IAAAA,EAAE,OAAO,CAAC,CAAC,SAAS,mDAAmD,CAAC,CAAC,SAAS,CAAC,CAAC,SAAS;AAClH,CAAC,CAAC,CAAC,SAAS,uCAAuC;AACnD,MAAa,4CAA0DA,IAAAA,EAAE,OAAO;CAC9E,mBAAmBA,IAAAA,EAAE,MAAM,mEAAmE,CAAC,CAAC,SAAS,0DAA0D,CAAC,CAAC,SAAS,CAAC,CAAC,SAAS;CACzL,wBAAwBA,IAAAA,EAAE,OAAO,CAAC,CAAC,SAAS,6CAA6C,CAAC,CAAC,SAAS,CAAC,CAAC,SAAS;CAC/G,2BAA2BA,IAAAA,EAAE,OAAO,CAAC,CAAC,SAAS,sDAAsD,CAAC,CAAC,SAAS,CAAC,CAAC,SAAS;AAC7H,CAAC,CAAC,CAAC,SAAS,mDAAmD;AAE/D,MAAa,sCAAsCC,eAAAA,OAAO,4CAA4C;CACpG,MAAM;CACN,MAAM;CACN,aAAa;CACb,OAAO;CACP,QAAQ;AACV,CAAC"}

package/dist/actions/add-email-overrides-to-envelope.d.cts

@@ -0,0 +1,9 @@
+import { z } from "zod";
+
+//#region src/actions/add-email-overrides-to-envelope.d.ts
+declare const DocusignAddEmailOverridesToEnvelopeInput: z.ZodTypeAny;
+declare const DocusignAddEmailOverridesToEnvelopeOutput: z.ZodTypeAny;
+declare const docusignAddEmailOverridesToEnvelope: import("@keystrokehq/action").WorkflowActionDefinition<unknown, unknown, import("@keystrokehq/shared").ResolvedCredentials<readonly [import("@keystrokehq/shared").Credential]>, readonly [import("@keystrokehq/shared").Credential]>;
+//#endregion
+export { docusignAddEmailOverridesToEnvelope };
+//# sourceMappingURL=add-email-overrides-to-envelope.d.cts.map

package/dist/actions/add-email-overrides-to-envelope.d.cts.map

@@ -0,0 +1 @@
+{"version":3,"file":"add-email-overrides-to-envelope.d.cts","names":[],"sources":["../../src/actions/add-email-overrides-to-envelope.ts"],"mappings":";;;cAIa,wCAAA,EAA0C,CAAA,CAAE,UASM;AAAA,cAKlD,yCAAA,EAA2C,CAAA,CAAE,UAIM;AAAA,cAEnD,mCAAA,gCAAmC,wBAAA,iDAAA,mBAAA,yCAAA,UAAA,4CAAA,UAAA"}

package/dist/actions/add-email-overrides-to-envelope.d.mts

@@ -0,0 +1,9 @@
+import { z } from "zod";
+
+//#region src/actions/add-email-overrides-to-envelope.d.ts
+declare const DocusignAddEmailOverridesToEnvelopeInput: z.ZodTypeAny;
+declare const DocusignAddEmailOverridesToEnvelopeOutput: z.ZodTypeAny;
+declare const docusignAddEmailOverridesToEnvelope: import("@keystrokehq/action").WorkflowActionDefinition<unknown, unknown, import("@keystrokehq/shared").ResolvedCredentials<readonly [import("@keystrokehq/shared").Credential]>, readonly [import("@keystrokehq/shared").Credential]>;
+//#endregion
+export { docusignAddEmailOverridesToEnvelope };
+//# sourceMappingURL=add-email-overrides-to-envelope.d.mts.map

package/dist/actions/add-email-overrides-to-envelope.d.mts.map

@@ -0,0 +1 @@
+{"version":3,"file":"add-email-overrides-to-envelope.d.mts","names":[],"sources":["../../src/actions/add-email-overrides-to-envelope.ts"],"mappings":";;;cAIa,wCAAA,EAA0C,CAAA,CAAE,UASM;AAAA,cAKlD,yCAAA,EAA2C,CAAA,CAAE,UAIM;AAAA,cAEnD,mCAAA,gCAAmC,wBAAA,iDAAA,mBAAA,yCAAA,UAAA,4CAAA,UAAA"}

package/dist/actions/add-email-overrides-to-envelope.mjs

@@ -0,0 +1,32 @@
+import { action } from "../action.mjs";
+import { z } from "zod";
+//#region src/actions/add-email-overrides-to-envelope.ts
+const DocusignAddEmailOverridesToEnvelopeInput = z.object({
+	accountId: z.string().describe("The unique identifier for the DocuSign account. This can be either the account number (integer) or the account ID GUID. It is required to specify which account the envelope belongs to. Format: string.").optional(),
+	envelopeId: z.string().describe("The unique identifier for the specific envelope to which the email settings will be applied. This is a GUID (Globally Unique Identifier) that uniquely identifies the envelope within the DocuSign system. Format: string. Example: \"93be49ab-xxxx-xxxx-xxxx-f752070d71ec\"."),
+	bccEmailAddresses: z.array(z.object({
+		email: z.string().describe("Specifies the BCC email address. DocuSign verifies that the email format is correct, but does not verify that the email is active. Using this overrides the BCC for Email Archive information setting for this envelope. Maximum length: 100 characters.").optional(),
+		bccEmailAddressId: z.string().describe("Unique identifier for the BCC email address entry. This is typically assigned by DocuSign when a BCC email address is added to the account settings. Optional field used to reference specific BCC configuration.").optional()
+	}).describe("Request schema for `BccEmailAddresses`")).describe("An array containing the email address that should receive a copy of all email communications related to an envelope for archiving purposes. Maximum Length: 100 characters. While this property is an array, note that it takes only a single email address. **Note:** Only users with the `canManageAccount` setting set to **true** can use this option.  Docusign verifies that the email format is correct, but does not verify that the email address is active. You can use this for archiving purposes. However, using this property overrides the BCC for Email Archive information setting for this envelope.  **Example:** if your account has BCC for Email Archive set up for the email address archive@mycompany.com and you send an envelope using the BCC Email Override to send a BCC email to salesarchive@mycompany.com, then a copy of the envelope is only sent to the salesarchive@mycompany.com email address.").optional(),
+	replyEmailNameOverride: z.string().describe("The name to associate with the Reply To email address, instead of the name that is configured at the account level. Maximum Length: 100 characters.").optional(),
+	replyEmailAddressOverride: z.string().describe("The Reply To email address to use for email replies, instead of the one that is configured at the account level. Docusign verifies that the email address is in a correct format, but does not verify that it is active. Maximum Length: 100 characters.").optional()
+}).describe("Request schema for `AddEmailOverridesToEnvelope`");
+const DocusignAddEmailOverridesToEnvelope_BccEmailAddressesResponseSchema = z.object({
+	email: z.string().describe("The BCC email address").nullable().optional(),
+	bccEmailAddressId: z.string().describe("Unique identifier for the BCC email address entry").nullable().optional()
+}).describe("Response schema for BCC email address");
+const docusignAddEmailOverridesToEnvelope = action("DOCUSIGN_ADD_EMAIL_OVERRIDES_TO_ENVELOPE", {
+	slug: "docusign-add-email-overrides-to-envelope",
+	name: "Add Email Overrides To Envelope",
+	description: "Adds or modifies email override settings for a specific DocuSign envelope, allowing customization of the reply-to email address and name, as well as BCC email addresses for archiving purposes. This endpoint should be used when you need to change email settings for an individual envelope, overriding the account-level configurations. It's particularly useful for setting up specialized archiving or customizing the reply-to information for specific envelopes. Note that these changes only affect email communications that occur after the addition is made, and the BCC feature is limited to users with appropriate permissions. For security reasons, additional signer authentication is recommended when using the BCC for Email Archive feature.",
+	input: DocusignAddEmailOverridesToEnvelopeInput,
+	output: z.object({
+		bccEmailAddresses: z.array(DocusignAddEmailOverridesToEnvelope_BccEmailAddressesResponseSchema).describe("Array of BCC email addresses configured for the envelope").nullable().optional(),
+		replyEmailNameOverride: z.string().describe("The Reply To name override for the envelope").nullable().optional(),
+		replyEmailAddressOverride: z.string().describe("The Reply To email address override for the envelope").nullable().optional()
+	}).describe("Response schema for `AddEmailOverridesToEnvelope`")
+});
+//#endregion
+export { docusignAddEmailOverridesToEnvelope };
+
+//# sourceMappingURL=add-email-overrides-to-envelope.mjs.map

package/dist/actions/add-email-overrides-to-envelope.mjs.map

@@ -0,0 +1 @@
+{"version":3,"file":"add-email-overrides-to-envelope.mjs","names":[],"sources":["../../src/actions/add-email-overrides-to-envelope.ts"],"sourcesContent":["import { z } from \"zod\";\n\nimport { action } from \"../action\";\n\nexport const DocusignAddEmailOverridesToEnvelopeInput: z.ZodTypeAny = z.object({\n  accountId: z.string().describe(\"The unique identifier for the DocuSign account. This can be either the account number (integer) or the account ID GUID. It is required to specify which account the envelope belongs to. Format: string.\").optional(),\n  envelopeId: z.string().describe(\"The unique identifier for the specific envelope to which the email settings will be applied. This is a GUID (Globally Unique Identifier) that uniquely identifies the envelope within the DocuSign system. Format: string. Example: \\\"93be49ab-xxxx-xxxx-xxxx-f752070d71ec\\\".\"),\n  bccEmailAddresses: z.array(z.object({\n  email: z.string().describe(\"Specifies the BCC email address. DocuSign verifies that the email format is correct, but does not verify that the email is active. Using this overrides the BCC for Email Archive information setting for this envelope. Maximum length: 100 characters.\").optional(),\n  bccEmailAddressId: z.string().describe(\"Unique identifier for the BCC email address entry. This is typically assigned by DocuSign when a BCC email address is added to the account settings. Optional field used to reference specific BCC configuration.\").optional(),\n}).describe(\"Request schema for `BccEmailAddresses`\")).describe(\"An array containing the email address that should receive a copy of all email communications related to an envelope for archiving purposes. Maximum Length: 100 characters. While this property is an array, note that it takes only a single email address. **Note:** Only users with the `canManageAccount` setting set to **true** can use this option.  Docusign verifies that the email format is correct, but does not verify that the email address is active. You can use this for archiving purposes. However, using this property overrides the BCC for Email Archive information setting for this envelope.  **Example:** if your account has BCC for Email Archive set up for the email address archive@mycompany.com and you send an envelope using the BCC Email Override to send a BCC email to salesarchive@mycompany.com, then a copy of the envelope is only sent to the salesarchive@mycompany.com email address.\").optional(),\n  replyEmailNameOverride: z.string().describe(\"The name to associate with the Reply To email address, instead of the name that is configured at the account level. Maximum Length: 100 characters.\").optional(),\n  replyEmailAddressOverride: z.string().describe(\"The Reply To email address to use for email replies, instead of the one that is configured at the account level. Docusign verifies that the email address is in a correct format, but does not verify that it is active. Maximum Length: 100 characters.\").optional(),\n}).describe(\"Request schema for `AddEmailOverridesToEnvelope`\");\nconst DocusignAddEmailOverridesToEnvelope_BccEmailAddressesResponseSchema: z.ZodTypeAny = z.object({\n  email: z.string().describe(\"The BCC email address\").nullable().optional(),\n  bccEmailAddressId: z.string().describe(\"Unique identifier for the BCC email address entry\").nullable().optional(),\n}).describe(\"Response schema for BCC email address\");\nexport const DocusignAddEmailOverridesToEnvelopeOutput: z.ZodTypeAny = z.object({\n  bccEmailAddresses: z.array(DocusignAddEmailOverridesToEnvelope_BccEmailAddressesResponseSchema).describe(\"Array of BCC email addresses configured for the envelope\").nullable().optional(),\n  replyEmailNameOverride: z.string().describe(\"The Reply To name override for the envelope\").nullable().optional(),\n  replyEmailAddressOverride: z.string().describe(\"The Reply To email address override for the envelope\").nullable().optional(),\n}).describe(\"Response schema for `AddEmailOverridesToEnvelope`\");\n\nexport const docusignAddEmailOverridesToEnvelope = action(\"DOCUSIGN_ADD_EMAIL_OVERRIDES_TO_ENVELOPE\", {\n  slug: \"docusign-add-email-overrides-to-envelope\",\n  name: \"Add Email Overrides To Envelope\",\n  description: \"Adds or modifies email override settings for a specific DocuSign envelope, allowing customization of the reply-to email address and name, as well as BCC email addresses for archiving purposes. This endpoint should be used when you need to change email settings for an individual envelope, overriding the account-level configurations. It's particularly useful for setting up specialized archiving or customizing the reply-to information for specific envelopes. Note that these changes only affect email communications that occur after the addition is made, and the BCC feature is limited to users with appropriate permissions. For security reasons, additional signer authentication is recommended when using the BCC for Email Archive feature.\",\n  input: DocusignAddEmailOverridesToEnvelopeInput,\n  output: DocusignAddEmailOverridesToEnvelopeOutput,\n});\n"],"mappings":";;;AAIA,MAAa,2CAAyD,EAAE,OAAO;CAC7E,WAAW,EAAE,OAAO,CAAC,CAAC,SAAS,0MAA0M,CAAC,CAAC,SAAS;CACpP,YAAY,EAAE,OAAO,CAAC,CAAC,SAAS,+QAA+Q;CAC/S,mBAAmB,EAAE,MAAM,EAAE,OAAO;EACpC,OAAO,EAAE,OAAO,CAAC,CAAC,SAAS,0PAA0P,CAAC,CAAC,SAAS;EAChS,mBAAmB,EAAE,OAAO,CAAC,CAAC,SAAS,mNAAmN,CAAC,CAAC,SAAS;CACvQ,CAAC,CAAC,CAAC,SAAS,wCAAwC,CAAC,CAAC,CAAC,SAAS,s4BAAs4B,CAAC,CAAC,SAAS;CAC/8B,wBAAwB,EAAE,OAAO,CAAC,CAAC,SAAS,qJAAqJ,CAAC,CAAC,SAAS;CAC5M,2BAA2B,EAAE,OAAO,CAAC,CAAC,SAAS,0PAA0P,CAAC,CAAC,SAAS;AACtT,CAAC,CAAC,CAAC,SAAS,kDAAkD;AAC9D,MAAM,sEAAoF,EAAE,OAAO;CACjG,OAAO,EAAE,OAAO,CAAC,CAAC,SAAS,uBAAuB,CAAC,CAAC,SAAS,CAAC,CAAC,SAAS;CACxE,mBAAmB,EAAE,OAAO,CAAC,CAAC,SAAS,mDAAmD,CAAC,CAAC,SAAS,CAAC,CAAC,SAAS;AAClH,CAAC,CAAC,CAAC,SAAS,uCAAuC;AAOnD,MAAa,sCAAsC,OAAO,4CAA4C;CACpG,MAAM;CACN,MAAM;CACN,aAAa;CACb,OAAO;CACP,QAXqE,EAAE,OAAO;EAC9E,mBAAmB,EAAE,MAAM,mEAAmE,CAAC,CAAC,SAAS,0DAA0D,CAAC,CAAC,SAAS,CAAC,CAAC,SAAS;EACzL,wBAAwB,EAAE,OAAO,CAAC,CAAC,SAAS,6CAA6C,CAAC,CAAC,SAAS,CAAC,CAAC,SAAS;EAC/G,2BAA2B,EAAE,OAAO,CAAC,CAAC,SAAS,sDAAsD,CAAC,CAAC,SAAS,CAAC,CAAC,SAAS;CAC7H,CAAC,CAAC,CAAC,SAAS,mDAOF;AACV,CAAC"}

package/dist/actions/add-envelope-attachments.cjs

@@ -0,0 +1,35 @@
+const require_action = require("../action.cjs");
+let zod = require("zod");
+//#region src/actions/add-envelope-attachments.ts
+const DocusignAddEnvelopeAttachmentsInput = zod.z.object({
+	accountId: zod.z.string().describe("The DocuSign account ID (GUID format). This parameter is automatically populated by the system from your authenticated account, so you typically don't need to provide it. If provided explicitly, it must match your authenticated account ID.").optional(),
+	envelopeId: zod.z.string().describe("The unique identifier for the envelope to which attachments will be added. This is a required parameter in the format of a GUID (Globally Unique Identifier). Example: \"93be49ab-xxxx-xxxx-xxxx-f752070d71ec\". It specifies the exact envelope that will receive the new attachments."),
+	attachments: zod.z.array(zod.z.object({
+		data: zod.z.string().describe("Base64-encoded file content for the attachment. File attachments may be up to 50 MB in size. Either `data` or `remoteUrl` must be provided - use `data` for direct file uploads, or `remoteUrl` to reference a pre-staged chunked upload for larger files.").optional(),
+		name: zod.z.string().describe("The filename for the attachment (e.g., 'contract-addendum.pdf', 'supporting-docs.zip'). This is displayed to recipients who have access to view the attachment.").optional(),
+		label: zod.z.string().describe("A label for the attachment. Potential values include:  - `guidedForm`: [Guided forms](https://www.docusign.com/products/guided-forms) provide a step-by-step, mobile-ready experience to help signers easily complete long or complex forms. - `eventNotifications`: A list of envelope-level event statuses that trigger Connect to send updates to the endpoint specified in the `url` property.").optional(),
+		remoteUrl: zod.z.string().describe("The URL of a previously staged chunked upload. Using a chunked upload enables you to stage a large, chunkable temp file. You then use the `remoteUrl` property to reference the chunked upload as the content in attachment and document-related requests. The `remoteUrl` property cannot be used for downloads.").optional(),
+		attachmentId: zod.z.string().describe("Optional attachment identifier. Note: DocuSign generates a unique attachmentId upon creation and does not use the value provided here.").optional(),
+		accessControl: zod.z.string().default("sender").describe("Controls who can view the attachment. Valid values are `sender` (default) and `senderAndAllRecipients`.").optional(),
+		attachmentType: zod.z.string().describe("The type/category of the attachment. Common values include 'document' for supporting documents, 'metadata' for structured data files, or custom values for application-specific categorization.").optional()
+	}).describe("Request schema for `Attachments`")).describe("A list of attachment objects to add to the envelope. Each attachment should include a name and either base64-encoded data or a remoteUrl.").optional()
+}).describe("Request schema for `AddEnvelopeAttachments`");
+const DocusignAddEnvelopeAttachments_AttachmentResponseSchema = zod.z.object({
+	name: zod.z.string().describe("The name of the attachment.").nullable().optional(),
+	label: zod.z.string().describe("The label/category of the attachment.").nullable().optional(),
+	attachmentId: zod.z.string().describe("The unique system-generated identifier for the attachment.").nullable().optional(),
+	accessControl: zod.z.string().describe("Who can access the attachment: 'sender' or 'senderAndAllRecipients'.").nullable().optional(),
+	attachmentType: zod.z.string().describe("The type of the attachment.").nullable().optional()
+}).describe("Schema for attachment response");
+const DocusignAddEnvelopeAttachmentsOutput = zod.z.object({ attachments: zod.z.array(DocusignAddEnvelopeAttachments_AttachmentResponseSchema).describe("List of attachments that were added to the envelope with their system-generated IDs.").nullable().optional() }).describe("Response schema for `AddEnvelopeAttachments`");
+const docusignAddEnvelopeAttachments = require_action.action("DOCUSIGN_ADD_ENVELOPE_ATTACHMENTS", {
+	slug: "docusign-add-envelope-attachments",
+	name: "Add envelope attachments",
+	description: "Adds one or more envelope attachments to a draft or in-process envelope in DocuSign. This endpoint allows developers to include additional files with an envelope that are not converted to PDF and are only accessible through the API. It's useful for attaching supporting documents or metadata files that should not be part of the main signing process. The endpoint supports up to 12 attachments per envelope, with a maximum file size of 50 MB each. Note that these attachments are not visible in the DocuSign web application and are intended for programmatic use only.",
+	input: DocusignAddEnvelopeAttachmentsInput,
+	output: DocusignAddEnvelopeAttachmentsOutput
+});
+//#endregion
+exports.docusignAddEnvelopeAttachments = docusignAddEnvelopeAttachments;
+
+//# sourceMappingURL=add-envelope-attachments.cjs.map

package/dist/actions/add-envelope-attachments.cjs.map

@@ -0,0 +1 @@
+{"version":3,"file":"add-envelope-attachments.cjs","names":["z","action"],"sources":["../../src/actions/add-envelope-attachments.ts"],"sourcesContent":["import { z } from \"zod\";\n\nimport { action } from \"../action\";\n\nexport const DocusignAddEnvelopeAttachmentsInput: z.ZodTypeAny = z.object({\n  accountId: z.string().describe(\"The DocuSign account ID (GUID format). This parameter is automatically populated by the system from your authenticated account, so you typically don't need to provide it. If provided explicitly, it must match your authenticated account ID.\").optional(),\n  envelopeId: z.string().describe(\"The unique identifier for the envelope to which attachments will be added. This is a required parameter in the format of a GUID (Globally Unique Identifier). Example: \\\"93be49ab-xxxx-xxxx-xxxx-f752070d71ec\\\". It specifies the exact envelope that will receive the new attachments.\"),\n  attachments: z.array(z.object({\n  data: z.string().describe(\"Base64-encoded file content for the attachment. File attachments may be up to 50 MB in size. Either `data` or `remoteUrl` must be provided - use `data` for direct file uploads, or `remoteUrl` to reference a pre-staged chunked upload for larger files.\").optional(),\n  name: z.string().describe(\"The filename for the attachment (e.g., 'contract-addendum.pdf', 'supporting-docs.zip'). This is displayed to recipients who have access to view the attachment.\").optional(),\n  label: z.string().describe(\"A label for the attachment. Potential values include:  - `guidedForm`: [Guided forms](https://www.docusign.com/products/guided-forms) provide a step-by-step, mobile-ready experience to help signers easily complete long or complex forms. - `eventNotifications`: A list of envelope-level event statuses that trigger Connect to send updates to the endpoint specified in the `url` property.\").optional(),\n  remoteUrl: z.string().describe(\"The URL of a previously staged chunked upload. Using a chunked upload enables you to stage a large, chunkable temp file. You then use the `remoteUrl` property to reference the chunked upload as the content in attachment and document-related requests. The `remoteUrl` property cannot be used for downloads.\").optional(),\n  attachmentId: z.string().describe(\"Optional attachment identifier. Note: DocuSign generates a unique attachmentId upon creation and does not use the value provided here.\").optional(),\n  accessControl: z.string().default(\"sender\").describe(\"Controls who can view the attachment. Valid values are `sender` (default) and `senderAndAllRecipients`.\").optional(),\n  attachmentType: z.string().describe(\"The type/category of the attachment. Common values include 'document' for supporting documents, 'metadata' for structured data files, or custom values for application-specific categorization.\").optional(),\n}).describe(\"Request schema for `Attachments`\")).describe(\"A list of attachment objects to add to the envelope. Each attachment should include a name and either base64-encoded data or a remoteUrl.\").optional(),\n}).describe(\"Request schema for `AddEnvelopeAttachments`\");\nconst DocusignAddEnvelopeAttachments_AttachmentResponseSchema: z.ZodTypeAny = z.object({\n  name: z.string().describe(\"The name of the attachment.\").nullable().optional(),\n  label: z.string().describe(\"The label/category of the attachment.\").nullable().optional(),\n  attachmentId: z.string().describe(\"The unique system-generated identifier for the attachment.\").nullable().optional(),\n  accessControl: z.string().describe(\"Who can access the attachment: 'sender' or 'senderAndAllRecipients'.\").nullable().optional(),\n  attachmentType: z.string().describe(\"The type of the attachment.\").nullable().optional(),\n}).describe(\"Schema for attachment response\");\nexport const DocusignAddEnvelopeAttachmentsOutput: z.ZodTypeAny = z.object({\n  attachments: z.array(DocusignAddEnvelopeAttachments_AttachmentResponseSchema).describe(\"List of attachments that were added to the envelope with their system-generated IDs.\").nullable().optional(),\n}).describe(\"Response schema for `AddEnvelopeAttachments`\");\n\nexport const docusignAddEnvelopeAttachments = action(\"DOCUSIGN_ADD_ENVELOPE_ATTACHMENTS\", {\n  slug: \"docusign-add-envelope-attachments\",\n  name: \"Add envelope attachments\",\n  description: \"Adds one or more envelope attachments to a draft or in-process envelope in DocuSign. This endpoint allows developers to include additional files with an envelope that are not converted to PDF and are only accessible through the API. It's useful for attaching supporting documents or metadata files that should not be part of the main signing process. The endpoint supports up to 12 attachments per envelope, with a maximum file size of 50 MB each. Note that these attachments are not visible in the DocuSign web application and are intended for programmatic use only.\",\n  input: DocusignAddEnvelopeAttachmentsInput,\n  output: DocusignAddEnvelopeAttachmentsOutput,\n});\n"],"mappings":";;;AAIA,MAAa,sCAAoDA,IAAAA,EAAE,OAAO;CACxE,WAAWA,IAAAA,EAAE,OAAO,CAAC,CAAC,SAAS,iPAAiP,CAAC,CAAC,SAAS;CAC3R,YAAYA,IAAAA,EAAE,OAAO,CAAC,CAAC,SAAS,yRAAyR;CACzT,aAAaA,IAAAA,EAAE,MAAMA,IAAAA,EAAE,OAAO;EAC9B,MAAMA,IAAAA,EAAE,OAAO,CAAC,CAAC,SAAS,4PAA4P,CAAC,CAAC,SAAS;EACjS,MAAMA,IAAAA,EAAE,OAAO,CAAC,CAAC,SAAS,iKAAiK,CAAC,CAAC,SAAS;EACtM,OAAOA,IAAAA,EAAE,OAAO,CAAC,CAAC,SAAS,oYAAoY,CAAC,CAAC,SAAS;EAC1a,WAAWA,IAAAA,EAAE,OAAO,CAAC,CAAC,SAAS,mTAAmT,CAAC,CAAC,SAAS;EAC7V,cAAcA,IAAAA,EAAE,OAAO,CAAC,CAAC,SAAS,wIAAwI,CAAC,CAAC,SAAS;EACrL,eAAeA,IAAAA,EAAE,OAAO,CAAC,CAAC,QAAQ,QAAQ,CAAC,CAAC,SAAS,yGAAyG,CAAC,CAAC,SAAS;EACzK,gBAAgBA,IAAAA,EAAE,OAAO,CAAC,CAAC,SAAS,iMAAiM,CAAC,CAAC,SAAS;CAClP,CAAC,CAAC,CAAC,SAAS,kCAAkC,CAAC,CAAC,CAAC,SAAS,2IAA2I,CAAC,CAAC,SAAS;AAChN,CAAC,CAAC,CAAC,SAAS,6CAA6C;AACzD,MAAM,0DAAwEA,IAAAA,EAAE,OAAO;CACrF,MAAMA,IAAAA,EAAE,OAAO,CAAC,CAAC,SAAS,6BAA6B,CAAC,CAAC,SAAS,CAAC,CAAC,SAAS;CAC7E,OAAOA,IAAAA,EAAE,OAAO,CAAC,CAAC,SAAS,uCAAuC,CAAC,CAAC,SAAS,CAAC,CAAC,SAAS;CACxF,cAAcA,IAAAA,EAAE,OAAO,CAAC,CAAC,SAAS,4DAA4D,CAAC,CAAC,SAAS,CAAC,CAAC,SAAS;CACpH,eAAeA,IAAAA,EAAE,OAAO,CAAC,CAAC,SAAS,sEAAsE,CAAC,CAAC,SAAS,CAAC,CAAC,SAAS;CAC/H,gBAAgBA,IAAAA,EAAE,OAAO,CAAC,CAAC,SAAS,6BAA6B,CAAC,CAAC,SAAS,CAAC,CAAC,SAAS;AACzF,CAAC,CAAC,CAAC,SAAS,gCAAgC;AAC5C,MAAa,uCAAqDA,IAAAA,EAAE,OAAO,EACzE,aAAaA,IAAAA,EAAE,MAAM,uDAAuD,CAAC,CAAC,SAAS,sFAAsF,CAAC,CAAC,SAAS,CAAC,CAAC,SAAS,EACrM,CAAC,CAAC,CAAC,SAAS,8CAA8C;AAE1D,MAAa,iCAAiCC,eAAAA,OAAO,qCAAqC;CACxF,MAAM;CACN,MAAM;CACN,aAAa;CACb,OAAO;CACP,QAAQ;AACV,CAAC"}

package/dist/actions/add-envelope-attachments.d.cts

@@ -0,0 +1,9 @@
+import { z } from "zod";
+
+//#region src/actions/add-envelope-attachments.d.ts
+declare const DocusignAddEnvelopeAttachmentsInput: z.ZodTypeAny;
+declare const DocusignAddEnvelopeAttachmentsOutput: z.ZodTypeAny;
+declare const docusignAddEnvelopeAttachments: import("@keystrokehq/action").WorkflowActionDefinition<unknown, unknown, import("@keystrokehq/shared").ResolvedCredentials<readonly [import("@keystrokehq/shared").Credential]>, readonly [import("@keystrokehq/shared").Credential]>;
+//#endregion
+export { docusignAddEnvelopeAttachments };
+//# sourceMappingURL=add-envelope-attachments.d.cts.map

package/dist/actions/add-envelope-attachments.d.cts.map

@@ -0,0 +1 @@
+{"version":3,"file":"add-envelope-attachments.d.cts","names":[],"sources":["../../src/actions/add-envelope-attachments.ts"],"mappings":";;;cAIa,mCAAA,EAAqC,CAAA,CAAE,UAYM;AAAA,cAQ7C,oCAAA,EAAsC,CAAA,CAAE,UAEM;AAAA,cAE9C,8BAAA,gCAA8B,wBAAA,iDAAA,mBAAA,yCAAA,UAAA,4CAAA,UAAA"}

package/dist/actions/add-envelope-attachments.d.mts

@@ -0,0 +1,9 @@
+import { z } from "zod";
+
+//#region src/actions/add-envelope-attachments.d.ts
+declare const DocusignAddEnvelopeAttachmentsInput: z.ZodTypeAny;
+declare const DocusignAddEnvelopeAttachmentsOutput: z.ZodTypeAny;
+declare const docusignAddEnvelopeAttachments: import("@keystrokehq/action").WorkflowActionDefinition<unknown, unknown, import("@keystrokehq/shared").ResolvedCredentials<readonly [import("@keystrokehq/shared").Credential]>, readonly [import("@keystrokehq/shared").Credential]>;
+//#endregion
+export { docusignAddEnvelopeAttachments };
+//# sourceMappingURL=add-envelope-attachments.d.mts.map

package/dist/actions/add-envelope-attachments.d.mts.map

@@ -0,0 +1 @@
+{"version":3,"file":"add-envelope-attachments.d.mts","names":[],"sources":["../../src/actions/add-envelope-attachments.ts"],"mappings":";;;cAIa,mCAAA,EAAqC,CAAA,CAAE,UAYM;AAAA,cAQ7C,oCAAA,EAAsC,CAAA,CAAE,UAEM;AAAA,cAE9C,8BAAA,gCAA8B,wBAAA,iDAAA,mBAAA,yCAAA,UAAA,4CAAA,UAAA"}

package/dist/actions/add-envelope-attachments.mjs

@@ -0,0 +1,34 @@
+import { action } from "../action.mjs";
+import { z } from "zod";
+//#region src/actions/add-envelope-attachments.ts
+const DocusignAddEnvelopeAttachmentsInput = z.object({
+	accountId: z.string().describe("The DocuSign account ID (GUID format). This parameter is automatically populated by the system from your authenticated account, so you typically don't need to provide it. If provided explicitly, it must match your authenticated account ID.").optional(),
+	envelopeId: z.string().describe("The unique identifier for the envelope to which attachments will be added. This is a required parameter in the format of a GUID (Globally Unique Identifier). Example: \"93be49ab-xxxx-xxxx-xxxx-f752070d71ec\". It specifies the exact envelope that will receive the new attachments."),
+	attachments: z.array(z.object({
+		data: z.string().describe("Base64-encoded file content for the attachment. File attachments may be up to 50 MB in size. Either `data` or `remoteUrl` must be provided - use `data` for direct file uploads, or `remoteUrl` to reference a pre-staged chunked upload for larger files.").optional(),
+		name: z.string().describe("The filename for the attachment (e.g., 'contract-addendum.pdf', 'supporting-docs.zip'). This is displayed to recipients who have access to view the attachment.").optional(),
+		label: z.string().describe("A label for the attachment. Potential values include:  - `guidedForm`: [Guided forms](https://www.docusign.com/products/guided-forms) provide a step-by-step, mobile-ready experience to help signers easily complete long or complex forms. - `eventNotifications`: A list of envelope-level event statuses that trigger Connect to send updates to the endpoint specified in the `url` property.").optional(),
+		remoteUrl: z.string().describe("The URL of a previously staged chunked upload. Using a chunked upload enables you to stage a large, chunkable temp file. You then use the `remoteUrl` property to reference the chunked upload as the content in attachment and document-related requests. The `remoteUrl` property cannot be used for downloads.").optional(),
+		attachmentId: z.string().describe("Optional attachment identifier. Note: DocuSign generates a unique attachmentId upon creation and does not use the value provided here.").optional(),
+		accessControl: z.string().default("sender").describe("Controls who can view the attachment. Valid values are `sender` (default) and `senderAndAllRecipients`.").optional(),
+		attachmentType: z.string().describe("The type/category of the attachment. Common values include 'document' for supporting documents, 'metadata' for structured data files, or custom values for application-specific categorization.").optional()
+	}).describe("Request schema for `Attachments`")).describe("A list of attachment objects to add to the envelope. Each attachment should include a name and either base64-encoded data or a remoteUrl.").optional()
+}).describe("Request schema for `AddEnvelopeAttachments`");
+const DocusignAddEnvelopeAttachments_AttachmentResponseSchema = z.object({
+	name: z.string().describe("The name of the attachment.").nullable().optional(),
+	label: z.string().describe("The label/category of the attachment.").nullable().optional(),
+	attachmentId: z.string().describe("The unique system-generated identifier for the attachment.").nullable().optional(),
+	accessControl: z.string().describe("Who can access the attachment: 'sender' or 'senderAndAllRecipients'.").nullable().optional(),
+	attachmentType: z.string().describe("The type of the attachment.").nullable().optional()
+}).describe("Schema for attachment response");
+const docusignAddEnvelopeAttachments = action("DOCUSIGN_ADD_ENVELOPE_ATTACHMENTS", {
+	slug: "docusign-add-envelope-attachments",
+	name: "Add envelope attachments",
+	description: "Adds one or more envelope attachments to a draft or in-process envelope in DocuSign. This endpoint allows developers to include additional files with an envelope that are not converted to PDF and are only accessible through the API. It's useful for attaching supporting documents or metadata files that should not be part of the main signing process. The endpoint supports up to 12 attachments per envelope, with a maximum file size of 50 MB each. Note that these attachments are not visible in the DocuSign web application and are intended for programmatic use only.",
+	input: DocusignAddEnvelopeAttachmentsInput,
+	output: z.object({ attachments: z.array(DocusignAddEnvelopeAttachments_AttachmentResponseSchema).describe("List of attachments that were added to the envelope with their system-generated IDs.").nullable().optional() }).describe("Response schema for `AddEnvelopeAttachments`")
+});
+//#endregion
+export { docusignAddEnvelopeAttachments };
+
+//# sourceMappingURL=add-envelope-attachments.mjs.map

package/dist/actions/add-envelope-attachments.mjs.map

@@ -0,0 +1 @@
+{"version":3,"file":"add-envelope-attachments.mjs","names":[],"sources":["../../src/actions/add-envelope-attachments.ts"],"sourcesContent":["import { z } from \"zod\";\n\nimport { action } from \"../action\";\n\nexport const DocusignAddEnvelopeAttachmentsInput: z.ZodTypeAny = z.object({\n  accountId: z.string().describe(\"The DocuSign account ID (GUID format). This parameter is automatically populated by the system from your authenticated account, so you typically don't need to provide it. If provided explicitly, it must match your authenticated account ID.\").optional(),\n  envelopeId: z.string().describe(\"The unique identifier for the envelope to which attachments will be added. This is a required parameter in the format of a GUID (Globally Unique Identifier). Example: \\\"93be49ab-xxxx-xxxx-xxxx-f752070d71ec\\\". It specifies the exact envelope that will receive the new attachments.\"),\n  attachments: z.array(z.object({\n  data: z.string().describe(\"Base64-encoded file content for the attachment. File attachments may be up to 50 MB in size. Either `data` or `remoteUrl` must be provided - use `data` for direct file uploads, or `remoteUrl` to reference a pre-staged chunked upload for larger files.\").optional(),\n  name: z.string().describe(\"The filename for the attachment (e.g., 'contract-addendum.pdf', 'supporting-docs.zip'). This is displayed to recipients who have access to view the attachment.\").optional(),\n  label: z.string().describe(\"A label for the attachment. Potential values include:  - `guidedForm`: [Guided forms](https://www.docusign.com/products/guided-forms) provide a step-by-step, mobile-ready experience to help signers easily complete long or complex forms. - `eventNotifications`: A list of envelope-level event statuses that trigger Connect to send updates to the endpoint specified in the `url` property.\").optional(),\n  remoteUrl: z.string().describe(\"The URL of a previously staged chunked upload. Using a chunked upload enables you to stage a large, chunkable temp file. You then use the `remoteUrl` property to reference the chunked upload as the content in attachment and document-related requests. The `remoteUrl` property cannot be used for downloads.\").optional(),\n  attachmentId: z.string().describe(\"Optional attachment identifier. Note: DocuSign generates a unique attachmentId upon creation and does not use the value provided here.\").optional(),\n  accessControl: z.string().default(\"sender\").describe(\"Controls who can view the attachment. Valid values are `sender` (default) and `senderAndAllRecipients`.\").optional(),\n  attachmentType: z.string().describe(\"The type/category of the attachment. Common values include 'document' for supporting documents, 'metadata' for structured data files, or custom values for application-specific categorization.\").optional(),\n}).describe(\"Request schema for `Attachments`\")).describe(\"A list of attachment objects to add to the envelope. Each attachment should include a name and either base64-encoded data or a remoteUrl.\").optional(),\n}).describe(\"Request schema for `AddEnvelopeAttachments`\");\nconst DocusignAddEnvelopeAttachments_AttachmentResponseSchema: z.ZodTypeAny = z.object({\n  name: z.string().describe(\"The name of the attachment.\").nullable().optional(),\n  label: z.string().describe(\"The label/category of the attachment.\").nullable().optional(),\n  attachmentId: z.string().describe(\"The unique system-generated identifier for the attachment.\").nullable().optional(),\n  accessControl: z.string().describe(\"Who can access the attachment: 'sender' or 'senderAndAllRecipients'.\").nullable().optional(),\n  attachmentType: z.string().describe(\"The type of the attachment.\").nullable().optional(),\n}).describe(\"Schema for attachment response\");\nexport const DocusignAddEnvelopeAttachmentsOutput: z.ZodTypeAny = z.object({\n  attachments: z.array(DocusignAddEnvelopeAttachments_AttachmentResponseSchema).describe(\"List of attachments that were added to the envelope with their system-generated IDs.\").nullable().optional(),\n}).describe(\"Response schema for `AddEnvelopeAttachments`\");\n\nexport const docusignAddEnvelopeAttachments = action(\"DOCUSIGN_ADD_ENVELOPE_ATTACHMENTS\", {\n  slug: \"docusign-add-envelope-attachments\",\n  name: \"Add envelope attachments\",\n  description: \"Adds one or more envelope attachments to a draft or in-process envelope in DocuSign. This endpoint allows developers to include additional files with an envelope that are not converted to PDF and are only accessible through the API. It's useful for attaching supporting documents or metadata files that should not be part of the main signing process. The endpoint supports up to 12 attachments per envelope, with a maximum file size of 50 MB each. Note that these attachments are not visible in the DocuSign web application and are intended for programmatic use only.\",\n  input: DocusignAddEnvelopeAttachmentsInput,\n  output: DocusignAddEnvelopeAttachmentsOutput,\n});\n"],"mappings":";;;AAIA,MAAa,sCAAoD,EAAE,OAAO;CACxE,WAAW,EAAE,OAAO,CAAC,CAAC,SAAS,iPAAiP,CAAC,CAAC,SAAS;CAC3R,YAAY,EAAE,OAAO,CAAC,CAAC,SAAS,yRAAyR;CACzT,aAAa,EAAE,MAAM,EAAE,OAAO;EAC9B,MAAM,EAAE,OAAO,CAAC,CAAC,SAAS,4PAA4P,CAAC,CAAC,SAAS;EACjS,MAAM,EAAE,OAAO,CAAC,CAAC,SAAS,iKAAiK,CAAC,CAAC,SAAS;EACtM,OAAO,EAAE,OAAO,CAAC,CAAC,SAAS,oYAAoY,CAAC,CAAC,SAAS;EAC1a,WAAW,EAAE,OAAO,CAAC,CAAC,SAAS,mTAAmT,CAAC,CAAC,SAAS;EAC7V,cAAc,EAAE,OAAO,CAAC,CAAC,SAAS,wIAAwI,CAAC,CAAC,SAAS;EACrL,eAAe,EAAE,OAAO,CAAC,CAAC,QAAQ,QAAQ,CAAC,CAAC,SAAS,yGAAyG,CAAC,CAAC,SAAS;EACzK,gBAAgB,EAAE,OAAO,CAAC,CAAC,SAAS,iMAAiM,CAAC,CAAC,SAAS;CAClP,CAAC,CAAC,CAAC,SAAS,kCAAkC,CAAC,CAAC,CAAC,SAAS,2IAA2I,CAAC,CAAC,SAAS;AAChN,CAAC,CAAC,CAAC,SAAS,6CAA6C;AACzD,MAAM,0DAAwE,EAAE,OAAO;CACrF,MAAM,EAAE,OAAO,CAAC,CAAC,SAAS,6BAA6B,CAAC,CAAC,SAAS,CAAC,CAAC,SAAS;CAC7E,OAAO,EAAE,OAAO,CAAC,CAAC,SAAS,uCAAuC,CAAC,CAAC,SAAS,CAAC,CAAC,SAAS;CACxF,cAAc,EAAE,OAAO,CAAC,CAAC,SAAS,4DAA4D,CAAC,CAAC,SAAS,CAAC,CAAC,SAAS;CACpH,eAAe,EAAE,OAAO,CAAC,CAAC,SAAS,sEAAsE,CAAC,CAAC,SAAS,CAAC,CAAC,SAAS;CAC/H,gBAAgB,EAAE,OAAO,CAAC,CAAC,SAAS,6BAA6B,CAAC,CAAC,SAAS,CAAC,CAAC,SAAS;AACzF,CAAC,CAAC,CAAC,SAAS,gCAAgC;AAK5C,MAAa,iCAAiC,OAAO,qCAAqC;CACxF,MAAM;CACN,MAAM;CACN,aAAa;CACb,OAAO;CACP,QATgE,EAAE,OAAO,EACzE,aAAa,EAAE,MAAM,uDAAuD,CAAC,CAAC,SAAS,sFAAsF,CAAC,CAAC,SAAS,CAAC,CAAC,SAAS,EACrM,CAAC,CAAC,CAAC,SAAS,8CAOF;AACV,CAAC"}

package/dist/actions/add-existing-brand-to-group.cjs

@@ -0,0 +1,27 @@
+const require_action = require("../action.cjs");
+let zod = require("zod");
+//#region src/actions/add-existing-brand-to-group.ts
+const DocusignAddExistingBrandToGroupInput = zod.z.object({
+	brands: zod.z.array(zod.z.object({ brandId: zod.z.string().describe("The unique identifier of the brand to add to the group. This must be an existing brand ID from the account's available brands. You can retrieve available brand IDs using the list brands endpoint.") }).describe("Request schema for `Brands`")).describe("A list of brand objects to add to the group. Each object must contain a valid brandId. This replaces any existing brand assignments for the group, so include all brands that should be associated with the group, not just new ones. An empty list will remove all brand associations from the group."),
+	groupId: zod.z.string().describe("The ID of the group being accessed. This is a required parameter that specifies which group will have brands added to it. The groupId must be a valid, existing group within the specified account. It is typically a string of characters that uniquely identifies the group in the DocuSign system."),
+	accountId: zod.z.string().describe("The external account number (int) or account ID GUID. This parameter is automatically populated by the DocuSign base action from your authenticated session. It identifies the DocuSign account for which the group brand association is being updated. You typically do not need to provide this value manually as it will be injected automatically.").optional()
+}).describe("Request schema for `AddExistingBrandToGroup`");
+const DocusignAddExistingBrandToGroup_BrandsResponseSchema = zod.z.object({
+	brandId: zod.z.string().describe("The ID of the brand").nullable().optional(),
+	brandName: zod.z.string().describe("The name of the brand").nullable().optional(),
+	brandCompany: zod.z.string().describe("The company associated with the brand").nullable().optional(),
+	errorDetails__message: zod.z.string().describe("The error message if the operation failed for this brand").nullable().optional(),
+	errorDetails__errorCode: zod.z.string().describe("The error code if the operation failed for this brand").nullable().optional()
+}).describe("Response schema for individual brand in the response");
+const DocusignAddExistingBrandToGroupOutput = zod.z.object({ brands: zod.z.array(DocusignAddExistingBrandToGroup_BrandsResponseSchema).describe("List of brands that were added to the group").nullable().optional() }).describe("Response schema for `AddExistingBrandToGroup`");
+const docusignAddExistingBrandToGroup = require_action.action("DOCUSIGN_ADD_EXISTING_BRAND_TO_GROUP", {
+	slug: "docusign-add-existing-brand-to-group",
+	name: "Add existing brand to group",
+	description: "This endpoint adds one or more existing brands to a specified group in DocuSign. It allows users to associate multiple brands with a group, enabling customized branding for different groups within an account. The endpoint should be used when there's a need to update the brands associated with a particular group, such as when reorganizing branding strategies or expanding brand options for specific user groups. It's important to note that this endpoint only adds existing brands to a group and does not create new brands or modify brand details.",
+	input: DocusignAddExistingBrandToGroupInput,
+	output: DocusignAddExistingBrandToGroupOutput
+});
+//#endregion
+exports.docusignAddExistingBrandToGroup = docusignAddExistingBrandToGroup;
+
+//# sourceMappingURL=add-existing-brand-to-group.cjs.map

package/dist/actions/add-existing-brand-to-group.cjs.map

@@ -0,0 +1 @@
+{"version":3,"file":"add-existing-brand-to-group.cjs","names":["z","action"],"sources":["../../src/actions/add-existing-brand-to-group.ts"],"sourcesContent":["import { z } from \"zod\";\n\nimport { action } from \"../action\";\n\nexport const DocusignAddExistingBrandToGroupInput: z.ZodTypeAny = z.object({\n  brands: z.array(z.object({\n  brandId: z.string().describe(\"The unique identifier of the brand to add to the group. This must be an existing brand ID from the account's available brands. You can retrieve available brand IDs using the list brands endpoint.\"),\n}).describe(\"Request schema for `Brands`\")).describe(\"A list of brand objects to add to the group. Each object must contain a valid brandId. This replaces any existing brand assignments for the group, so include all brands that should be associated with the group, not just new ones. An empty list will remove all brand associations from the group.\"),\n  groupId: z.string().describe(\"The ID of the group being accessed. This is a required parameter that specifies which group will have brands added to it. The groupId must be a valid, existing group within the specified account. It is typically a string of characters that uniquely identifies the group in the DocuSign system.\"),\n  accountId: z.string().describe(\"The external account number (int) or account ID GUID. This parameter is automatically populated by the DocuSign base action from your authenticated session. It identifies the DocuSign account for which the group brand association is being updated. You typically do not need to provide this value manually as it will be injected automatically.\").optional(),\n}).describe(\"Request schema for `AddExistingBrandToGroup`\");\nconst DocusignAddExistingBrandToGroup_BrandsResponseSchema: z.ZodTypeAny = z.object({\n  brandId: z.string().describe(\"The ID of the brand\").nullable().optional(),\n  brandName: z.string().describe(\"The name of the brand\").nullable().optional(),\n  brandCompany: z.string().describe(\"The company associated with the brand\").nullable().optional(),\n  errorDetails__message: z.string().describe(\"The error message if the operation failed for this brand\").nullable().optional(),\n  errorDetails__errorCode: z.string().describe(\"The error code if the operation failed for this brand\").nullable().optional(),\n}).describe(\"Response schema for individual brand in the response\");\nexport const DocusignAddExistingBrandToGroupOutput: z.ZodTypeAny = z.object({\n  brands: z.array(DocusignAddExistingBrandToGroup_BrandsResponseSchema).describe(\"List of brands that were added to the group\").nullable().optional(),\n}).describe(\"Response schema for `AddExistingBrandToGroup`\");\n\nexport const docusignAddExistingBrandToGroup = action(\"DOCUSIGN_ADD_EXISTING_BRAND_TO_GROUP\", {\n  slug: \"docusign-add-existing-brand-to-group\",\n  name: \"Add existing brand to group\",\n  description: \"This endpoint adds one or more existing brands to a specified group in DocuSign. It allows users to associate multiple brands with a group, enabling customized branding for different groups within an account. The endpoint should be used when there's a need to update the brands associated with a particular group, such as when reorganizing branding strategies or expanding brand options for specific user groups. It's important to note that this endpoint only adds existing brands to a group and does not create new brands or modify brand details.\",\n  input: DocusignAddExistingBrandToGroupInput,\n  output: DocusignAddExistingBrandToGroupOutput,\n});\n"],"mappings":";;;AAIA,MAAa,uCAAqDA,IAAAA,EAAE,OAAO;CACzE,QAAQA,IAAAA,EAAE,MAAMA,IAAAA,EAAE,OAAO,EACzB,SAASA,IAAAA,EAAE,OAAO,CAAC,CAAC,SAAS,qMAAqM,EACpO,CAAC,CAAC,CAAC,SAAS,6BAA6B,CAAC,CAAC,CAAC,SAAS,wSAAwS;CAC3V,SAASA,IAAAA,EAAE,OAAO,CAAC,CAAC,SAAS,uSAAuS;CACpU,WAAWA,IAAAA,EAAE,OAAO,CAAC,CAAC,SAAS,wVAAwV,CAAC,CAAC,SAAS;AACpY,CAAC,CAAC,CAAC,SAAS,8CAA8C;AAC1D,MAAM,uDAAqEA,IAAAA,EAAE,OAAO;CAClF,SAASA,IAAAA,EAAE,OAAO,CAAC,CAAC,SAAS,qBAAqB,CAAC,CAAC,SAAS,CAAC,CAAC,SAAS;CACxE,WAAWA,IAAAA,EAAE,OAAO,CAAC,CAAC,SAAS,uBAAuB,CAAC,CAAC,SAAS,CAAC,CAAC,SAAS;CAC5E,cAAcA,IAAAA,EAAE,OAAO,CAAC,CAAC,SAAS,uCAAuC,CAAC,CAAC,SAAS,CAAC,CAAC,SAAS;CAC/F,uBAAuBA,IAAAA,EAAE,OAAO,CAAC,CAAC,SAAS,0DAA0D,CAAC,CAAC,SAAS,CAAC,CAAC,SAAS;CAC3H,yBAAyBA,IAAAA,EAAE,OAAO,CAAC,CAAC,SAAS,uDAAuD,CAAC,CAAC,SAAS,CAAC,CAAC,SAAS;AAC5H,CAAC,CAAC,CAAC,SAAS,sDAAsD;AAClE,MAAa,wCAAsDA,IAAAA,EAAE,OAAO,EAC1E,QAAQA,IAAAA,EAAE,MAAM,oDAAoD,CAAC,CAAC,SAAS,6CAA6C,CAAC,CAAC,SAAS,CAAC,CAAC,SAAS,EACpJ,CAAC,CAAC,CAAC,SAAS,+CAA+C;AAE3D,MAAa,kCAAkCC,eAAAA,OAAO,wCAAwC;CAC5F,MAAM;CACN,MAAM;CACN,aAAa;CACb,OAAO;CACP,QAAQ;AACV,CAAC"}

package/dist/actions/add-existing-brand-to-group.d.cts

@@ -0,0 +1,9 @@
+import { z } from "zod";
+
+//#region src/actions/add-existing-brand-to-group.d.ts
+declare const DocusignAddExistingBrandToGroupInput: z.ZodTypeAny;
+declare const DocusignAddExistingBrandToGroupOutput: z.ZodTypeAny;
+declare const docusignAddExistingBrandToGroup: import("@keystrokehq/action").WorkflowActionDefinition<unknown, unknown, import("@keystrokehq/shared").ResolvedCredentials<readonly [import("@keystrokehq/shared").Credential]>, readonly [import("@keystrokehq/shared").Credential]>;
+//#endregion
+export { docusignAddExistingBrandToGroup };
+//# sourceMappingURL=add-existing-brand-to-group.d.cts.map

package/dist/actions/add-existing-brand-to-group.d.cts.map

@@ -0,0 +1 @@
+{"version":3,"file":"add-existing-brand-to-group.d.cts","names":[],"sources":["../../src/actions/add-existing-brand-to-group.ts"],"mappings":";;;cAIa,oCAAA,EAAsC,CAAA,CAAE,UAMM;AAAA,cAQ9C,qCAAA,EAAuC,CAAA,CAAE,UAEM;AAAA,cAE/C,+BAAA,gCAA+B,wBAAA,iDAAA,mBAAA,yCAAA,UAAA,4CAAA,UAAA"}

package/dist/actions/add-existing-brand-to-group.d.mts

@@ -0,0 +1,9 @@
+import { z } from "zod";
+
+//#region src/actions/add-existing-brand-to-group.d.ts
+declare const DocusignAddExistingBrandToGroupInput: z.ZodTypeAny;
+declare const DocusignAddExistingBrandToGroupOutput: z.ZodTypeAny;
+declare const docusignAddExistingBrandToGroup: import("@keystrokehq/action").WorkflowActionDefinition<unknown, unknown, import("@keystrokehq/shared").ResolvedCredentials<readonly [import("@keystrokehq/shared").Credential]>, readonly [import("@keystrokehq/shared").Credential]>;
+//#endregion
+export { docusignAddExistingBrandToGroup };
+//# sourceMappingURL=add-existing-brand-to-group.d.mts.map

package/dist/actions/add-existing-brand-to-group.d.mts.map

@@ -0,0 +1 @@
+{"version":3,"file":"add-existing-brand-to-group.d.mts","names":[],"sources":["../../src/actions/add-existing-brand-to-group.ts"],"mappings":";;;cAIa,oCAAA,EAAsC,CAAA,CAAE,UAMM;AAAA,cAQ9C,qCAAA,EAAuC,CAAA,CAAE,UAEM;AAAA,cAE/C,+BAAA,gCAA+B,wBAAA,iDAAA,mBAAA,yCAAA,UAAA,4CAAA,UAAA"}

package/dist/actions/add-existing-brand-to-group.mjs

@@ -0,0 +1,26 @@
+import { action } from "../action.mjs";
+import { z } from "zod";
+//#region src/actions/add-existing-brand-to-group.ts
+const DocusignAddExistingBrandToGroupInput = z.object({
+	brands: z.array(z.object({ brandId: z.string().describe("The unique identifier of the brand to add to the group. This must be an existing brand ID from the account's available brands. You can retrieve available brand IDs using the list brands endpoint.") }).describe("Request schema for `Brands`")).describe("A list of brand objects to add to the group. Each object must contain a valid brandId. This replaces any existing brand assignments for the group, so include all brands that should be associated with the group, not just new ones. An empty list will remove all brand associations from the group."),
+	groupId: z.string().describe("The ID of the group being accessed. This is a required parameter that specifies which group will have brands added to it. The groupId must be a valid, existing group within the specified account. It is typically a string of characters that uniquely identifies the group in the DocuSign system."),
+	accountId: z.string().describe("The external account number (int) or account ID GUID. This parameter is automatically populated by the DocuSign base action from your authenticated session. It identifies the DocuSign account for which the group brand association is being updated. You typically do not need to provide this value manually as it will be injected automatically.").optional()
+}).describe("Request schema for `AddExistingBrandToGroup`");
+const DocusignAddExistingBrandToGroup_BrandsResponseSchema = z.object({
+	brandId: z.string().describe("The ID of the brand").nullable().optional(),
+	brandName: z.string().describe("The name of the brand").nullable().optional(),
+	brandCompany: z.string().describe("The company associated with the brand").nullable().optional(),
+	errorDetails__message: z.string().describe("The error message if the operation failed for this brand").nullable().optional(),
+	errorDetails__errorCode: z.string().describe("The error code if the operation failed for this brand").nullable().optional()
+}).describe("Response schema for individual brand in the response");
+const docusignAddExistingBrandToGroup = action("DOCUSIGN_ADD_EXISTING_BRAND_TO_GROUP", {
+	slug: "docusign-add-existing-brand-to-group",
+	name: "Add existing brand to group",
+	description: "This endpoint adds one or more existing brands to a specified group in DocuSign. It allows users to associate multiple brands with a group, enabling customized branding for different groups within an account. The endpoint should be used when there's a need to update the brands associated with a particular group, such as when reorganizing branding strategies or expanding brand options for specific user groups. It's important to note that this endpoint only adds existing brands to a group and does not create new brands or modify brand details.",
+	input: DocusignAddExistingBrandToGroupInput,
+	output: z.object({ brands: z.array(DocusignAddExistingBrandToGroup_BrandsResponseSchema).describe("List of brands that were added to the group").nullable().optional() }).describe("Response schema for `AddExistingBrandToGroup`")
+});
+//#endregion
+export { docusignAddExistingBrandToGroup };
+
+//# sourceMappingURL=add-existing-brand-to-group.mjs.map

package/dist/actions/add-existing-brand-to-group.mjs.map

@@ -0,0 +1 @@
+{"version":3,"file":"add-existing-brand-to-group.mjs","names":[],"sources":["../../src/actions/add-existing-brand-to-group.ts"],"sourcesContent":["import { z } from \"zod\";\n\nimport { action } from \"../action\";\n\nexport const DocusignAddExistingBrandToGroupInput: z.ZodTypeAny = z.object({\n  brands: z.array(z.object({\n  brandId: z.string().describe(\"The unique identifier of the brand to add to the group. This must be an existing brand ID from the account's available brands. You can retrieve available brand IDs using the list brands endpoint.\"),\n}).describe(\"Request schema for `Brands`\")).describe(\"A list of brand objects to add to the group. Each object must contain a valid brandId. This replaces any existing brand assignments for the group, so include all brands that should be associated with the group, not just new ones. An empty list will remove all brand associations from the group.\"),\n  groupId: z.string().describe(\"The ID of the group being accessed. This is a required parameter that specifies which group will have brands added to it. The groupId must be a valid, existing group within the specified account. It is typically a string of characters that uniquely identifies the group in the DocuSign system.\"),\n  accountId: z.string().describe(\"The external account number (int) or account ID GUID. This parameter is automatically populated by the DocuSign base action from your authenticated session. It identifies the DocuSign account for which the group brand association is being updated. You typically do not need to provide this value manually as it will be injected automatically.\").optional(),\n}).describe(\"Request schema for `AddExistingBrandToGroup`\");\nconst DocusignAddExistingBrandToGroup_BrandsResponseSchema: z.ZodTypeAny = z.object({\n  brandId: z.string().describe(\"The ID of the brand\").nullable().optional(),\n  brandName: z.string().describe(\"The name of the brand\").nullable().optional(),\n  brandCompany: z.string().describe(\"The company associated with the brand\").nullable().optional(),\n  errorDetails__message: z.string().describe(\"The error message if the operation failed for this brand\").nullable().optional(),\n  errorDetails__errorCode: z.string().describe(\"The error code if the operation failed for this brand\").nullable().optional(),\n}).describe(\"Response schema for individual brand in the response\");\nexport const DocusignAddExistingBrandToGroupOutput: z.ZodTypeAny = z.object({\n  brands: z.array(DocusignAddExistingBrandToGroup_BrandsResponseSchema).describe(\"List of brands that were added to the group\").nullable().optional(),\n}).describe(\"Response schema for `AddExistingBrandToGroup`\");\n\nexport const docusignAddExistingBrandToGroup = action(\"DOCUSIGN_ADD_EXISTING_BRAND_TO_GROUP\", {\n  slug: \"docusign-add-existing-brand-to-group\",\n  name: \"Add existing brand to group\",\n  description: \"This endpoint adds one or more existing brands to a specified group in DocuSign. It allows users to associate multiple brands with a group, enabling customized branding for different groups within an account. The endpoint should be used when there's a need to update the brands associated with a particular group, such as when reorganizing branding strategies or expanding brand options for specific user groups. It's important to note that this endpoint only adds existing brands to a group and does not create new brands or modify brand details.\",\n  input: DocusignAddExistingBrandToGroupInput,\n  output: DocusignAddExistingBrandToGroupOutput,\n});\n"],"mappings":";;;AAIA,MAAa,uCAAqD,EAAE,OAAO;CACzE,QAAQ,EAAE,MAAM,EAAE,OAAO,EACzB,SAAS,EAAE,OAAO,CAAC,CAAC,SAAS,qMAAqM,EACpO,CAAC,CAAC,CAAC,SAAS,6BAA6B,CAAC,CAAC,CAAC,SAAS,wSAAwS;CAC3V,SAAS,EAAE,OAAO,CAAC,CAAC,SAAS,uSAAuS;CACpU,WAAW,EAAE,OAAO,CAAC,CAAC,SAAS,wVAAwV,CAAC,CAAC,SAAS;AACpY,CAAC,CAAC,CAAC,SAAS,8CAA8C;AAC1D,MAAM,uDAAqE,EAAE,OAAO;CAClF,SAAS,EAAE,OAAO,CAAC,CAAC,SAAS,qBAAqB,CAAC,CAAC,SAAS,CAAC,CAAC,SAAS;CACxE,WAAW,EAAE,OAAO,CAAC,CAAC,SAAS,uBAAuB,CAAC,CAAC,SAAS,CAAC,CAAC,SAAS;CAC5E,cAAc,EAAE,OAAO,CAAC,CAAC,SAAS,uCAAuC,CAAC,CAAC,SAAS,CAAC,CAAC,SAAS;CAC/F,uBAAuB,EAAE,OAAO,CAAC,CAAC,SAAS,0DAA0D,CAAC,CAAC,SAAS,CAAC,CAAC,SAAS;CAC3H,yBAAyB,EAAE,OAAO,CAAC,CAAC,SAAS,uDAAuD,CAAC,CAAC,SAAS,CAAC,CAAC,SAAS;AAC5H,CAAC,CAAC,CAAC,SAAS,sDAAsD;AAKlE,MAAa,kCAAkC,OAAO,wCAAwC;CAC5F,MAAM;CACN,MAAM;CACN,aAAa;CACb,OAAO;CACP,QATiE,EAAE,OAAO,EAC1E,QAAQ,EAAE,MAAM,oDAAoD,CAAC,CAAC,SAAS,6CAA6C,CAAC,CAAC,SAAS,CAAC,CAAC,SAAS,EACpJ,CAAC,CAAC,CAAC,SAAS,+CAOF;AACV,CAAC"}

package/dist/actions/add-file-to-workspace.cjs

@@ -0,0 +1,33 @@
+const require_action = require("../action.cjs");
+let zod = require("zod");
+//#region src/actions/add-file-to-workspace.ts
+const DocusignAddFileToWorkspaceInput = zod.z.object({
+	file: zod.z.object({
+		name: zod.z.string().describe("The filename that will be used when uploading the file to the destination service"),
+		s3key: zod.z.string().describe("The S3 key of a publicly accessible file, typically returned from a previous download action that stored the file in S3. This key references an existing file that can be uploaded to another service."),
+		mimetype: zod.z.string().describe("The MIME type of the file")
+	}).describe("The file to upload to the workspace folder. The file content will be uploaded to the specified workspace folder."),
+	folderId: zod.z.string().describe("The unique identifier of the folder within the workspace where the file will be added. This parameter is required and must be a valid string representation of the folder ID. The folderId is typically a GUID, for example: \"f1o2l3d4-e5r6-i7d8-9a0b-c1d2e3f4g5h6\". Use \"root\" as a special value to add the file to the root folder of the workspace."),
+	accountId: zod.z.string().describe("The external account number (int) or account ID GUID that uniquely identifies the DocuSign account where the file will be added. This parameter is required and must be a valid string representation of either an integer or a GUID. For example: \"12345\" or \"a1b2c3d4-e5f6-g7h8-i9j0-k1l2m3n4o5p6\".").optional(),
+	workspaceId: zod.z.string().describe("The unique identifier of the workspace where the file will be added. This parameter is required and must be a valid string representation of the workspace ID. The workspaceId is typically a GUID, for example: \"w1x2y3z4-a1b2-c3d4-e5f6-g7h8i9j0k1l2\".")
+}).describe("Request schema for `AddFileToWorkspace`");
+const DocusignAddFileToWorkspaceOutput = zod.z.object({
+	uri: zod.z.string().describe("The URI path to access the uploaded file.").nullable().optional(),
+	data: zod.z.object({}).describe("Additional file metadata returned by the API.").nullable().optional(),
+	name: zod.z.string().describe("The name of the uploaded file.").nullable().optional(),
+	size: zod.z.number().int().describe("The size of the uploaded file in bytes.").nullable().optional(),
+	fileId: zod.z.string().describe("The unique identifier of the uploaded file in the workspace.").nullable().optional(),
+	created: zod.z.string().describe("The UTC datetime when the file was created/uploaded.").nullable().optional(),
+	createdById: zod.z.string().describe("The ID of the user who uploaded the file.").nullable().optional()
+}).describe("Response schema for `AddFileToWorkspace`");
+const docusignAddFileToWorkspace = require_action.action("DOCUSIGN_ADD_FILE_TO_WORKSPACE", {
+	slug: "docusign-add-file-to-workspace",
+	name: "Add file to workspace",
+	description: "This endpoint adds a file to a specific folder within a DocuSign workspace. It allows users to upload and organize files in their DocuSign account, enabling better document management and collaboration. The method should be used when integrating file upload functionality with DocuSign workspaces, such as when adding new documents to a project or sharing files with team members. It's important to note that this endpoint only handles the file addition process and does not provide functions for file modification or deletion.",
+	input: DocusignAddFileToWorkspaceInput,
+	output: DocusignAddFileToWorkspaceOutput
+});
+//#endregion
+exports.docusignAddFileToWorkspace = docusignAddFileToWorkspace;
+
+//# sourceMappingURL=add-file-to-workspace.cjs.map

package/dist/actions/add-file-to-workspace.cjs.map

@@ -0,0 +1 @@
+{"version":3,"file":"add-file-to-workspace.cjs","names":["z","action"],"sources":["../../src/actions/add-file-to-workspace.ts"],"sourcesContent":["import { z } from \"zod\";\n\nimport { action } from \"../action\";\n\nexport const DocusignAddFileToWorkspaceInput: z.ZodTypeAny = z.object({\n  file: z.object({\n  name: z.string().describe(\"The filename that will be used when uploading the file to the destination service\"),\n  s3key: z.string().describe(\"The S3 key of a publicly accessible file, typically returned from a previous download action that stored the file in S3. This key references an existing file that can be uploaded to another service.\"),\n  mimetype: z.string().describe(\"The MIME type of the file\"),\n}).describe(\"The file to upload to the workspace folder. The file content will be uploaded to the specified workspace folder.\"),\n  folderId: z.string().describe(\"The unique identifier of the folder within the workspace where the file will be added. This parameter is required and must be a valid string representation of the folder ID. The folderId is typically a GUID, for example: \\\"f1o2l3d4-e5r6-i7d8-9a0b-c1d2e3f4g5h6\\\". Use \\\"root\\\" as a special value to add the file to the root folder of the workspace.\"),\n  accountId: z.string().describe(\"The external account number (int) or account ID GUID that uniquely identifies the DocuSign account where the file will be added. This parameter is required and must be a valid string representation of either an integer or a GUID. For example: \\\"12345\\\" or \\\"a1b2c3d4-e5f6-g7h8-i9j0-k1l2m3n4o5p6\\\".\").optional(),\n  workspaceId: z.string().describe(\"The unique identifier of the workspace where the file will be added. This parameter is required and must be a valid string representation of the workspace ID. The workspaceId is typically a GUID, for example: \\\"w1x2y3z4-a1b2-c3d4-e5f6-g7h8i9j0k1l2\\\".\"),\n}).describe(\"Request schema for `AddFileToWorkspace`\");\nexport const DocusignAddFileToWorkspaceOutput: z.ZodTypeAny = z.object({\n  uri: z.string().describe(\"The URI path to access the uploaded file.\").nullable().optional(),\n  data: z.object({}).describe(\"Additional file metadata returned by the API.\").nullable().optional(),\n  name: z.string().describe(\"The name of the uploaded file.\").nullable().optional(),\n  size: z.number().int().describe(\"The size of the uploaded file in bytes.\").nullable().optional(),\n  fileId: z.string().describe(\"The unique identifier of the uploaded file in the workspace.\").nullable().optional(),\n  created: z.string().describe(\"The UTC datetime when the file was created/uploaded.\").nullable().optional(),\n  createdById: z.string().describe(\"The ID of the user who uploaded the file.\").nullable().optional(),\n}).describe(\"Response schema for `AddFileToWorkspace`\");\n\nexport const docusignAddFileToWorkspace = action(\"DOCUSIGN_ADD_FILE_TO_WORKSPACE\", {\n  slug: \"docusign-add-file-to-workspace\",\n  name: \"Add file to workspace\",\n  description: \"This endpoint adds a file to a specific folder within a DocuSign workspace. It allows users to upload and organize files in their DocuSign account, enabling better document management and collaboration. The method should be used when integrating file upload functionality with DocuSign workspaces, such as when adding new documents to a project or sharing files with team members. It's important to note that this endpoint only handles the file addition process and does not provide functions for file modification or deletion.\",\n  input: DocusignAddFileToWorkspaceInput,\n  output: DocusignAddFileToWorkspaceOutput,\n});\n"],"mappings":";;;AAIA,MAAa,kCAAgDA,IAAAA,EAAE,OAAO;CACpE,MAAMA,IAAAA,EAAE,OAAO;EACf,MAAMA,IAAAA,EAAE,OAAO,CAAC,CAAC,SAAS,mFAAmF;EAC7G,OAAOA,IAAAA,EAAE,OAAO,CAAC,CAAC,SAAS,wMAAwM;EACnO,UAAUA,IAAAA,EAAE,OAAO,CAAC,CAAC,SAAS,2BAA2B;CAC3D,CAAC,CAAC,CAAC,SAAS,kHAAkH;CAC5H,UAAUA,IAAAA,EAAE,OAAO,CAAC,CAAC,SAAS,6VAA6V;CAC3X,WAAWA,IAAAA,EAAE,OAAO,CAAC,CAAC,SAAS,2SAA2S,CAAC,CAAC,SAAS;CACrV,aAAaA,IAAAA,EAAE,OAAO,CAAC,CAAC,SAAS,4PAA4P;AAC/R,CAAC,CAAC,CAAC,SAAS,yCAAyC;AACrD,MAAa,mCAAiDA,IAAAA,EAAE,OAAO;CACrE,KAAKA,IAAAA,EAAE,OAAO,CAAC,CAAC,SAAS,2CAA2C,CAAC,CAAC,SAAS,CAAC,CAAC,SAAS;CAC1F,MAAMA,IAAAA,EAAE,OAAO,CAAC,CAAC,CAAC,CAAC,SAAS,+CAA+C,CAAC,CAAC,SAAS,CAAC,CAAC,SAAS;CACjG,MAAMA,IAAAA,EAAE,OAAO,CAAC,CAAC,SAAS,gCAAgC,CAAC,CAAC,SAAS,CAAC,CAAC,SAAS;CAChF,MAAMA,IAAAA,EAAE,OAAO,CAAC,CAAC,IAAI,CAAC,CAAC,SAAS,yCAAyC,CAAC,CAAC,SAAS,CAAC,CAAC,SAAS;CAC/F,QAAQA,IAAAA,EAAE,OAAO,CAAC,CAAC,SAAS,8DAA8D,CAAC,CAAC,SAAS,CAAC,CAAC,SAAS;CAChH,SAASA,IAAAA,EAAE,OAAO,CAAC,CAAC,SAAS,sDAAsD,CAAC,CAAC,SAAS,CAAC,CAAC,SAAS;CACzG,aAAaA,IAAAA,EAAE,OAAO,CAAC,CAAC,SAAS,2CAA2C,CAAC,CAAC,SAAS,CAAC,CAAC,SAAS;AACpG,CAAC,CAAC,CAAC,SAAS,0CAA0C;AAEtD,MAAa,6BAA6BC,eAAAA,OAAO,kCAAkC;CACjF,MAAM;CACN,MAAM;CACN,aAAa;CACb,OAAO;CACP,QAAQ;AACV,CAAC"}

package/dist/actions/add-file-to-workspace.d.cts

@@ -0,0 +1,9 @@
+import { z } from "zod";
+
+//#region src/actions/add-file-to-workspace.d.ts
+declare const DocusignAddFileToWorkspaceInput: z.ZodTypeAny;
+declare const DocusignAddFileToWorkspaceOutput: z.ZodTypeAny;
+declare const docusignAddFileToWorkspace: import("@keystrokehq/action").WorkflowActionDefinition<unknown, unknown, import("@keystrokehq/shared").ResolvedCredentials<readonly [import("@keystrokehq/shared").Credential]>, readonly [import("@keystrokehq/shared").Credential]>;
+//#endregion
+export { docusignAddFileToWorkspace };
+//# sourceMappingURL=add-file-to-workspace.d.cts.map

package/dist/actions/add-file-to-workspace.d.cts.map

@@ -0,0 +1 @@
+{"version":3,"file":"add-file-to-workspace.d.cts","names":[],"sources":["../../src/actions/add-file-to-workspace.ts"],"mappings":";;;cAIa,+BAAA,EAAiC,CAAA,CAAE,UASM;AAAA,cACzC,gCAAA,EAAkC,CAAA,CAAE,UAQM;AAAA,cAE1C,0BAAA,gCAA0B,wBAAA,iDAAA,mBAAA,yCAAA,UAAA,4CAAA,UAAA"}

package/dist/actions/add-file-to-workspace.d.mts

@@ -0,0 +1,9 @@
+import { z } from "zod";
+
+//#region src/actions/add-file-to-workspace.d.ts
+declare const DocusignAddFileToWorkspaceInput: z.ZodTypeAny;
+declare const DocusignAddFileToWorkspaceOutput: z.ZodTypeAny;
+declare const docusignAddFileToWorkspace: import("@keystrokehq/action").WorkflowActionDefinition<unknown, unknown, import("@keystrokehq/shared").ResolvedCredentials<readonly [import("@keystrokehq/shared").Credential]>, readonly [import("@keystrokehq/shared").Credential]>;
+//#endregion
+export { docusignAddFileToWorkspace };
+//# sourceMappingURL=add-file-to-workspace.d.mts.map

package/dist/actions/add-file-to-workspace.d.mts.map

@@ -0,0 +1 @@
+{"version":3,"file":"add-file-to-workspace.d.mts","names":[],"sources":["../../src/actions/add-file-to-workspace.ts"],"mappings":";;;cAIa,+BAAA,EAAiC,CAAA,CAAE,UASM;AAAA,cACzC,gCAAA,EAAkC,CAAA,CAAE,UAQM;AAAA,cAE1C,0BAAA,gCAA0B,wBAAA,iDAAA,mBAAA,yCAAA,UAAA,4CAAA,UAAA"}

package/dist/actions/add-file-to-workspace.mjs

@@ -0,0 +1,30 @@
+import { action } from "../action.mjs";
+import { z } from "zod";
+const docusignAddFileToWorkspace = action("DOCUSIGN_ADD_FILE_TO_WORKSPACE", {
+	slug: "docusign-add-file-to-workspace",
+	name: "Add file to workspace",
+	description: "This endpoint adds a file to a specific folder within a DocuSign workspace. It allows users to upload and organize files in their DocuSign account, enabling better document management and collaboration. The method should be used when integrating file upload functionality with DocuSign workspaces, such as when adding new documents to a project or sharing files with team members. It's important to note that this endpoint only handles the file addition process and does not provide functions for file modification or deletion.",
+	input: z.object({
+		file: z.object({
+			name: z.string().describe("The filename that will be used when uploading the file to the destination service"),
+			s3key: z.string().describe("The S3 key of a publicly accessible file, typically returned from a previous download action that stored the file in S3. This key references an existing file that can be uploaded to another service."),
+			mimetype: z.string().describe("The MIME type of the file")
+		}).describe("The file to upload to the workspace folder. The file content will be uploaded to the specified workspace folder."),
+		folderId: z.string().describe("The unique identifier of the folder within the workspace where the file will be added. This parameter is required and must be a valid string representation of the folder ID. The folderId is typically a GUID, for example: \"f1o2l3d4-e5r6-i7d8-9a0b-c1d2e3f4g5h6\". Use \"root\" as a special value to add the file to the root folder of the workspace."),
+		accountId: z.string().describe("The external account number (int) or account ID GUID that uniquely identifies the DocuSign account where the file will be added. This parameter is required and must be a valid string representation of either an integer or a GUID. For example: \"12345\" or \"a1b2c3d4-e5f6-g7h8-i9j0-k1l2m3n4o5p6\".").optional(),
+		workspaceId: z.string().describe("The unique identifier of the workspace where the file will be added. This parameter is required and must be a valid string representation of the workspace ID. The workspaceId is typically a GUID, for example: \"w1x2y3z4-a1b2-c3d4-e5f6-g7h8i9j0k1l2\".")
+	}).describe("Request schema for `AddFileToWorkspace`"),
+	output: z.object({
+		uri: z.string().describe("The URI path to access the uploaded file.").nullable().optional(),
+		data: z.object({}).describe("Additional file metadata returned by the API.").nullable().optional(),
+		name: z.string().describe("The name of the uploaded file.").nullable().optional(),
+		size: z.number().int().describe("The size of the uploaded file in bytes.").nullable().optional(),
+		fileId: z.string().describe("The unique identifier of the uploaded file in the workspace.").nullable().optional(),
+		created: z.string().describe("The UTC datetime when the file was created/uploaded.").nullable().optional(),
+		createdById: z.string().describe("The ID of the user who uploaded the file.").nullable().optional()
+	}).describe("Response schema for `AddFileToWorkspace`")
+});
+//#endregion
+export { docusignAddFileToWorkspace };
+
+//# sourceMappingURL=add-file-to-workspace.mjs.map

package/dist/actions/add-file-to-workspace.mjs.map

@@ -0,0 +1 @@
+{"version":3,"file":"add-file-to-workspace.mjs","names":[],"sources":["../../src/actions/add-file-to-workspace.ts"],"sourcesContent":["import { z } from \"zod\";\n\nimport { action } from \"../action\";\n\nexport const DocusignAddFileToWorkspaceInput: z.ZodTypeAny = z.object({\n  file: z.object({\n  name: z.string().describe(\"The filename that will be used when uploading the file to the destination service\"),\n  s3key: z.string().describe(\"The S3 key of a publicly accessible file, typically returned from a previous download action that stored the file in S3. This key references an existing file that can be uploaded to another service.\"),\n  mimetype: z.string().describe(\"The MIME type of the file\"),\n}).describe(\"The file to upload to the workspace folder. The file content will be uploaded to the specified workspace folder.\"),\n  folderId: z.string().describe(\"The unique identifier of the folder within the workspace where the file will be added. This parameter is required and must be a valid string representation of the folder ID. The folderId is typically a GUID, for example: \\\"f1o2l3d4-e5r6-i7d8-9a0b-c1d2e3f4g5h6\\\". Use \\\"root\\\" as a special value to add the file to the root folder of the workspace.\"),\n  accountId: z.string().describe(\"The external account number (int) or account ID GUID that uniquely identifies the DocuSign account where the file will be added. This parameter is required and must be a valid string representation of either an integer or a GUID. For example: \\\"12345\\\" or \\\"a1b2c3d4-e5f6-g7h8-i9j0-k1l2m3n4o5p6\\\".\").optional(),\n  workspaceId: z.string().describe(\"The unique identifier of the workspace where the file will be added. This parameter is required and must be a valid string representation of the workspace ID. The workspaceId is typically a GUID, for example: \\\"w1x2y3z4-a1b2-c3d4-e5f6-g7h8i9j0k1l2\\\".\"),\n}).describe(\"Request schema for `AddFileToWorkspace`\");\nexport const DocusignAddFileToWorkspaceOutput: z.ZodTypeAny = z.object({\n  uri: z.string().describe(\"The URI path to access the uploaded file.\").nullable().optional(),\n  data: z.object({}).describe(\"Additional file metadata returned by the API.\").nullable().optional(),\n  name: z.string().describe(\"The name of the uploaded file.\").nullable().optional(),\n  size: z.number().int().describe(\"The size of the uploaded file in bytes.\").nullable().optional(),\n  fileId: z.string().describe(\"The unique identifier of the uploaded file in the workspace.\").nullable().optional(),\n  created: z.string().describe(\"The UTC datetime when the file was created/uploaded.\").nullable().optional(),\n  createdById: z.string().describe(\"The ID of the user who uploaded the file.\").nullable().optional(),\n}).describe(\"Response schema for `AddFileToWorkspace`\");\n\nexport const docusignAddFileToWorkspace = action(\"DOCUSIGN_ADD_FILE_TO_WORKSPACE\", {\n  slug: \"docusign-add-file-to-workspace\",\n  name: \"Add file to workspace\",\n  description: \"This endpoint adds a file to a specific folder within a DocuSign workspace. It allows users to upload and organize files in their DocuSign account, enabling better document management and collaboration. The method should be used when integrating file upload functionality with DocuSign workspaces, such as when adding new documents to a project or sharing files with team members. It's important to note that this endpoint only handles the file addition process and does not provide functions for file modification or deletion.\",\n  input: DocusignAddFileToWorkspaceInput,\n  output: DocusignAddFileToWorkspaceOutput,\n});\n"],"mappings":";;AAwBA,MAAa,6BAA6B,OAAO,kCAAkC;CACjF,MAAM;CACN,MAAM;CACN,aAAa;CACb,OAxB2D,EAAE,OAAO;EACpE,MAAM,EAAE,OAAO;GACf,MAAM,EAAE,OAAO,CAAC,CAAC,SAAS,mFAAmF;GAC7G,OAAO,EAAE,OAAO,CAAC,CAAC,SAAS,wMAAwM;GACnO,UAAU,EAAE,OAAO,CAAC,CAAC,SAAS,2BAA2B;EAC3D,CAAC,CAAC,CAAC,SAAS,kHAAkH;EAC5H,UAAU,EAAE,OAAO,CAAC,CAAC,SAAS,6VAA6V;EAC3X,WAAW,EAAE,OAAO,CAAC,CAAC,SAAS,2SAA2S,CAAC,CAAC,SAAS;EACrV,aAAa,EAAE,OAAO,CAAC,CAAC,SAAS,4PAA4P;CAC/R,CAAC,CAAC,CAAC,SAAS,yCAeH;CACP,QAf4D,EAAE,OAAO;EACrE,KAAK,EAAE,OAAO,CAAC,CAAC,SAAS,2CAA2C,CAAC,CAAC,SAAS,CAAC,CAAC,SAAS;EAC1F,MAAM,EAAE,OAAO,CAAC,CAAC,CAAC,CAAC,SAAS,+CAA+C,CAAC,CAAC,SAAS,CAAC,CAAC,SAAS;EACjG,MAAM,EAAE,OAAO,CAAC,CAAC,SAAS,gCAAgC,CAAC,CAAC,SAAS,CAAC,CAAC,SAAS;EAChF,MAAM,EAAE,OAAO,CAAC,CAAC,IAAI,CAAC,CAAC,SAAS,yCAAyC,CAAC,CAAC,SAAS,CAAC,CAAC,SAAS;EAC/F,QAAQ,EAAE,OAAO,CAAC,CAAC,SAAS,8DAA8D,CAAC,CAAC,SAAS,CAAC,CAAC,SAAS;EAChH,SAAS,EAAE,OAAO,CAAC,CAAC,SAAS,sDAAsD,CAAC,CAAC,SAAS,CAAC,CAAC,SAAS;EACzG,aAAa,EAAE,OAAO,CAAC,CAAC,SAAS,2CAA2C,CAAC,CAAC,SAAS,CAAC,CAAC,SAAS;CACpG,CAAC,CAAC,CAAC,SAAS,0CAOF;AACV,CAAC"}

package/dist/actions/add-members-to-signing-group.cjs

@@ -0,0 +1,32 @@
+const require_action = require("../action.cjs");
+let zod = require("zod");
+//#region src/actions/add-members-to-signing-group.ts
+const DocusignAddMembersToSigningGroupInput = zod.z.object({
+	users: zod.z.array(zod.z.object({
+		email: zod.z.string().describe("The email address of the signing group member. Required field when adding members. Must be a valid email format (e.g., user@example.com). This email will be used to identify and contact the member for signing documents.").optional(),
+		userName: zod.z.string().describe("The display name of the group member. Required field when adding members. This is the human-readable name that will appear in the signing group (e.g., 'John Smith', 'Jane Doe'). Maximum length: 100 characters.").optional(),
+		errorDetails__message: zod.z.string().describe("A brief message describing the error condition.").optional(),
+		errorDetails__errorCode: zod.z.string().describe("The code associated with the error condition.").optional()
+	}).describe("Request schema for `Users`")).describe("List of users to add to the signing group. Each user must have an email address and userName. You can add up to 50 members in a single request. Each member should have a valid email address and a display name (userName) with a maximum length of 100 characters.").optional(),
+	accountId: zod.z.string().describe("The external account number (integer) or account ID GUID that uniquely identifies the DocuSign account. This parameter is required and must be provided in the path of the API request. It is used to specify which account the signing group belongs to.").optional(),
+	signingGroupId: zod.z.string().describe("The unique identifier of the signing group to which members will be added. This parameter is required and must be provided in the path of the API request. It should be a string value that corresponds to an existing signing group within the specified account.")
+}).describe("Request schema for `AddMembersToSigningGroup`");
+const DocusignAddMembersToSigningGroup_UsersResponseSchema = zod.z.object({
+	uri: zod.z.string().describe("The URI for accessing the user resource.").nullable().optional(),
+	email: zod.z.string().describe("The email address of the signing group member.").nullable().optional(),
+	userId: zod.z.string().describe("The unique identifier for the user.").nullable().optional(),
+	userName: zod.z.string().describe("The name of the signing group member.").nullable().optional(),
+	errorDetails: zod.z.object({}).describe("Error details if the operation failed for this user.").nullable().optional()
+}).describe("Response schema for users in signing group");
+const DocusignAddMembersToSigningGroupOutput = zod.z.object({ users: zod.z.array(DocusignAddMembersToSigningGroup_UsersResponseSchema).describe("List of users that were added to the signing group.").nullable().optional() }).describe("Response schema for `AddMembersToSigningGroup`");
+const docusignAddMembersToSigningGroup = require_action.action("DOCUSIGN_ADD_MEMBERS_TO_SIGNING_GROUP", {
+	slug: "docusign-add-members-to-signing-group",
+	name: "Add members to signing group",
+	description: "This endpoint adds one or more new members to a specified signing group within a DocuSign account. Signing groups allow multiple users to act as potential signers for a document, where any member of the group can sign on behalf of the group. This tool should be used when you need to expand or update the membership of an existing signing group. The endpoint allows you to add up to 50 members to a signing group, which is the maximum limit. When adding members, you must provide their email addresses and usernames. It's important to note that DocuSign recommends separating signer recipients and non-signer recipients (such as carbon copy recipients) into different signing groups to maintain clarity in the signing process.",
+	input: DocusignAddMembersToSigningGroupInput,
+	output: DocusignAddMembersToSigningGroupOutput
+});
+//#endregion
+exports.docusignAddMembersToSigningGroup = docusignAddMembersToSigningGroup;
+
+//# sourceMappingURL=add-members-to-signing-group.cjs.map