--- title: "Connect Vryno to Luma - APIANT.ai" description: "When \"Create or Update Call Log\" fires in Vryno, your agent runs \"Add ticket type\" in Luma." canonical: "https://apiant.ai/connect/vryno-to-luma" --- # Connect Vryno to Luma When **Create or Update Call Log** fires in [Vryno](https://apiant.ai/connections/vryno), 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. Vryno **10** triggers Vryno **28** 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 Vryno 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 Vryno can start in Luma - When **Create or Update Call Log** in Vryno then **Add ticket type** in Luma - When **Create or Update Case** in Vryno 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 Vryno and Luma ## Triggers and actions 10 triggers · 47 actions - Trigger **Create or Update Call Log** Triggers when a call log is created or updated in Vryno. - Trigger **Create or Update Case** Triggers when a case is created or updated in Vryno. - Trigger **Create or Update Contact** Triggers when a contact is created or updated in Vryno CRM. - Trigger **Create or Update Invoice** Triggers when an invoice is created or updated in Vryno. - Trigger **Create or Update Lead** Triggers when a lead is created or updated in Vryno. - Trigger **Create or Update Meeting** Triggers when a meeting is created or updated in Vryno. - Trigger **Create or Update Project** Triggers when a project is created or updated in Vryno. - Trigger **Create or Update Quote** Triggers when a quote is created or updated in Vryno CRM. - Trigger **Create or Update Sales Order** Triggers when a sales order is created or updated in Vryno. - Trigger **Create or Update Task** Triggers when a task is created or updated in Vryno. - Action **Create or Update Case** Creates a new case in Vryno CRM, or updates an existing case when a case id is supplied. Returns the saved case. - Action **Create or Update Deal** Creates a new deal in Vryno CRM, or updates an existing deal when a Deal ID is supplied. Returns the saved deal. - Action **Create or Update Invoice** Creates a new invoice in Vryno, or updates an existing one when an invoice ID is supplied. - Action **Create or Update Lead** Creates a new lead in Vryno CRM, or updates an existing lead when a Lead ID is supplied. Returns the saved lead. - Action **Create or Update Organization** Creates a new organization in Vryno CRM, or updates an existing one when an organization ID is supplied. Returns the saved organization. - Action **Create or Update Product** Creates a new product in Vryno CRM, or updates an existing product when a product id is supplied. - Action **Create or Update Project** Creates a new project in Vryno, or updates an existing project when a project id is supplied. Returns the saved project. - Action **Create or Update Quote** Creates a new quote in Vryno, or updates an existing quote when a quote ID is supplied. - Action **Create or Update Sales Order** Creates a new sales order in Vryno, or updates an existing one when a sales order ID is supplied. - Action **Create or Update Task** Creates a new task in Vryno CRM, or updates an existing task when a task ID is supplied. - Action **Create or Update Vendor** Creates a new vendor in Vryno CRM, or updates an existing vendor when a vendor ID is supplied, and returns the saved vendor. - Action **Delete contact** Deletes a contact in Vryno CRM by its ID and returns Vryno's confirmation message. - Action **Delete lead** Deletes a lead from Vryno CRM by its ID and returns Vryno's confirmation. - Action **Find contacts** Returns the contacts in Vryno CRM that match the filters you specify, or those in a chosen custom view. - Action **Find deals** Returns the deals that match the conditions you specify, such as a deal name or email. - Action **Find leads** Returns the leads in Vryno CRM that match the conditions you specify, such as a name or email address. - Action **Get Case** Returns one case from Vryno CRM by its id, including any custom fields you ask for. - Action **Get contact** Returns one contact from Vryno CRM by its id. An error occurs if the contact is not found. - Action **Get deal** Returns one Vryno deal by its id, including any fields your account has added to deals. An error occurs if the deal is not found. - Action **Get Invoice** Returns one invoice from Vryno CRM by its id, including any custom fields you name. An error occurs if the invoice is not found. - Action **Get lead** Returns a single lead from Vryno CRM by its id, including any custom fields you name. An error occurs if the lead is not found. - Action **Get Organization** Returns one organization from Vryno CRM by its id, including any custom fields you ask for. An error occurs if the organization is not found. - Action **Get Product** Returns a single product from Vryno by its id, including any custom fields you ask for. An error occurs if the product is not found. - Action **Get Project** Returns a project from Vryno by its id, including any custom fields you name. An error occurs if the project is not found. - Action **Get Quote** Returns a single quote from Vryno CRM by its id, including its billing and shipping details, related records and totals. - Action **Get Sales Order** Returns a single sales order from Vryno by its id, including any custom fields you name. - Action **Get Task** Returns a task from Vryno CRM by its id, including its status, assignee, due date and priority. Fails if the task is not found. - Action **Get Vendor** Returns one vendor from Vryno CRM by its id, including any custom fields you ask for. - 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 - [ **Vryno** Vryno is a simplified CRM with customization and workflows](https://apiant.ai/connections/vryno) - [ **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 Vryno - [ **Vryno to Zoom** Zoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...](https://apiant.ai/connect/vryno-to-zoom) - [ **Vryno to Webflow** Webflow is a professional website builder and CMS for designing, building, and launching responsive...](https://apiant.ai/connect/vryno-to-webflow) - [ **Vryno to Wix** The Wix website builder gives businesses of any size the tools to create, manage and grow a fully integrated...](https://apiant.ai/connect/vryno-to-wix) - [ **Vryno to LinkedIn** LinkedIn is a professional networking platform enabling job seekers, companies, and thought leaders to...](https://apiant.ai/connect/vryno-to-linkedin) - [ **Vryno to Facebook** Facebook is a social media and advertising platform used by individuals and businesses to connect, share...](https://apiant.ai/connect/vryno-to-facebook) - [ **Vryno to Anthropic** Anthropic builds Claude, a family of large language models.](https://apiant.ai/connect/vryno-to-anthropic) ## 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 ## Vryno and Luma, answered ### ### What can start an automation from Vryno? Any of Vryno's 10 triggers in the catalog, including Create or Update Call Log, Create or Update Case, Create or Update Contact and Create or Update Invoice. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in Luma when something happens in Vryno? 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 Vryno? Luma has no triggers in the catalog today, so automations start in Vryno. 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 Vryno 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 Vryno 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.