Luma Tools

Integrate Luma event management into your workflows to create and update events, fetch event details, list calendar events, retrieve guest lists, and add guests. Use these tools to automate event operations and connect Luma data to other steps in your workflow.

Overview

Operations

Configuration

luma_get_event

luma_create_event

luma_update_event

luma_list_events

luma_get_guests

luma_add_guests

Outputs

luma_get_event

• event (json) — Event details (id, name, startAt, endAt, timezone, createdAt, description, coverUrl, url, visibility, meetingUrl)
• hosts (json) — Event hosts (id, name, firstName, lastName, email, avatarUrl)

luma_create_event

• event (json) — Created event details
• hosts (json) — Event hosts

luma_update_event

• event (json) — Updated event details
• hosts (json) — Event hosts

luma_list_events

• events (json) — List of events
• hasMore (boolean) — Whether there are more events
• nextCursor (string) — Cursor for next page

luma_get_guests

• guests (json) — List of guests (id, email, name, firstName, lastName, approvalStatus, registeredAt, invitedAt, joinedAt, checkedInAt, phoneNumber)
• hasMore (boolean) — Whether there are more guests
• nextCursor (string) — Cursor for next page

luma_add_guests

• guests (json) — Added guests

YAML Example

luma_1:
  type: luma
  name: "Luma"
  inputs:
    operation: "luma_create_event"
    name: "Product Launch Meetup"
    start_at: "2026-07-15T18:00:00Z"
    timezone: "America/New_York"
    end_at: "2026-07-15T20:00:00Z"
    description_md: "Join us for the launch of our new product."
    visibility: "public"
    apiKey: "{{LUMA_API_KEY}}"
  connections:
    outgoing:
      - target: next-block-id

Tips

• Authentication uses your Luma API key, sent as the x-luma-api-key request header. Generate it from your Luma calendar settings under the API section, and store it as an environment variable referenced via {{LUMA_API_KEY}}.
• Event IDs start with the evt- prefix and are returned in the event.id field. Chain operations by passing a created event's ID into a later block, e.g. {{luma_1.event.id}}.
• For luma_add_guests, the guests parameter must be a valid JSON array string such as [{"email": "user@example.com", "name": "John Doe"}]. Each guest requires an email; name, first_name, and last_name are optional.
• luma_list_events and luma_get_guests are paginated — when hasMore is true, pass the returned nextCursor into pagination_cursor on the next call to fetch the following page.