Integration
Connect Rev.io to Luma
When Customer Profile Updated fires in Rev.io, 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 Rev.io 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)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
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 Rev.io can start in Luma
When Customer Profile Updated in Rev.io
then Add ticket type in Luma
When New Bill in Rev.io
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 Rev.io and Luma
Triggers and actions 17 triggers · 38 actions
Trigger
Customer Profile UpdatedTriggers when a customer's profile is created or updated.
Trigger
New BillTriggers when a new bill is created.
Trigger
New ContactTriggers when a new contact is created.
Trigger
New CustomerTriggers when a new customer is created.
Trigger
New OrderTriggers when a new order is created.
Trigger
New PaymentTriggers when a new payment is received.
Trigger
New ProductTriggers when a new product is created.
Trigger
New RequestTriggers when a new request is created.
Trigger
New TaskTriggers when a new task is created.
Trigger
New TicketTriggers when a new ticket is created.
Trigger
Order Status ChangedTriggers when an order reaches a new status.
Trigger
Request AssignedTriggers when a request is assigned to a new user.
Trigger
Request Status ChangedTriggers when a request reaches a new status.
Trigger
Task CanceledTriggers when a task is canceled.
Trigger
Task CompletedTriggers when a task is marked complete.
Trigger
Task UpdatedTriggers when a task is created or any of its details change.
Trigger
Ticket UpdatedTriggers when a ticket is created or updated.
Action
Add Contact to CustomerCreates a contact on a customer account and returns the new contact's ID.
Action
Add Note to CustomerAdds a note to a customer account and returns the new note's ID.
Action
Download Request PDFGenerates a request's PDF and returns its file name and base64 content.
Action
Find a BillFinds bills by bill ID or customer ID and returns the matching bills.
Action
Find a ContactFinds contacts by contact ID or customer ID and returns the matching contacts.
Action
Find a CustomerFinds customers by name, account number or customer ID and returns the matching customer records.
Action
Find a OrderFinds orders by order ID, customer ID or request ID and returns the matching orders.
Action
Find a ReportReturns a saved report's definition by its report ID.
Action
Find a RequestFinds requests by request ID or customer ID and returns the matching requests.
Action
Find a Request TemplateFinds request templates by name or ID and returns the matching templates.
Action
Find a ServiceFinds services by service number or customer ID and returns the matching services.
Action
Find a TaskFinds tasks by task ID, customer ID or request ID and returns the matching tasks.
Action
Find a TicketFinds tickets by ticket ID or customer ID and returns the matching tickets.
Action
Update ContactUpdates the fields you supply on an existing contact; fields left blank are unchanged.
Action
Update CustomerUpdates the fields you supply on an existing customer; fields left blank are unchanged.
Action
Update OrderUpdates the fields you supply on an existing order; fields left blank are unchanged.
Action
Update TaskUpdates the fields you supply on an existing task; fields left blank are unchanged.
Action
Update TicketUpdates the fields you supply on an existing ticket; fields left blank are unchanged.
Action
Upload File/AttachmentUploads a file (base64 content) and attaches it to a customer, order, request, task or ticket; returns the new file's ID.
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 Rev.io
Rev.io to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Rev.io to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Rev.io to StripeStripe is a payment processing platform for online businesses.
Rev.io to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Rev.io to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
Rev.io to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
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
Rev.io and Luma, answered
What can start an automation from Rev.io?
Any of Rev.io's 17 triggers in the catalog, including Customer Profile Updated, New Bill, New Contact and New Customer. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Luma when something happens in Rev.io?
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 Rev.io?
Luma has no triggers in the catalog today, so automations start in Rev.io. 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 Rev.io 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 Rev.io 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.