Boloforms ACTION
Send Template Signature
Dispatch a predefined template to obtain a signature. See the documentation
- Action
- Writes data
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Boloforms account once, then configure and run Send Template Signature from your backend or agent.
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: "boloforms-send-template-signature",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
boloforms: { authProvisionId: "apn_xxxxxxx" },
documentId: "Document ID",
subject: "Subject",
},
})
console.log(result)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "boloforms-send-template-signature",
"configured_props": {
"boloforms": { "authProvisionId": "apn_xxxxxxx" },
"documentId": "Document ID",
"subject": "Subject"
}
}'// 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": "boloforms",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// listTools() hands your model this tool's input schema, so it can
// fill the arguments itself:
const result = await mcp.callTool({
name: "boloforms-send-template-signature",
arguments: {
documentId: "Document ID",
subject: "Subject",
},
})SCHEMA
Inputs
Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.
| Property | Type | Description |
|---|---|---|
documentId Document ID | string | The ID of the document. Required Dynamic |
subject Subject | string | The subject will be sent. Required |
message Message | string | The message will be sent. Required |
receiversList Receivers List | string[] | A list of receiver objects. Format: {"name": "Chirag Gupta", "email": "support@boloforms.com", "roleTitle": "Junior Doctor", "roleColour": "#8FB1C8"} roleTitle has to be exactly the same as the role you added or it won't work properly. You can pass a hex code to give a color to your role, but it's not required. Required |
customVariables Custom Variables | string[] | A list of custom variable objects. Format: {"varName": "[v1]", "varValue": "v1 value from api" }. The variable name has to be in square brackets. If you don't pass customVariables then the call will still work, Boloforms will pass each variable as empty. Optional |
REFERENCE
Tool details
Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.
- Registry key
- boloforms-send-template-signature
- Version
- 0.0.3
- App
- Boloforms
- Authentication
- API key
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗