robly ACTION
Create Contact
- Action
- Writes data
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's robly 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: "robly-create-contact",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
robly: { authProvisionId: "apn_xxxxxxx" },
email: "Email",
autogenerateFields: true,
},
})
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": "robly-create-contact",
"configured_props": {
"robly": { "authProvisionId": "apn_xxxxxxx" },
"email": "Email",
"autogenerateFields": true
}
}'// 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": "robly",
},
},
},
)
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: "robly-create-contact",
arguments: {
email: "Email",
autogenerateFields: true,
},
})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 |
|---|---|---|
email Email | string | Email address of the contact Required |
autogenerateFields Autogenerate Fields | boolean | When true, field tags will be autogenerated based on the parameters sent into the request Optional |
doubleOptIn Double Opt-In | boolean | When true, the welcome email will be sent to the member Optional |
fieldTags Field Tags | object | The field tags are sent in as parameters based on the name of the field. These fields are configured when your account is setup, and should correspond to fields that already exist in the account configuration. For example, if you have a custom field for Invalid fields will be ignored, and could throw an HTTP 500 server error. Optional |
includeAutomations Include Automations | boolean | When true, automations are updated with the new member Optional |
includeAutoresponder Include Autoresponder | boolean | When true, sends the autoresponder email on the sub_lists that the new member has been subscribed to Optional |
subLists Sub Lists | integer[] | Array of sub-list IDs to add the contact to Optional Dynamic |
welcomeEmail Welcome Email | boolean | When true, the welcome email for the sign up process is sent 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
- robly-create-contact
- Version
- 0.0.1
- App
- robly
- Authentication
- API key
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗