IMPLEMENTATION
Call this tool
Connect a user's Cardly account once, then configure and run Send Card 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: "cardly-send-card",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
cardly: { authProvisionId: "apn_xxxxxxx" },
artId: "Art",
templateId: "Template",
},
})
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": "cardly-send-card",
"configured_props": {
"cardly": { "authProvisionId": "apn_xxxxxxx" },
"artId": "Art",
"templateId": "Template"
}
}'// 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": "cardly",
},
},
},
)
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: "cardly-send-card",
arguments: {
artId: "Art",
templateId: "Template",
},
})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 |
|---|---|---|
artId Art | string | Identifier of artwork Required Dynamic |
templateId Template | string | Identifier of a template Optional Dynamic |
firstName First Name | string | The recipient's first name, as it should appear on the envelope. Required |
lastName Last Name | string | The recipient's last name, as it should appear on the envelope. Optional |
company Company | string | The recipient's company, if required, as it should appear below their name on the envelope. Optional |
address Address | string | The recipient's street number, name and type. Required |
address2 Address 2 | string | Unit, floor, apartment etc. additional information for the recipient's address. Optional |
city City | string | Suburb or city for the recipient. Required |
region Region | string | State / province / region for the recipient, if required. UK and NZ currently do not require a region specified. Conditionally required based on the country supplied. Required |
country Country | string | The 2-character ISO code for the country relating to this recipient. Required |
postcode Postcode | string | The postcode for this recipient. Note that this may be empty for countries that do not utilise postcodes. 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
- cardly-send-card
- Version
- 0.0.2
- App
- Cardly
- Authentication
- API key
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗