Cometly ACTION
Send Event
Sends an event to the Cometly API. [See the documentation]https://developers.cometly.com/#endpoint-advanced-method)
- Action
- Writes data
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Cometly account once, then configure and run Send Event 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: "cometly-send-event",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
cometly: { authProvisionId: "apn_xxxxxxx" },
eventName: "Event Name",
eventTime: "Event Time",
},
})
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": "cometly-send-event",
"configured_props": {
"cometly": { "authProvisionId": "apn_xxxxxxx" },
"eventName": "Event Name",
"eventTime": "Event Time"
}
}'// 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": "cometly",
},
},
},
)
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: "cometly-send-event",
arguments: {
eventName: "Event Name",
eventTime: "Event Time",
},
})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 |
|---|---|---|
eventName Event Name | string | The event type. Required |
eventTime Event Time | string | Timestamp in UTC timezone. You can use an ISO 8601 formatted string, or a Unix timestamp in milliseconds. Required |
email Email | string | Email associated with the event Required |
ip IP | string | IP address associated with the event Required |
fullName Full Name | string | Full name of the user Optional |
firstName First Name | string | First name of the user Optional |
lastName Last Name | string | Last name of the user Optional |
userAgent User Agent | string | User agent of the user's device Optional |
phone Phone | string | Phone numbers must include a country code to be used for matching (e.g., the number 1 must precede a phone number in the United States). Always include the country code as part of your customers' phone numbers, even if all of your data is from the same country. Optional |
orderId Order ID | string | Order ID for the event Optional |
orderName Order Name | string | Order name for the event Optional |
checkoutToken Checkout Token | string | Checkout token for the event Optional |
amount Amount | integer | Amount for the event 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
- cometly-send-event
- Version
- 0.0.2
- App
- Cometly
- Authentication
- API key
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗