Cardly ACTION
Create Contact
Creates a new contact in Cardly. See the documentation
- Action
- Writes data
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Cardly account once, then configure and run Create Contact 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-create-contact",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
cardly: { authProvisionId: "apn_xxxxxxx" },
listId: "List",
firstName: "First Name",
},
})
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-create-contact",
"configured_props": {
"cardly": { "authProvisionId": "apn_xxxxxxx" },
"listId": "List",
"firstName": "First Name"
}
}'// 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-create-contact",
arguments: {
listId: "List",
firstName: "First Name",
},
})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 |
|---|---|---|
listId List | string | Identifier of a contact list Required Dynamic |
firstName First Name | string | The first name of a contact. Required |
lastName Last Name | string | The last name of a contact, if known / applicable. Optional |
email Email | string | An email address for this contact, if supplied, which can be used to uniquely identify this contact for subsequent actions. Optional |
company Company | string | The company a contact belongs to, if required. Optional |
address Address | string | The primary address line, including street number, name and type. Required |
address2 Address 2 | string | A secondary address line, typically containing a unit, apartment, suite number etc. Optional |
locality Locality | string | A suburb or city for the contact. Required |
region Region | string | The state or province for this address. Required |
country Country | string | A 2-character ISO code identifying the contact's country. Required |
postcode Postcode | string | A postal code or ZIP code for this contact, where required by local addressing formats. Required |
externalId External ID | string | Any external identifier you have supplied for this contact which can be used to update this contact in future calls. 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
- cardly-create-contact
- Version
- 0.0.2
- App
- Cardly
- Authentication
- API key
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗