Luma

Live

API KEY

EVENTS

Calendar

Luma gives your agent event operations on your calendar: create events, manage guests and tickets, send email blasts, and organize contacts with tags.

  • Per-user credentials: each call uses the actual user's API key, never a shared bot.
  • Encrypted per-tenant vault: AES-256, resolved at request time, never in LLM context.
  • Scoped before every call: pre-call scope check, 90-day SIEM-exportable audit chain.
Luma
agent · Acme Q3
Run
Which guests are still pending approval for Thursday's AI Builders Meetup?
S
luma_event_guests_list
96ms
Events agent
14 guests are pending approval for AI Builders Meetup. The oldest request came in 6 days ago.
Sources: 1 event, 14 pending guests
luma
14 guests
18:29
Message Claude...

Tools your events agent reaches for on Luma, scoped per user.

CALL ANY TOOL
74 tools for Luma events: create and update events, manage guests, tickets, and coupons, send email blasts, and organize calendar contacts.
luma_calendar_admin_add
Add calendar admin
Add one or more admins to a Luma calendar by email. Returns the calendar's full list of admins after the addition. Use this to grant people admin access to manage a calendar's events and settings; emails already in the admin list are skipped automatically. Use luma_calendar_admins_list to see current admins first.
Parameters
Name
Type
Required
Description
emails
array
Required
Email addresses of the people to make calendar admins, 1 to 20 at a time. Anyone without a Luma account gets one automatically, and new admins are emailed a notification. On a Luma Plus calendar, an addition that would need an extra paid admin seat is rejected, add that admin from the Luma app instead, where the seat charge can be confirmed.
luma_calendar_admins_list
List calendar admins
luma_calendar_coupon_create
Create calendar coupon
luma_calendar_coupon_update
Update calendar coupon
luma_calendar_event_approve
Approve calendar event
luma_calendar_event_reject
Reject calendar event
luma_calendar_get
Get calendar
luma_contact_remove
Remove contact
luma_contact_restore
Restore contact
luma_contact_tag_delete
Delete contact tag
luma_contact_tag_update
Update contact tag
luma_contact_tags_list
List contact tags
luma_contacts_import
Import contacts
luma_event_blast_create
Create event blast
luma_event_cancel
Cancel event
luma_event_coupons_list
List event coupons
luma_event_get
Get event
luma_event_guest_status_update
Update event guest status
luma_event_guests_add
Add event guests
luma_event_guests_send_invites
Event guests send invites
luma_event_host_update
Update event host
luma_event_tag_apply
Apply event tag
luma_event_tag_create
Create event tag
luma_event_tag_delete
Delete event tag
luma_event_ticket_type_get
Get event ticket type
luma_event_ticket_types_list
List event ticket types
luma_event_update
Update event
luma_image_upload_url_create
Create image upload url
luma_images_search
Search images
luma_organization_calendars_list
List organization calendars

For more tools, view docs.

Build your Agent
Same auth pattern across LangChain, OpenAI, Anthropic, and Google ADK.
Python · LlamaIndex
import { ScalekitClient } from "@scalekit-sdk/node";
import { createReactAgent } from "@langchain/langgraph/prebuilt";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

// Luma tools scoped to this user
const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["luma"], toolNames: [
    "luma_event_create",
    "luma_event_guests_list",
    "luma_event_blast_create"] },
  pageSize: 100,
});

const agent = createReactAgent({ llm, tools });
await agent.invoke({ messages: [{ role: "user", content: "List guests pending approval for the AI Builders Meetup" }] });
import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["luma"] }, pageSize: 100,
});

const res = await openai.chat.completions.create({
  model: "gpt-5",
  messages: [{ role: "user", content: "List guests pending approval for the AI Builders Meetup" }],
  tools,
});

// Execute the tool call with the user's vaulted Luma API key
await sk.tools.executeTool(res.choices[0].message.tool_calls[0], "user_123");
import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["luma"] }, pageSize: 100,
});

const msg = await anthropic.messages.create({
  model: "claude-sonnet-5",
  max_tokens: 1024,
  messages: [{ role: "user", content: "List guests pending approval for the AI Builders Meetup" }],
  tools,
});

// Tool call runs with the user's vaulted Luma API key
await sk.tools.executeTool(msg.content, "user_123");
import { Agent } from "@google/adk/agents";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["luma"] }, pageSize: 100,
});

const agent = new Agent({
  name: "events_agent",
  model: "gemini-2.5-pro",
  instruction: "Luma tools scoped to this user",
  tools,
});

await agent.run("List guests pending approval for the AI Builders Meetup");
Try these prompts
Copy any prompt into your agent. Each maps directly to a Luma tool. Click to copy, paste into your agent, done.
Events
Copy the prompt
Copied
Create an event next Thursday at 6pm called AI Builders Meetup.
Copy the prompt
Copied
List events on our calendar for the next 30 days.
Copy the prompt
Copied
Add a paid VIP ticket type to the Launch Party event.
Guests and tickets
Copy the prompt
Copied
List guests pending approval for the AI Builders Meetup.
Copy the prompt
Copied
Approve every pending guest from acme.com for the Launch Party.
Copy the prompt
Copied
Create a LAUNCH20 coupon for 20% off the Launch Party, limited to 50 uses.
Contacts and blasts
Copy the prompt
Copied
Send an email blast to the Launch Party guests tomorrow at 9am.
Copy the prompt
Copied
Tag every contact who attended the March meetup as community.
Copy the prompt
Copied
Import these 40 contacts into our calendar.
SEE HOW AUTH WORKS
Each user connects their own Luma API key once; Scalekit sends it with every call. Keys stay vaulted, every call is scope checked, and every action is logged.
1
Authorize
Your user connects
Luma
once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access
Who:
user ‘A’
when:
Once per user
access:
Limited to user
2
Store
Their
Luma
token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection
vault:
encrypted
scope:
per-user
tokens:
auto-refreshed
3
Resolve
When your agent calls a
Luma
tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs
speed:
~40ms
check:
before every call
seen by:
nobody
4
Audit
Every
Luma
tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it
history:
90 days
export:
SIEM-ready
logged:
every call
Test other agents
See the same per-user auth pattern across other calendar and events connectors.
Support and Ops Teams
Email-to-calendar agent
Reads scheduling intent out of Gmail threads, resolves the times everyone actually has free, and creates the event on the user's own Google Calendar. No shared service account.
Support and Ops Teams
Meeting prep
Pulls agenda, participant context, and open action items before every meeting.
Engineering Teams
Slack triage
Polls Slack for new messages, classifies bugs and support requests with a LangGraph router, files GitHub issues or Zendesk tickets, and confirms in the thread.
GTM and RevOps Teams
Outbound prospecting agent
Searches Apollo for prospects matching your ICP, scores and ranks them, drafts personalized outreach in Gmail, and logs every send to Google Sheets. Mail goes out as the rep, not from a shared inbox.
Test other agents
See the same per-user auth pattern across other calendar and events connectors.
OPS
Email-to-calendar scheduling agent
Read scheduling intent out of Gmail threads, resolve mutual free time, and create the Google Calendar event.
OPS
Meeting prep agent
Assemble the agenda, HubSpot attendee history, and open action items from Gmail before every meeting on the calendar.
ENGINEERING
Slack triage agent
Classify new Slack messages as bugs or support requests, file the GitHub issue or Zendesk ticket, and reply in the thread.
SALES
Outbound prospecting agent
Search Apollo for ICP matches, rank them, draft personalised Gmail outreach, and log every send to Google Sheets.
Why Scalekit
Secure your agent's access. Connectors ship in minutes
01.
Shared tokens break per-user analytics
A shared Luma API key looks fine in a demo. In production every guest approval looks like one service account, and you cannot tell which user triggered it. Scalekit resolves the credential of the actual user who triggered the agent, never a shared bot.
// shared key
audit → bot_service_account

// scalekit
audit → user_abc ✓
02.
Authentication is not authorization
03.
Multi-tenancy is architectural
04.
Luma today. Ten connectors tomorrow.
“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”
Venu Madhav Kattagoni
Head of Engineering / Von
FAQs
Frequently Asked Questions
Does the agent access Luma as the user or through a shared key?
As the user. Each user connects their own Luma API key once, and Scalekit sends it with every call. Audit logs attribute every event change and email blast to that user, not a shared service account.
Where is the Luma API key stored?
In Scalekit's managed AES-256 token vault, namespaced per tenant. To rotate it, the user reconnects with a new API key. Revocation is a single dashboard action. Credentials never appear in prompts, logs, or LLM context.
Can I limit what the agent does in Luma?
Yes. Filter by tool name in listScopedTools to expose only what you want, for example guest and ticket tools without luma_event_cancel, which permanently deletes an event and notifies every guest. Scalekit also enforces scope checks before every API call.
What happens when a user revokes Luma access?
The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.
Which Luma calendar does the agent work on?
The calendar the user's Luma API key is scoped to. Event, guest, contact, and tag tools act on that calendar, and the organization tools such as luma_organization_events_list reach the other calendars in the Luma organization that owns it.
Start in your coding agent
Up and running in one command
Install the Scalekit skill in your editor of choice. Connector, auth, tools, prompt, all wired up
Claude Code REPL
/plugin marketplace add scalekit-inc/claude-code-authstack
/plugin install agentkit@scalekit-auth-stack
Cursor Code REPL
# ~/.cursor/mcp.json
{
""mcpServers"": {
""luma"": {
""url"": ""https://mcp.scalekit.com/luma"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.luma]
url = ""https://mcp.scalekit.com/luma""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""luma"": {
""url"": ""https://mcp.scalekit.com/luma"",
""type"": ""http""
}
}
}