Arlo ACTION
Create Event
Create a new scheduled Arlo Event by submitting an event import request. Provide the parent template
Code (not its numeric ID) and one or more sessions. The Arlo API processes this asynchronously and returns an AsyncTaskID; the created event starts in Draft status. Run List Event Templates to find the template Code. Example: call with templateCode: "SP1", sessions: '[{"Name":"Day 1","StartDateTime":"2026-09-15T09:00:00+12:00","EndDateTime":"2026-09-15T17:00:00+12:00"}]' to schedule one session under that template. See the documentation.- Action
- Writes data
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Arlo account once, then configure and run Create 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: "arlo-create-event",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
arlo: { authProvisionId: "apn_xxxxxxx" },
templateCode: "Template Code",
sessions: "Sessions",
},
})
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": "arlo-create-event",
"configured_props": {
"arlo": { "authProvisionId": "apn_xxxxxxx" },
"templateCode": "Template Code",
"sessions": "Sessions"
}
}'// 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": "arlo",
},
},
},
)
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: "arlo-create-event",
arguments: {
templateCode: "Template Code",
sessions: "Sessions",
},
})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 |
|---|---|---|
templateCode Template Code | string | The Code (short string identifier) of the EventTemplate this event belongs to. Run List Event Templates to find the template Code. Required |
sessions Sessions | string | JSON array of session objects. Each session requires Name, StartDateTime, and EndDateTime in ISO 8601 with UTC offset. Optional per session: TimeZoneId, PresenterIds (array of integer contact IDs), VenueDetails ({"VenueId": 123} — run List Venues to find valid venue IDs). Example: [{"Name":"Day 1","StartDateTime":"2026-09-15T09:00:00+12:00","EndDateTime":"2026-09-15T17:00:00+12:00","VenueDetails":{"VenueId":123}}]. Required |
name Name | string | Optional display name for the event. Optional |
locationName Location Name | string | Optional location name for the event. Optional |
registrationMethod Registration Method | string | Optional. The registration method to apply in the event's RegistrationSettings (e.g. OrderProcess). 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
- arlo-create-event
- Version
- 0.0.2
- App
- Arlo
- Authentication
- API key
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗