Integration
Connect Vryno to Luma
When Create or Update Call Log fires in Vryno, your agent runs Add ticket type in Luma. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Vryno and Luma to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne 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.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)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)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)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)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)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)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 LogTriggers when a call log is created or updated in Vryno.
Trigger
Create or Update CaseTriggers when a case is created or updated in Vryno.
Trigger
Create or Update ContactTriggers when a contact is created or updated in Vryno CRM.
Trigger
Create or Update InvoiceTriggers when an invoice is created or updated in Vryno.
Trigger
Create or Update LeadTriggers when a lead is created or updated in Vryno.
Trigger
Create or Update MeetingTriggers when a meeting is created or updated in Vryno.
Trigger
Create or Update ProjectTriggers when a project is created or updated in Vryno.
Trigger
Create or Update QuoteTriggers when a quote is created or updated in Vryno CRM.
Trigger
Create or Update Sales OrderTriggers when a sales order is created or updated in Vryno.
Trigger
Create or Update TaskTriggers when a task is created or updated in Vryno.
Action
Create or Update CaseCreates 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 DealCreates 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 InvoiceCreates a new invoice in Vryno, or updates an existing one when an invoice ID is supplied.
Action
Create or Update LeadCreates 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 OrganizationCreates 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 ProductCreates a new product in Vryno CRM, or updates an existing product when a product id is supplied.
Action
Create or Update ProjectCreates a new project in Vryno, or updates an existing project when a project id is supplied. Returns the saved project.
Action
Create or Update QuoteCreates a new quote in Vryno, or updates an existing quote when a quote ID is supplied.
Action
Create or Update Sales OrderCreates a new sales order in Vryno, or updates an existing one when a sales order ID is supplied.
Action
Create or Update TaskCreates a new task in Vryno CRM, or updates an existing task when a task ID is supplied.
Action
Create or Update VendorCreates a new vendor in Vryno CRM, or updates an existing vendor when a vendor ID is supplied, and returns the saved vendor.
Action
Delete contactDeletes a contact in Vryno CRM by its ID and returns Vryno's confirmation message.
Action
Delete leadDeletes a lead from Vryno CRM by its ID and returns Vryno's confirmation.
Action
Find contactsReturns the contacts in Vryno CRM that match the filters you specify, or those in a chosen custom view.
Action
Find dealsReturns the deals that match the conditions you specify, such as a deal name or email.
Action
Find leadsReturns the leads in Vryno CRM that match the conditions you specify, such as a name or email address.
Action
Get CaseReturns one case from Vryno CRM by its id, including any custom fields you ask for.
Action
Get contactReturns one contact from Vryno CRM by its id. An error occurs if the contact is not found.
Action
Get dealReturns 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 InvoiceReturns 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 leadReturns 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 OrganizationReturns 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 ProductReturns 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 ProjectReturns a project from Vryno by its id, including any custom fields you name. An error occurs if the project is not found.
Action
Get QuoteReturns a single quote from Vryno CRM by its id, including its billing and shipping details, related records and totals.
Action
Get Sales OrderReturns a single sales order from Vryno by its id, including any custom fields you name.
Action
Get TaskReturns 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 VendorReturns one vendor from Vryno CRM by its id, including any custom fields you ask for.
Action
Add eventAdds 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 guestsAdds 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 hostAdds a host to a Luma event, as a manager or as check-in staff, by email address.
Action
Add ticket typeCreates 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 tagApplies a contact tag to existing contacts on your Luma calendar, identified by user ID or email. Does not create new contacts.
Action
Block contactBlocks 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 eventCancels a Luma event. The event is permanently deleted, all guests are notified, and paid guests can optionally be refunded.
Action
Create Calendar PersonAdds 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 calendarReturns 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 eventReturns the details of a Luma event, including its schedule, location, visibility, hosts and, for events you manage, guest counts by status.
Action
Get guestReturns 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 contactsImports contacts into your Luma calendar so you can invite them to events and send them newsletters, optionally tagging them.
Action
List contactsReturns the contacts (people) on your Luma calendar, optionally filtered by a name/email search, tags or membership status.
Action
List eventsReturns the events on your Luma calendar, optionally filtered by date range, submission status, platform and access level.
Action
List guestsReturns 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 typesReturns every ticket type set up for a Luma event, including its name, price and capacity.
Action
Send invitesSends 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 eventUpdates 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 statusChanges 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.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Vryno
Vryno to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
Vryno to WebflowWebflow is a professional website builder and CMS for designing, building, and launching responsive...
Vryno to WixThe Wix website builder gives businesses of any size the tools to create, manage and grow a fully integrated...
Vryno to LinkedInLinkedIn is a professional networking platform enabling job seekers, companies, and thought leaders to...
Vryno to FacebookFacebook is a social media and advertising platform used by individuals and businesses to connect, share...
Vryno to AnthropicAnthropic builds Claude, a family of large language models.
More into Luma
HubSpot to LumaHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to LumaSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to LumaSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to LumaGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to LumaGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to LumaGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
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.