---
title: "Connect Gridfox to Luma - APIANT.ai"
description: "When \"Record Created\" fires in Gridfox, your agent runs \"Add ticket type\" in Luma."
canonical: "https://apiant.ai/connect/gridfox-to-luma"
---

# Connect Gridfox to Luma

When **Record Created** fires in [Gridfox](https://apiant.ai/connections/gridfox), 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.

Gridfox **2** triggers Gridfox **9** 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 Gridfox 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 Gridfox can start in Luma

- When **Record Created** in Gridfox then **Add ticket type** in Luma
- When **Record Created or Updated** in Gridfox 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 Gridfox and Luma

## Triggers and actions 2 triggers · 26 actions

- Trigger

**Record Created**

Triggers when a new record is created.

- Trigger

**Record Created or Updated**

Fires when a record in the chosen Gridfox table is created or updated.

- Action

**Add record**

Create a record in a table.

- Action

**Add user**

Add a user to the project.

- Action

**Delete record**

Delete a record.

- Action

**Find records**

Search records in a table by search parameters.

- Action

**Get record**

Get a record by reference field value.

- Action

**Get record audit**

Get audit history for a record.

- Action

**List tables**

List tables in the project.

- Action

**List User Groups**

lists the project's user groups with their member users (id, email).

- Action

**Update record**

Update a record by reference field value.

- 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

- [ **Gridfox** Manage your work, your way with Gridfox. The tool for team collaboration that helps you build custom...](https://apiant.ai/connections/gridfox)
- [ **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 Gridfox

- [ **Gridfox to Checkly** Synthetic monitoring platform for uptime, API, and browser checks with alerting and status pages.](https://apiant.ai/connect/gridfox-to-checkly)
- [ **Gridfox to Jungle Grid** GPU orchestration platform that runs AI inference/training jobs by intent without managing GPU providers.](https://apiant.ai/connect/gridfox-to-jungle-grid)
- [ **Gridfox to Less Annoying CRM** Less Annoying CRM is a small business CRM with easy-to-use features at an affordable price.](https://apiant.ai/connect/gridfox-to-less-annoying-crm)
- [ **Gridfox to Memsource** Translation management system for automating localization workflows, machine translation, and multilingual...](https://apiant.ai/connect/gridfox-to-memsource)
- [ **Gridfox to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/gridfox-to-hubspot)
- [ **Gridfox to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/gridfox-to-salesforce)

## 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

## Gridfox and Luma, answered

###

### What can start an automation from Gridfox?

Any of Gridfox's 2 triggers in the catalog, including Record Created and Record Created or Updated. Describe the moment in plain language and your agent picks the right one.

###

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

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 Gridfox?

Luma has no triggers in the catalog today, so automations start in Gridfox. 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 Gridfox 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 Gridfox 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.
