Luma ACTION
Add Guests
Add guests to a Luma event with status
Going. Guests receive the default ticket type unless Ticket JSON or Tickets JSON is provided. Use List Events first if you need to find the event ID, and List Ticket Types if assigning custom tickets. See the documentation- Action
- Writes data
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Luma account once, then configure and run Add Guests 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: "luma-add-guests",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
luma: { authProvisionId: "apn_xxxxxxx" },
eventId: "Event ID",
guestsJson: "Guests",
},
})
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": "luma-add-guests",
"configured_props": {
"luma": { "authProvisionId": "apn_xxxxxxx" },
"eventId": "Event ID",
"guestsJson": "Guests"
}
}'// 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": "luma",
},
},
},
)
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: "luma-add-guests",
arguments: {
eventId: "Event ID",
guestsJson: "Guests",
},
})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 |
|---|---|---|
eventId Event ID | string | The Luma event ID. Event IDs usually start with evt-. Required Dynamic |
guestsJson Guests | string | A JSON array of guests. Example: [{"email":"jane@example.com","name":"Jane Doe"}]. Required |
ticketJson Ticket JSON | string | Optional JSON object assigning one ticket type to each guest. Cannot be used with Tickets JSON. Example: {"ticket_type_id":"tt-123"}. Optional |
ticketsJson Tickets JSON | string | Optional JSON array assigning multiple tickets to each guest. Cannot be used with Ticket JSON. Example: [{"ticket_type_id":"tt-123"}]. 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
- luma-add-guests
- Version
- 0.0.2
- App
- Luma
- Authentication
- API key
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗