Luma: Post V1 Events Guests Add

Add guests to the event.

Tool ID: luma_post_v1_events_guests_add

Run this action

Use the TypeScript SDK for a single call. Put ctx.tools.execute(...) inside a Play when the call should be durable, scheduled, or run across a CSV.

import { Deepline } from 'deepline';

const deepline = await Deepline.connect();
const result = await deepline.tools.execute(
  'luma_post_v1_events_guests_add',
  {
    "event_id": "event_123",
    "guests": [
      {
        "email": "jane.doe@example.com"
      }
    ]
  },
);

console.log(result.toolResponse.raw);

CLI

deepline tools execute luma_post_v1_events_guests_add --input '{
  "event_id": "event_123",
  "guests": [
    {
      "email": "jane.doe@example.com"
    }
  ]
}' --json

Example response

The SDK exposes this shape at result.toolResponse.raw. Values below are representative.

{
  "data": {
    "skipped": [
      {
        "email": "jane.doe@example.com"
      }
    ]
  }
}

Use deepline tools get luma_post_v1_events_guests_add --json for the latest machine-readable contract.

Input reference

Add guests to the event. By default, guests are added with the status “Going” (approved) and receive one ticket of the default ticket type. Use the ticket or tickets parameter to specify custom ticket assignments. Get available ticket types using /v1/events/ticket-types/list. Use approval_status to add guests as pending approval or on the waitlist instead of immediately approved. Use registration_answers on each guest to record answers to the event’s registration questions — question IDs come from the registration_questions field of Get Event. Guests are added in the background; the response lists any guests that will be skipped because they unsubscribed from your calendar, were removed by an admin, or blocked you.

Name	Type	Required	Default	Details
`payload.event_id`	`string`	Yes	—	Event ID, this usually starts with evt-
`payload.guests`	`array`	Yes	—	—
`payload.ticket`	`object`	No	—	Optional. Assign a single ticket of the specified type to each guest. Cannot be used with `tickets` parameter.
`payload.tickets`	`array`	No	—	Optional. Assign multiple tickets to each guest. Each guest receives all tickets in the array. Use this to add multiple tickets of the same or different types. Cannot be used with `ticket` parameter.
`payload.approval_status`	`"approved" \| "pending_approval" \| "waitlist"`	No	—	Optional. Status to assign to each added guest. Defaults to `approved` (“Going”). Use `pending_approval` to add guests for host review, or `waitlist` to add to the event waitlist. To send a soft invite that guests can accept, use `/v1/events/guests/send-invites` instead. Allowed: `approved`, `pending_approval`, `waitlist`.
`payload.send_email`	`boolean`	No	—	Optional. Whether Luma should email each added guest. Defaults to true. Set to false if your integration sends its own notifications.

Output reference

Standard tool result payload.

Name	Type	Required	Default	Details
`result.data`	`object`	Yes	—	Provider response payload.
`result.data.skipped`	`array`	Yes	—	Guests that won’t be added because they unsubscribed from your calendar, were removed or blocked by a calendar admin, or there is a block between you and them. Everyone else in the request is processed.
`result.data.skipped[].email`	`string`	Yes	—	—
`result.meta`	`object`	No	—	Additional response metadata (status, paging).

Deepline cost

Pricing model: fixed (per call).
Estimated Deepline credits: 0 per pricing unit.
Provider-native pricing may still exist outside Deepline credit billing.

Get started

Build and automate

Common workflows

Data and integrations

Reference

Luma: Post V1 Events Guests Add

Run this action

CLI

Example response

Input reference

Output reference

Deepline cost

​Run this action

​CLI

​Example response

​Input reference

​Output reference

​Deepline cost

​Related documentation

Run this action

CLI

Example response

Input reference

Output reference

Deepline cost

Related documentation