← Docusign

New Folder from Docusign API

Pipedream makes it easy to connect APIs for Docusign and + other apps remarkably fast.

Trigger workflow on
New Folder from the Docusign API
Next, do this
Connect to 500+ APIs using code and no-code building blocks
No credit card required
Trusted by 200,000+ developers from startups to Fortune 500 companies:
Trusted by 200,000+ developers from startups to Fortune 500 companies

Developers Pipedream

Getting Started

Trigger a workflow on New Folder with Docusign API. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

  1. Configure the New Folder trigger
    1. Connect your Docusign account
    2. Configure timer
    3. Select a Account
    4. Select one or more Folder types
  2. Add steps to connect to + APIs using code and no-code building blocks
  3. Deploy the workflow
  4. Send a test event to validate your setup
  5. Turn on the trigger

Details

This is a pre-built, open source component from Pipedream's GitHub repo. The component is developed by Pipedream and the community, and verified and maintained by Pipedream.

To contribute an update to an existing component or create a new component, create a PR on GitHub. If you're new to Pipedream component development, you can start with quickstarts for trigger span and action development, and then review the component API reference.

New Folder on Docusign
Description:Emits an event when a new folder is created
Version:0.0.2
Key:docusign-new-folder

Code

const docusign = require("../../docusign.app.js");

module.exports = {
  key: "docusign-new-folder",
  name: "New Folder",
  description: "Emits an event when a new folder is created",
  version: "0.0.2",
  dedupe: "unique",
  props: {
    docusign,
    db: "$.service.db",
    timer: {
      type: "$.interface.timer",
      default: {
        intervalSeconds: 60 * 15,
      },
    },
    account: {
      propDefinition: [
        docusign,
        "account",
      ],
    },
    include: {
      type: "string[]",
      label: "Folder types",
      description: "Folder types to include in the response",
      options: [
        "envelope_folders",
        "template_folders",
        "shared_template_folders",
      ],
      default: [
        "envelope_folders",
        "template_folders",
        "shared_template_folders",
      ],
    },
  },
  methods: {
    async processFolders(baseUri, params, folders, ts) {
      for (const folder of folders) {
        if (folder.hasSubFolders == "true") {
          for (const subfolder of folder.folders) {
            let done = false;
            do {
              const {
                folders: subfolders,
                nextUri,
                resultSetSize,
              } = await this.docusign.listFolderItems(baseUri, params, subfolder.folderId);
              await this.processFolders(baseUri, params, subfolders, ts);
              if (nextUri) params.start_postion += resultSetSize + 1;
              else done = true;
            } while (!done);
          }
        }
        const meta = this.generateMeta(folder, ts);
        this.$emit(folder, meta);
      }
    },
    generateMeta({
      folderId: id, name: summary,
    }, ts) {
      return {
        id,
        summary,
        ts,
      };
    },
  },
  async run(event) {
    const { timestamp: ts } = event;
    const baseUri =  await this.docusign.getBaseUri(this.account);
    let done = false;
    const params = {
      start_position: 0,
      include: (this.include).join(),
      include_items: true,
    };
    do {
      const {
        folders = [],
        nextUri,
        resultSetSize,
      } = await this.docusign.listFolders(baseUri, params);
      if (nextUri) params.start_position += resultSetSize + 1;
      else done = true;

      await this.processFolders(baseUri, params, folders, ts);

    } while (!done);
  },
};

Configuration

This component may be configured based on the props defined in the component code. Pipedream automatically prompts for input values in the UI and CLI.
LabelPropTypeDescription
DocusigndocusignappThis component uses the Docusign app.
N/Adb$.service.dbThis component uses $.service.db to maintain state between component invocations.
timer$.interface.timer
AccountaccountstringSelect a value from the drop down menu.
Folder typesincludestring[]Select a value from the drop down menu:envelope_folderstemplate_foldersshared_template_folders

Authentication

Docusign uses OAuth authentication. When you connect your Docusign account, Pipedream will open a popup window where you can sign into Docusign and grant Pipedream permission to connect to your account. Pipedream securely stores and automatically refreshes the OAuth tokens so you can easily authenticate any Docusign API.

Pipedream requests the following authorization scopes when you connect your account:

signatureextendedopenid

About Docusign

Electronic Signature and Agreement Cloud

About Pipedream

Stop writing boilerplate code, struggling with authentication and managing infrastructure. Start connecting APIs with code-level control when you need it — and no code when you don't.

Into to Pipedream
Watch us build a workflow
Watch us build a workflow
4 min
Watch now ➜
"The past few weeks, I truly feel like the clichéd 10x engineer."
@heyellieday
Powerful features that scale
Manage concurrency and execution rate
Manage concurrency and execution rate

Queue up to 10,000 events per workfow and manage the concurrency and rate at which workflows are triggered.

Process large payloads up to 5 terabytes
Process large payloads up to 5 terabytes

Large file support enables you to trigger workflows with any data (e.g., large JSON files, images and videos) up to 5 terabytes.

Return custom responses to HTTP requests
Return custom responses to HTTP requests

Return any JSON-serializable response from an HTTP triggered workflow using $respond().

Use most npm packages
Use most npm packages

To use any npm package, just require() it -- there's no npm install or package.json required.

Maintain state between executions
Maintain state between executions

Use $checkpoint to save state in one workflow invocation and read it the next time your workflow runs.

Pass data between steps
Pass data between steps

Return data from any step to inspect it in a human-friendly way and reference the data in future steps via the steps object.