Actionist·Luma
Luma

Luma

· #288 most-used

Host memorable events and grow your community on autopilot

MarketingCommunicationProductivitySchedulingAutomationCommunity

Luma is the event management platform used by communities, startups, and enterprises to host memorable events — from small invite-only gatherings to large public conferences with paid ticketing. Connect it to Actionist and your agents can create and update events directly from your planning tools, sync registrants to your CRM within about a minute of sign-up, send personalised invitations to specific guests, grow your Luma calendar community from any form or tool, and log ticket revenue to your finance tracker in near real-time — all without logging into the Luma dashboard.

Try Luma with ActionistVisit Luma
Average time saved
10 hours
per person · per month
≈ 1 workdays back

Eliminates manual work. Agents eliminate the manual cycle of exporting guest lists, creating events from planning docs, cross-posting announcements, and reconciling attendance data across multiple tools after each event.

Schedule

What your Luma agent runs on autopilot

A week of scheduled jobs your Actionist agent will execute on your behalf.

28Scheduled jobs
7Agents at work
24/7Always on
Agents
Tue–Thu
Tue
Wed
Thu
7a
8a
9a
10a
11a
12p
1p
2p
3p
4p
5p
6p
Multi-app workflows

Luma × every other app you use

End-to-end automations that span multiple apps — each one a real business outcome.

6Workflows
7Apps spanned
~31 hrsSaved / week
6Personas served
For sales
Featured3 apps

New Luma registrant synced to CRM within minutes

Within about a minute of a guest registering for a Luma event, the agent looks them up in HubSpot, creates or updates their contact record with an event tag, assigns a follow-up task to the account executive, and sends a Slack alert if the registrant is flagged as a priority prospect. Every registration becomes a pipeline entry automatically.

~10 hrs

Time saved for your team — every week, on autopilot

The flow
Trigger·When a guest registers for a Luma event
Trigger
Step 1
Luma
Guest Registered trigger fires for new event registrant
read
Step 2
HubSpot
Look up contact by email in HubSpot
write
Step 3
HubSpot
Create or update contact with 'event-registrant' tag and event name note
write
Step 4
HubSpot
Create follow-up task assigned to account executive
write
Step 5
Slack
Alert account executive in Slack if registrant is a hot lead
Result
Create or update contact with 'event-registrant' tag and event name noteCreate follow-up task assigned to account executiveAlert account executive in Slack if registrant is a hot lead
The win
Saved per run
15 min
Runs / week
~40×
No event registrant ever falls out of the sales pipeline
Driven bySales Agent
ROI

Savings

What your team gets back — two angles: what you stop doing manually, and what that's worth.

Without Actionist

What you do manually today

With Actionist

What your agent runs for you

  • Sales
    30 min / week
    Manual post-event CSV export to CRM

    After each event, reps manually export the Luma guest list, import it into HubSpot, and assign follow-up tasks — often taking 1–2 days after the event, by which time the lead has gone cold.

    Sales Agent
    0 min
    Agent syncs registrants to CRM within minutes automatically

    Within about a minute of a guest registering, the Sales Agent creates or updates their HubSpot contact, applies an event tag, and assigns a follow-up task to the account executive — no manual export needed.

  • Marketing
    45 min / week
    Manual event creation and cross-posting

    Marketing manually recreates each event in Luma from the content calendar, then separately posts announcements to each channel — a 20-30 minute process repeated for every event.

    Marketing Agent
    0 min
    Agent creates and announces events automatically from content calendar

    When an event is confirmed in Notion, the Marketing Agent creates the Luma event, posts announcements to Slack and Telegram, and adds the event to HubSpot — all before any manual action is taken.

  • Customer Support
    40 min / week
    Manual post-event attendee list segmentation

    Support manually downloads the guest list, filters by check-in status, and sends two separate batches of emails — a process that typically takes 45-60 minutes per event.

    Customer Support Agent
    0 min
    Agent routes attendees and no-shows to the right follow-up automatically

    After every event, the Support Agent separates attendees from no-shows and sends each group the correct follow-up — resources for attendees, recording link for no-shows — without manual list building.

  • Human Resources
    20 min / week
    Manual new hire event invitation setup

    HR manually adds each new hire to the Luma calendar, then individually sends event invitations to each onboarding session — taking 15-20 minutes per new hire per cohort.

    Human Resources Agent
    0 min
    Agent adds new hires to Luma and sends all onboarding event invitations

    When a new hire is added to the onboarding tracker, the HR Agent adds them to the Luma community and invites them to every onboarding session — no manual calendar management per new hire.

  • Finance
    30 min / week
    Manual post-event ticket revenue reconciliation

    Finance waits until after each event closes to export ticket sales from Luma, paste them into the revenue tracker, and reconcile against the budget — a 30-minute task per event.

    Finance Agent
    0 min
    Agent logs ticket revenue to tracker within minutes of each sale

    Every paid ticket registration triggers the Finance Agent to log the sale to Google Sheets and update the event budget page — revenue data is current without waiting for a post-event export.

  • Operations
    25 min / week
    Manual event change propagation across tools

    When an event changes in Luma, someone manually updates Google Calendar, edits the Notion event page, and posts a Slack alert — often taking 20-30 minutes and frequently delayed or missed.

    Operations Agent
    0 min
    Agent propagates event changes to all connected systems automatically

    When a Luma event is updated, the Operations Agent syncs the change to Google Calendar, Notion, and Slack within about a minute — all systems stay consistent without any manual update cycle.

  • Legal
    15 min / week
    Manual event compliance review before promotion

    Legal manually reviews each event page for compliance language before approving promotion — an ad-hoc, manually-triggered process that is frequently skipped under time pressure.

    Legal Agent
    0 min
    Agent checks every event for required legal language before promotion

    The Legal Agent reviews upcoming events for required privacy notice and disclaimer language automatically each week, flagging any that fall short before they are promoted to the public.

+ 100s of other Luma automations
Average time saved
21 hrs / person / month
Calculator

Calculate what your team saves

Team size
5 people
Hourly rate
$75 / hr
Hours saved / week
13
Hours saved / year
625
Annual ROI
$46,875

Based on Luma's typical team usage — the visible tasks plus a few other automations the agent runs: ~2.5 hrs / person / week of admin work automated.

Connect

How to plug Luma into Actionist

Pick the connection method that suits your environment.

Connect with a Luma calendar API key — the standard method for automating a single Luma calendar. Requires a Luma Plus subscription.

1
Open Luma API settings

In your Luma calendar, go to Settings → Integrations → API. You'll need a Luma Plus subscription on the calendar to access API settings.

2
Generate and copy the API key

Click 'Generate API key' to create a calendar API key. Copy it immediately — it's shown only once.

3
Paste into Actionist

Paste the key into Actionist and click Test connection. Actionist makes a read-only call to verify the key is valid.

Credentials you'll need
API key*
Luma calendar settings → Integrations → API → Generate calendar API key
Actions

13 actions your agent can call

Read and write operations available to your Actionist agent.

Triggers

7 events your agent can react to

Events your agent watches for, and the actions it kicks off in response.

Skills

Skills that pair with Luma

Reusable agent skills that work well alongside this app.

AI Video Generation

Create AI videos with Sora 2, Veo 3, Seedance, Runway, and modern APIs using reliable prompt and rendering workflows.

MCP servers

MCP servers that work with Luma

Connect Actionist to MCP servers built for or around this app.

Luma Events

Discover events from Luma — search by category, city, distance, and keywords with calendar export.

FAQs

Questions about Luma + Actionist

How does Actionist connect to Luma?
Go to the Apps tab in Actionist, find Luma, and click Connect. The recommended path uses an API key — in your Luma calendar settings, navigate to Integrations → API, generate a calendar API key, and paste it into Actionist. Once connected, Actionist runs a test read call to confirm access. You'll need an active Luma Plus subscription on the calendar you want to connect, as API access is a Plus-tier feature.
What type of API key do I need, and what are the rate limits?
Luma offers two types of API credentials: a Calendar API key (scoped to a single calendar, 200 requests per minute) and an Organisation API key (spans all calendars in your organisation, 500 requests per minute). For most teams, a calendar API key is sufficient. If you're managing events across multiple calendars or running high-volume automation, use the organisation key. Both are generated inside Luma settings under Integrations → API.
Can I use Luma with other apps in the same workflow?
Yes. Luma is most powerful when paired with other apps. Common combinations: add guests to your Luma calendar whenever a lead fills out a HubSpot form; post a Slack message to the events channel when a new event is created; sync new ticket registrations to a Google Sheets attendee tracker; trigger a Notion task when an event is updated; or send a personalised follow-up email via Gmail when a guest registers. Any of Actionist's 200+ connected apps can be used alongside Luma in the same scheduled agent task.
What are the most common automation patterns with Luma?
The four patterns that come up most: (1) post-registration nurture — when a guest registers for an event, the agent adds them to an email sequence in your CRM; (2) attendee roster sync — new ticket registrations are written to Google Sheets or Notion in near real-time; (3) event lifecycle notifications — when an event is created or updated in Luma, team channels get an automatic Slack or Telegram alert; (4) calendar community growth — people who submit a form, buy a product, or attend a webinar are automatically added as Luma calendar subscribers.
How fast do Luma webhook triggers fire?
Luma webhooks fire within about a minute of the triggering event. This covers: Calendar Event Added, Calendar Person Subscribed, Event Created, Event Updated, Guest Registered, Guest Updated, and Ticket Registered. There is no guaranteed instantaneous delivery — Luma's webhook system processes events asynchronously, so a short delay is normal. For time-sensitive follow-ups (e.g. sending a welcome message to a new registrant), build your downstream steps to tolerate a 1–2 minute lag.
Can Actionist add people to my Luma calendar community automatically?
Yes — use the Create Calendar Person action to programmatically add people to your Luma calendar community. You can include optional tags (Luma creates them if they don't exist yet), which lets you segment your audience by source, interest, or acquisition channel. This is the standard way to grow a Luma community from other tools: a form submission, a CRM deal stage change, or a completed purchase can each trigger an add-to-calendar action so your event community stays in sync with your broader contact database.
Can Actionist create fully configured Luma events, not just blank ones?
Yes. When you create an event via the Actionist agent using the Create Event action, you can set all the key fields: title, description, start and end time, location (in-person or virtual with a meeting URL), cover image URL, and ticket capacity. You can also control visibility (public vs unlisted) and whether registration requires approval. The agent can create draft events for team review before they go public, or publish them immediately if your workflow is fully automated.
Do I need a paid Luma plan to use Actionist automation?
Luma API access requires a Luma Plus subscription on the calendar. Plus is Luma's paid tier, which also unlocks advanced ticketing, custom domains, and deeper analytics. If you're on the free plan, you can still receive Luma webhook triggers manually via Zapier webhooks (Luma's own Zapier integration is Plus-only too), but direct API and webhook automation through Actionist requires Plus. Most teams running regular events find the Plus tier cost easily justified by the time saved on manual guest management alone.