[Data] Parse JSON with Formatting API on New Folder from Docusign Developer API

Pipedream makes it easy to connect APIs for Formatting, Docusign Developer and 2,000+ other apps remarkably fast.

Trigger workflow on

New Folder from the Docusign Developer API

Next, do this

[Data] Parse JSON with the Formatting API

No credit card required

▶

Watch us build a workflow

4 min

Watch now ➜

Trusted by 800,000+ developers from startups to Fortune 500 companies

Developers ♥ Pipedream

Getting Started#

This integration creates a workflow with a Docusign Developer trigger and Formatting action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the New Folder trigger
1. Connect your Docusign Developer account
2. Select a Account
3. Configure Polling Interval
4. Select one or more Folder types
Configure the [Data] Parse JSON action
1. Connect your Formatting account
2. Configure Input
Deploy the workflow
Send a test event to validate your setup
Turn on the trigger

Details#

This integration uses pre-built, source-available components from Pipedream's GitHub repo. These components are 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.

Trigger#

New Folder on Docusign Developer

Description:Emit new event when a new folder is created

Version:0.0.2

Key:docusign_developer-new-folder

View on GitHub

Docusign Developer Overview#

With the Docusign Developer API, you can build applications that allow users to
electronically sign documents, track the status of documents, and manage
document workflows. Here are some examples of what you can build:

An application that allows users to electronically sign documents
An application that tracks the status of documents
An application that manages document workflows

Trigger Code#

import docusign from "../../docusign_developer.app.mjs";
import common from "../../../docusign/sources/new-folder/common.mjs";

export default {
  ...common,
  key: "docusign_developer-new-folder",
  version: "0.0.2",
  name: "New Folder",
  description: "Emit new event when a new folder is created",
  type: "source",
  props: {
    docusign,
    account: {
      propDefinition: [
        docusign,
        "account",
      ],
    },
    ...common.props,
  },
};

Trigger 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.

Label	Prop	Type	Description
Docusign Developer	`docusign`	`app`	This component uses the Docusign Developer app.
Account	`account`	`string`	Select a value from the drop down menu.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
Polling Interval	`timer`	`$.interface.timer`	Pipedream will poll the Docusign API on this schedule
Folder types	`include`	`string[]`	Select a value from the drop down menu:`envelope_folderstemplate_foldersshared_template_folders`

Trigger Authentication#

Docusign Developer uses OAuth authentication. When you connect your Docusign Developer account, Pipedream will open a popup window where you can sign into Docusign Developer 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 Developer API.

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

signatureextendedopenid

About Docusign Developer#

Electronic Signature and Agreement Cloud (for developers)

Action#

[Data] Parse JSON on Formatting

Description:Parse a JSON string

Version:0.0.4

Key:formatting-parse-json

View on GitHub

Action Code#

import { defineAction } from "@pipedream/types";
import app from "../../app/formatting.app.mjs";
export default defineAction({
    name: "[Data] Parse JSON",
    description: "Parse a JSON string",
    key: "formatting-parse-json",
    version: "0.0.4",
    type: "action",
    props: {
        app,
        input: {
            label: "Input",
            description: "A valid JSON format string to be parsed.",
            type: "string",
        },
    },
    async run({ $ }) {
        try {
            const result = JSON.parse(this.input);
            $.export("$summary", "Successfully parsed JSON string");
            return result;
        }
        catch (err) {
            throw new Error("Error parsing input as JSON: " + err.toString());
        }
    },
});