---
title: "Connect SOS Inventory to Luma - APIANT.ai"
description: "When \"New Customer\" fires in SOS Inventory, your agent runs \"Add ticket type\" in Luma."
canonical: "https://apiant.ai/connect/sos-inventory-to-luma"
---

# Connect SOS Inventory to Luma

When **New Customer** fires in [SOS Inventory](https://apiant.ai/connections/sos-inventory), 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.

SOS Inventory **10** triggers SOS Inventory **26** 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 SOS Inventory 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 SOS Inventory can start in Luma

- When **New Customer** in SOS Inventory then **Add ticket type** in Luma
- When **New Estimate** in SOS Inventory 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 SOS Inventory and Luma

## Triggers and actions 10 triggers · 43 actions

- Trigger

**New Customer**

Triggers when a new customer is created.

- Trigger

**New Estimate**

- Trigger

**New Invoice**

Triggers when a new invoice is created.

- Trigger

**New Item**

- Trigger

**New Purchase Order**

Triggers when a new purchase order is created.

- Trigger

**New Sales Order**

Triggers when a new sales order is created.

- Trigger

**New Sales Receipt**

Triggers when a new sales receipt is created.

- Trigger

**New Shipment**

Triggers when a new shipment is created.

- Trigger

**New Vendor**

- Trigger

**Updated Item Quantity**

Triggers when an item quantity is updated.

- Action

**Add estimate**

/api/v2/estimate. Creates an estimate.

- Action

**Add inventory adjustment**

/api/v2/adjustment. Creates an inventory adjustment.

- Action

**Add invoice**

/api/v2/invoice. Creates an invoice.

- Action

**Add item**

/api/v2/item. Creates an item (inventory, non-inventory, service, assembly, kit etc.).

- Action

**Add purchase order**

/api/v2/purchaseorder. Creates a purchase order.

- Action

**Add transfer**

/api/v2/transfer. Creates an inventory transfer between locations.

- Action

**Add vendor**

/api/v2/vendor. Creates a vendor.

- Action

**Create Customer**

Creates a new customer

- Action

**Create Sales Order**

Creates a new sales order

- Action

**Create Sales Receipt**

Creates a new sales receipt

- Action

**Find Customer**

Finds a customer

- Action

**Find Sales Order**

Finds a sales order

- Action

**Find vendors**

/api/v2/vendor with query filters. Searches vendors.

- Action

**Get customer**

/api/v2/customer/{id}. Retrieves one customer by id.

- Action

**Get estimate**

Returns one estimate by id, including its lines and custom fields.

- Action

**Get inventory adjustment**

Returns one inventory adjustment by id, including its lines.

- Action

**Get invoice**

Returns one invoice by id.

- Action

**Get item**

/api/v2/item/{id}. Retrieves one item by id.

- Action

**Get purchase order**

Returns one purchase order by id.

- Action

**Get sales order**

/api/v2/salesorder/{id}. Retrieves one sales order.

- Action

**Get sales receipt**

Returns one sales receipt by id, including its lines and custom fields.

- Action

**Get transfer**

Retrieves a single inventory transfer by id, including its from/to locations and lines.

- Action

**List items**

/api/v2/item. Lists items with query filters and paging.

- Action

**Update customer**

/api/v2/customer/{id}. Updates a customer; requires syncToken.

- Action

**Update item**

/api/v2/item/{id}. Updates an item; requires current syncToken.

- Action

**Update sales order**

/api/v2/salesorder/{id}. Updates a sales order; requires syncToken.

- 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

- [ **SOS Inventory** SOS Inventory is an app that tracks inventory, provides order management and manufacturing tracking and...](https://apiant.ai/connections/sos-inventory)
- [ **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 SOS Inventory

- [ **SOS Inventory to Stripe** Stripe is a payment processing platform for online businesses.](https://apiant.ai/connect/sos-inventory-to-stripe)
- [ **SOS Inventory to Trello** Trello is a visual collaboration tool that organizes projects into boards, lists, and cards.](https://apiant.ai/connect/sos-inventory-to-trello)
- [ **SOS Inventory to Zoom** Zoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...](https://apiant.ai/connect/sos-inventory-to-zoom)
- [ **SOS Inventory to Twilio** Cloud communications platform for sending SMS/MMS messages, making and managing voice calls, and looking up...](https://apiant.ai/connect/sos-inventory-to-twilio)
- [ **SOS Inventory to Typeform** Build and publish online forms, surveys, and quizzes with Typeform.](https://apiant.ai/connect/sos-inventory-to-typeform)
- [ **SOS Inventory to Webflow** Webflow is a professional website builder and CMS for designing, building, and launching responsive...](https://apiant.ai/connect/sos-inventory-to-webflow)

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

## SOS Inventory and Luma, answered

###

### What can start an automation from SOS Inventory?

Any of SOS Inventory's 10 triggers in the catalog, including New Customer, New Estimate, New Invoice and New Item. Describe the moment in plain language and your agent picks the right one.

###

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

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 SOS Inventory?

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