--- title: "Connect Grist to Luma - APIANT.ai" description: "When \"New or Updated Record\" fires in Grist, your agent runs \"Add ticket type\" in Luma." canonical: "https://apiant.ai/connect/grist-to-luma" --- # Connect Grist to Luma When **New or Updated Record** fires in [Grist](https://apiant.ai/connections/grist), 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. Grist **4** triggers Grist **21** 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 Grist 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 Grist can start in Luma - When **New or Updated Record** in Grist then **Add ticket type** in Luma - When **New Record** in Grist 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 Grist and Luma ## Triggers and actions 4 triggers · 38 actions - Trigger **New or Updated Record** Triggered when a row in a Grist table is created or updated. - Trigger **New or Updated Record (Instant)** Triggers when a Record is updated, or a new Record is added. - Trigger **New Record** Triggered when a new row is added to a Grist table. - Trigger **New Record (Instant)** Triggers when a new Record is created - Action **Add Column** Adds a column to a table in a Grist document. - Action **Add Table** Creates a new table in a Grist document, optionally with a starting set of columns. - Action **Create Document** Creates a new document in a Grist workspace and returns its document ID. - Action **Create or Update Record** Adds a row to a Grist table, or updates the existing row when the match column already holds the match value. Returns the row ID. - Action **Create Record** Adds a new row to a Grist table and returns its row ID. - Action **Create Workspace** Creates a new workspace in a Grist organization and returns its ID. - Action **Delete Document** Deletes a Grist document permanently. - Action **Delete Records** Deletes one or more rows from a Grist table by row ID. - Action **Delete Workspace** Deletes a Grist workspace along with every document inside it. - Action **Find Record** Searches a Grist table for a row whose column holds a given value and returns that row's ID and column values. - Action **Get Document** Returns the details of one Grist document — its name, web address, workspace, and organization. - Action **Get Org** Returns the details of one Grist organization (team site) — its name, subdomain, owner, and your access level. - Action **Get Workspace** Returns the details of one Grist workspace, including the documents it contains. - Action **List Columns** Returns the columns of a Grist table, with each column's ID, label, and type. - Action **List Orgs** Returns every Grist organization (team site) this connection can reach. - Action **List Tables** Returns the tables in a Grist document. - Action **List Workspaces** Returns the workspaces in a Grist organization, each with the documents it contains. - Action **Run SQL Query** Runs a read-only SELECT statement against a Grist document and returns the rows. - Action **Update Document** Renames a Grist document or changes whether it is pinned. Anything left blank stays as it is. - Action **Update Record** Changes the column values of one row in a Grist table. Columns left blank keep their current values. - Action **Update Workspace** Renames a Grist workspace. - 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 - [ **Grist** Grist combines the flexibility of a spreadsheet with the robustness of a database to organize your data...](https://apiant.ai/connections/grist) - [ **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 Grist - [ **Grist to Gmail** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/grist-to-gmail) - [ **Grist to Clickhouse** Column-oriented database for real-time analytical SQL queries at petabyte scale.](https://apiant.ai/connect/grist-to-clickhouse) - [ **Grist to Mistral AI** Mistral AI is a platform for building, customizing, and deploying advanced AI models and agents for...](https://apiant.ai/connect/grist-to-mistral-ai) - [ **Grist to OpusClip** OpusClip is a AI video tool that turns long videos into viral shorts with captions and transcripts.](https://apiant.ai/connect/grist-to-opusclip) - [ **Grist to Postman** Postman is a platform for building and testing APIs.](https://apiant.ai/connect/grist-to-postman) - [ **Grist to RuneScape** The RuneScape Wiki API exposes data for RuneScape and Old School RuneScape.](https://apiant.ai/connect/grist-to-runescape) ## 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 ## Grist and Luma, answered ### ### What can start an automation from Grist? Any of Grist's 4 triggers in the catalog, including New or Updated Record, New or Updated Record (Instant), New Record and New Record (Instant). Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in Luma when something happens in Grist? 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 Grist? Luma has no triggers in the catalog today, so automations start in Grist. 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 Grist 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 Grist 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.