BoldSign icon

CONNECT APP

Build with BoldSign

Electronic Signature Software & API

CRM

  • OAuth

MCP

Give your agent BoldSign tools

Every BoldSign action is exposed as an MCP tool on Pipedream's remote server. Point a client at it with your end user's ID and Connect resolves that user's BoldSign account for each tool call — you store no tokens.

// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
  new URL("https://remote.mcp.pipedream.net/v3"),
  {
    requestInit: {
      headers: {
        Authorization: `Bearer ${accessToken}`,
        "x-pd-project-id": "{project_id}",
        "x-pd-environment": "production",
        "x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
        "x-pd-app-slug": "boldsign",
      },
    },
  },
)

const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)

const { tools } = await mcp.listTools()

// e.g. run List Brand ID Options:
const result = await mcp.callTool({
  name: "boldsign-list-brand-id-options",
  arguments: {},
})

API PROXY

Call the BoldSign API directly

For an endpoint with no pre-built tool, the Connect proxy forwards your request to the BoldSign API with the connected user's credentials attached. You store no tokens and write no refresh logic.

const resp = await pd.proxy.get({
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  accountId: "apn_xxxxxxx",
  url: "https://api.boldsign.com/v1/users/list",
})

// Any allowed BoldSign endpoint works here. Pipedream attaches the
// connected account's credentials to the outgoing request.

SDK

Run BoldSign actions from your backend

Connect a user's BoldSign account once, then run List Brand ID Options on their behalf from your own code — TypeScript, Python, or plain HTTP.

import { PipedreamClient } from "@pipedream/sdk"

const pd = new PipedreamClient({
  projectId: process.env.PIPEDREAM_PROJECT_ID!,
  clientId: process.env.PIPEDREAM_CLIENT_ID!,
  clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
  projectEnvironment: "production",
})

const result = await pd.actions.run({
  id: "boldsign-list-brand-id-options",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    boldsign: { authProvisionId: "apn_xxxxxxx" },
  },
})

REFERENCE

App details

Reference metadata for the BoldSign connector in the Pipedream registry.

App slug
boldsign
Authentication
OAuth
Categories
CRM
Actions
5
Triggers
3
API proxy
Available

OAuth scopes

These are the scopes Pipedream's managed BoldSign OAuth client requests when one of your users connects an account. Supply your own OAuth client to request a different set.

  • offline_access
  • BoldSign.Users.Read
  • BoldSign.Documents.Write
  • BoldSign.Documents.Create
  • BoldSign.Templates.Read
  • BoldSign.Templates.Write
  • BoldSign.Templates.Create
  • BoldSign.SenderIdentity.Read
  • BoldSign.Documents.Read
  • BoldSign.Contacts.Read