---
title: "Connect Reply to Luma - APIANT.ai"
description: "When \"New Email Opened\" fires in Reply, your agent runs \"Add ticket type\" in Luma."
canonical: "https://apiant.ai/connect/reply-to-luma"
---

# Connect Reply to Luma

When **New Email Opened** fires in [Reply](https://apiant.ai/connections/reply), your agent runs **Add ticket type** in [Luma](https://apiant.ai/connections/luma). Describe the whole flow and it is built, tested on every scenario and kept running.

Reply **7** triggers Reply **16** actions Luma **17** actions

What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.

## What do you want Reply and Luma to do together?

Give your AI client this address.

`https://mcp.apiant.ai`

One connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.

### Set it up in your client

### Claude Code

Run this in the directory you want to work in.

`claude mcp add --transport http -s project apiant-ai https://mcp.apiant.ai`

Start Claude Code there, approve the server, and sign in in the browser page it opens.

[Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code)

### Claude, web and desktop

Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Cursor

Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Zed

Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Codex and the ChatGPT desktop app

Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Any other MCP client

Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

Example flows

## What Reply can start in Luma

- When **New Email Opened** in Reply then **Add ticket type** in Luma
- When **New Emails Sent** in Reply then **Apply contact tag** in Luma

Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.

Everything your agent can do with Reply and Luma

## Triggers and actions 7 triggers · 33 actions

- Trigger

**Inbox Category Set for Reply**

Triggers when an email reply in Reply is given an inbox category, automatically or by a user.

- Trigger

**New Email Opened**

Triggers when a contact opens a tracked email sent from Reply.

- Trigger

**New Emails Sent**

Triggers when Reply sends an email from a sequence step.

- Trigger

**New Link Clicked**

Triggers when a recipient clicks a tracked link in an email sent from Reply.

- Trigger

**New Person Bounce**

Triggers when an email sent from Reply bounces or is rejected by the recipient's mail server.

- Trigger

**New Person Opt Out**

Triggers when a contact opts out of outreach in Reply (unsubscribe link, manual opt-out, or marked Do Not Contact).

- Trigger

**Prospect Finished**

Triggers when a contact's participation in a Reply sequence ends — completed, replied, bounced, opted out, or finished manually.

- Action

**Add contact list**

Creates a new contact list in Reply, optionally shared with your team.

- Action

**Add note to contact**

Adds a note to a contact's timeline in Reply.

- Action

**Add sequence**

Creates a new sequence in Reply with its steps, schedule, sending accounts and settings.

- Action

**Create\Update Person**

Creates a Reply contact, or updates the existing contact with the same email address.

- Action

**Delete contact**

Deletes a contact from your Reply account.

- Action

**Find contacts by criteria**

Returns the contacts that match a search term and/or field rules, optionally scoped to a contact list, sequence or sequence step.

- Action

**Get contact**

Returns one Reply contact by its id, including profile details, owner, opt-out, call and meeting status, stage and custom fields.

- Action

**Get sequence**

Returns one sequence in full: name, status, owner, schedule, settings, connected email and LinkedIn accounts, and its steps.

- Action

**List contact lists**

Returns the contact lists you own plus those shared with your team, optionally filtered by name.

- Action

**List contacts**

Returns your Reply contacts, optionally narrowed to one email address or LinkedIn profile URL.

- Action

**List inbox categories**

Returns the inbox categories you can file conversations under.

- Action

**List Sequence Contacts**

Returns the contacts enrolled in a sequence, with each contact's status, current step, added date, opt-out and call status.

- Action

**List sequences**

Returns the sequences in your Reply account, optionally filtered by status, owner, folder, archive state or name.

- Action

**Mark as Finished**

Marks one or more contacts as finished in every sequence they are in, so they receive no further sequence steps.

- Action

**Remove Person From Campaign**

Removes a contact from a sequence so they stop progressing through it. The contact and their history stay in your Reply account.

- Action

**Send Test Webhook Event**

Sends a test event from an existing Reply webhook subscription to its configured URL.

- Action

**Add guests**

Adds one or more guests to a Luma event, optionally assigning ticket types, an approval status, and whether Luma emails them. Returns any guests Luma skipped.

- Action

**Add host**

Adds a host to a Luma event, as a manager or as check-in staff, by email address.

- Action

**Add ticket type**

Creates a new ticket type (free or paid) for a Luma event. Paid ticket types require the calendar to have a connected Stripe account.

- Action

**Apply contact tag**

Applies a contact tag to existing contacts on your Luma calendar, identified by user ID or email. Does not create new contacts.

- Action

**Block contact**

Blocks a contact on your Luma calendar so they can't follow it or join its events, and stop receiving your invites and newsletters.

- Action

**Cancel event**

Cancels a Luma event. The event is permanently deleted, all guests are notified, and paid guests can optionally be refunded.

- Action

**Create Calendar Person**

Adds a person to your Luma calendar as a contact by email, optionally with a name and contact tags, so you can invite them to events and send newsletters.

- Action

**Get calendar**

Returns the details of the Luma calendar your connected API key belongs to, including its name, URL, location, social handles and default event settings.

- Action

**Get event**

Returns the details of a Luma event, including its schedule, location, visibility, hosts and, for events you manage, guest counts by status.

- Action

**Get guest**

Returns one guest of a Luma event, looked up by guest ID, ticket key, guest key or email, including their approval status, registration answers and tickets.

- Action

**Import contacts**

Imports contacts into your Luma calendar so you can invite them to events and send them newsletters, optionally tagging them.

- Action

**List contacts**

Returns the contacts (people) on your Luma calendar, optionally filtered by a name/email search, tags or membership status.

- Action

**List events**

Returns the events on your Luma calendar, optionally filtered by date range, submission status, platform and access level.

- Action

**List guests**

Returns the guests who have registered for or been invited to a Luma event, with their approval status, contact details, registration answers and tickets.

- Action

**List ticket types**

Returns every ticket type set up for a Luma event, including its name, price and capacity.

- Action

**Send invites**

Sends people an email invite (and an SMS if their phone is linked to Luma) to a Luma event. Returns any invitees who were skipped because they unsubscribed, were removed, or are blocked.

- Action

**Update guest status**

Changes a guest's registration status for a Luma event — approve (Going), decline, move back to pending approval, or waitlist — optionally refunding a paid guest and adding a personal note to the notification email.

## Each app on its own

- [ **Reply** Reply is a sales automation platform that puts outreach on autopilot, while still making each communication...](https://apiant.ai/connections/reply)
- [ **Luma** Luma is an event management app that gives you the tools to host delightful events.](https://apiant.ai/connections/luma)

Reviews

## What our customers say

## More from Reply

- [ **Reply to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/reply-to-salesforce)
- [ **Reply to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/reply-to-slack)
- [ **Reply to Stripe** Stripe is a payment processing platform for online businesses.](https://apiant.ai/connect/reply-to-stripe)
- [ **Reply to Shopify** Shopify is a commerce platform for online stores and retail point-of-sale.](https://apiant.ai/connect/reply-to-shopify)
- [ **Reply to Trello** Trello is a visual collaboration tool that organizes projects into boards, lists, and cards.](https://apiant.ai/connect/reply-to-trello)
- [ **Reply to Zoom** Zoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...](https://apiant.ai/connect/reply-to-zoom)

## More into Luma

- [ **HubSpot to Luma** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-luma)
- [ **Salesforce to Luma** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-luma)
- [ **Slack to Luma** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-luma)
- [ **Google Sheets to Luma** Google Sheets](https://apiant.ai/connect/google-sheets-to-luma)
- [ **Gmail to Luma** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-luma)
- [ **Google Calendar to Luma** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-luma)

Questions

## Reply and Luma, answered

###

### What can start an automation from Reply?

Any of Reply's 7 triggers in the catalog, including New Email Opened, New Emails Sent, New Link Clicked and New Person Bounce. Describe the moment in plain language and your agent picks the right one.

###

### What can your agent do in Luma when something happens in Reply?

Any of Luma's 17 actions, including Create Calendar Person, Send invites, Update guest status and Add guests. Your agent maps the data both ways and tests every scenario before it ships.

###

### Can it also run from Luma to Reply?

Luma has no triggers in the catalog today, so automations start in Reply. If you need the other direction, ask: your agent reads Luma's API documentation and adds it.

###

### Do I have to build a connector for Reply or Luma?

No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.

###

### Can my AI client use Reply and Luma without building an automation?

Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.

###

### What happens when something fails?

Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.

###

### Is there a free plan?

Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.
