--- title: "Connect Commerce Layer to Luma - APIANT.ai" description: "When \"New Attachment\" fires in Commerce Layer, your agent runs \"Add ticket type\" in Luma." canonical: "https://apiant.ai/connect/commerce-layer-to-luma" --- # Connect Commerce Layer to Luma When **New Attachment** fires in [Commerce Layer](https://apiant.ai/connections/commerce-layer), 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. Commerce Layer **13** triggers Commerce Layer **28** 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 Commerce Layer 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 Commerce Layer can start in Luma - When **New Attachment** in Commerce Layer then **Add ticket type** in Luma - When **New Customer** in Commerce Layer 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 Commerce Layer and Luma ## Triggers and actions 13 triggers · 45 actions - Trigger **New Attachment** Triggers when a new Attachment is created. - Trigger **New Customer** Triggers when a new Customer is created. - Trigger **New Customer Address Event** Triggers when a customer address is created. - Trigger **New Customer Password Reset Event** Triggers when a customer password reset is requested. - Trigger **New Customer Subscription Event** Triggers when a given customer_subscription event (one of create or destroy) is fired. - Trigger **New Price** Triggers when a new Price is created. - Trigger **New Price Import** Fires when a new price import is created in Commerce Layer. - Trigger **New Price List** Triggers when a new Price List is created. - Trigger **New Shipping Category** Triggers when a Shipping Category is created. - Trigger **New SKU** Triggers when a new SKU is created. - Trigger **New SKU Import** Triggers when a new SKU import is created. - Trigger **New Stock Item Import** Triggers when a new Stock Item import is created. - Trigger **New Stock Transfer Event** Triggers when a given stock transfer event (one of create, upocoming, picking, in_transit, complete, cancel is fired). - Action **Add Customer Address** Adds an existing address to a customer's address book. - Action **Add Customer Password Reset** Requests a password reset for a customer, returning the reset token to send them. - Action **Add Customer Subscription** Subscribes a customer email to a list, identified by a reference such as a newsletter id. - Action **Add Stock Transfer** Moves a quantity of a SKU from one stock location to another. - Action **Balance Change Gift Card** Change balance of a gift card. - Action **Create Address** Creates a postal address that can be attached to customers, orders and stock locations. - Action **Create Attachment** Creates a new Attachment. - Action **Create Customer** Creates a new Customer. - Action **Create Gift Card** Creates a new Gift Card. - Action **Create Price Import** Creates a new Price Import. - Action **Create Price List** Creates a new Price List. - Action **Create SKU** Creates a new SKU. - Action **Find Attachment** Finds a Attachment by name. - Action **Find Customer** Finds a customer by id or reference. - Action **Find Gift Card** Finds a gift card by id or reference. - Action **Find Price** Finds a price by price list. - Action **Find Price Import** Finds a Price Import by status. - Action **Find Price List** Finds a Price List by name. - Action **Find Shipping Category** Finds an Shipping Category by name. - Action **Find SKU** Finds an SKU by code. - Action **Find SKU Import** Finds an SKU Import by status. - Action **Find Stock Item Import** Finds a Stock Item Import by status. - Action **Get Address** Retrieves one address by id. - Action **Get Customer Address** Retrieves one customer address link by id. - Action **Get Customer Password Reset** Retrieves a customer password reset by id, returning customer_email, reset_password_token and reset_password_at. - Action **Get Customer Subscription** Retrieves one customer subscription by id. - Action **Get Stock Transfer** Retrieves one stock transfer by id. - Action **Update Customer Reference** Update customer data setting external identifier. - 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 - [ **Commerce Layer** Commerce Layer is a lightning fast, super flexible and ultra secure REST API that lets you build...](https://apiant.ai/connections/commerce-layer) - [ **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 Commerce Layer - [ **Commerce Layer to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/commerce-layer-to-hubspot) - [ **Commerce Layer to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/commerce-layer-to-salesforce) - [ **Commerce Layer to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/commerce-layer-to-slack) - [ **Commerce Layer to Google Sheets** Google Sheets](https://apiant.ai/connect/commerce-layer-to-google-sheets) - [ **Commerce Layer to Gmail** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/commerce-layer-to-gmail) - [ **Commerce Layer to Google Calendar** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/commerce-layer-to-google-calendar) ## 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 ## Commerce Layer and Luma, answered ### ### What can start an automation from Commerce Layer? Any of Commerce Layer's 13 triggers in the catalog, including New Attachment, New Customer, New Customer Address Event and New Customer Password Reset Event. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in Luma when something happens in Commerce Layer? 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 Commerce Layer? Luma has no triggers in the catalog today, so automations start in Commerce Layer. 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 Commerce Layer 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 Commerce Layer 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.