TemplateDocs ACTION
Generate Document
Generate a document by merging data with a template's placeholders. Returns the document as a file saved to
/tmp. See the documentation- Action
- Writes data
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's TemplateDocs account once, then configure and run Generate Document 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: "templatedocs-generate-document",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
templatedocs: { authProvisionId: "apn_xxxxxxx" },
templateId: "Template",
format: "Output Format",
},
})
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": "templatedocs-generate-document",
"configured_props": {
"templatedocs": { "authProvisionId": "apn_xxxxxxx" },
"templateId": "Template",
"format": "Output Format"
}
}'// 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": "templatedocs",
},
},
},
)
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: "templatedocs-generate-document",
arguments: {
templateId: "Template",
format: "Output Format",
},
})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 |
|---|---|---|
templateId Template | string | The unique identifier of the template Required Dynamic |
format Output Format | string | The output format of the generated document. Defaults to docx. Optional |
outputFilename Output Filename | string | Custom filename for the generated file (e.g. invoice.pdf). If not specified, defaults to generated-document.docx or generated-document.pdf. The file is saved to the /tmp directory. Optional |
emailTo Email To | string[] | Primary recipients to email the generated document to. Optional |
emailCc Email CC | string[] | Carbon copy recipients for email delivery. Optional |
emailBcc Email BCC | string[] | Blind carbon copy recipients for email delivery. Optional |
emailSubject Email Subject | string | Custom subject line for email delivery. Optional |
emailBody Email Body | string | Text or HTML body content for email delivery. Optional |
syncDir SyncDir | dir | Required |
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
- templatedocs-generate-document
- Version
- 0.0.1
- App
- TemplateDocs
- Authentication
- API key
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗