--- title: "Connect Hyros to Luma - APIANT.ai" description: "When \"New Call\" fires in Hyros, your agent runs \"Add ticket type\" in Luma. Describe the whole flow and it is built, tested on every scenario and kept running." canonical: "https://apiant.ai/connect/hyros-to-luma" --- # Connect Hyros to Luma When **New Call** fires in [Hyros](https://apiant.ai/connections/hyros), 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. Hyros **5** triggers Hyros **20** actions Luma **19** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want Hyros 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 Hyros can start in Luma - When **New Call** in Hyros then **Add ticket type** in Luma - When **New Lead** in Hyros then **Add event** 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 Hyros and Luma ## Triggers and actions 5 triggers · 39 actions - Trigger **New Call** Triggers when a new call is recorded in HYROS. - Trigger **New Lead** Triggers when a new lead is created in HYROS. - Trigger **New Sale** Triggers when a new sale is recorded in HYROS. - Trigger **New Sale Attributed** Triggers when a new sale is recorded and attributed in Hyros. - Trigger **New Subscription** Triggers when a new subscription is recorded in HYROS. - Action **Delete Call** Deletes a call. - Action **Delete Sale** Deletes a sale. - Action **Find Lead Clicks** Returns the tracked clicks of a lead. - Action **Find Leads** Finds leads by ID, email or creation date. - Action **Find Sales** Finds sales by ID, email, lead, product tag or date. - Action **Find Subscriptions** Finds subscriptions by ID, email, lead, product tag, status or date. - Action **Get Ad Accounts Attribution Report** Returns sales, revenue, cost and other attribution figures per ad account. - Action **Get Ads Attribution Report** Returns sales, revenue, cost and other attribution figures per ad, ad set or campaign. - Action **Get Lead Journey** Returns the attribution journey of one or more leads: their sales and the sources that led to them. - Action **Get User Info** Returns the profile of the account the API key belongs to. - Action **List Ads** Returns the ads HYROS tracks for an ad platform. - Action **List Domains** Returns the domains configured in the account. - Action **List Keywords** Returns the keywords of a Google ad group. - Action **List Lead Stages** Returns the lead stages in the account. - Action **List Sources** Returns the traffic sources in the account. - Action **List Tags** Returns every tag in the account. - Action **Refund Order** Refunds an order and updates the income of its lead. - Action **Retrieve Calls** Finds calls by ID, email, lead, product tag, qualification or date. - Action **Update Call** Updates the name, state or qualification of calls. - Action **Update Sale** Marks sales as refunded or recurring. - Action **Add event** Adds an existing event to your Luma calendar — either a Luma event you manage or an event hosted on another platform. The event is approved right away unless you choose to keep it pending for admin review. - 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 event** Updates an existing Luma event's details, such as its name, time, location, description, capacity, registration settings and page appearance. Fields left blank keep their current values. - 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 - [ **Hyros** HYROS makes profitable action clear for high end digital businesses with laser accurate sales attribution...](https://apiant.ai/connections/hyros) - [ **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 Hyros - [ **Hyros to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/hyros-to-salesforce) - [ **Hyros to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/hyros-to-slack) - [ **Hyros to Mailchimp** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/hyros-to-mailchimp) - [ **Hyros to Stripe** Stripe is a payment processing platform for online businesses.](https://apiant.ai/connect/hyros-to-stripe) - [ **Hyros to Shopify** Shopify is a commerce platform for online stores and retail point-of-sale.](https://apiant.ai/connect/hyros-to-shopify) - [ **Hyros to QuickBooks Online** QuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...](https://apiant.ai/connect/hyros-to-quickbooks-online) ## 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 is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](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 ## Hyros and Luma, answered ### ### What can start an automation from Hyros? Any of Hyros's 5 triggers in the catalog, including New Call, New Lead, New Sale and New Sale Attributed. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in Luma when something happens in Hyros? Any of Luma's 19 actions, including Create Calendar Person, Send invites, Update event and Update guest status. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Luma to Hyros? Luma has no triggers in the catalog today, so automations start in Hyros. 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 Hyros 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 Hyros 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.