Integration
Connect Ortto to Luma
When Fields Updated fires in Ortto, 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 Ortto 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 Ortto can start in Luma
When Fields Updated in Ortto
then Add ticket type 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 Ortto and Luma
Triggers and actions 4 triggers · 27 actions
- Fields Updated
Triggers when the specified field(s) of a record have been updated in your Ortto account.
- New Activity Occurred
Triggers when a new Ortto activity occurs.
- New Record Created
Triggers when a new record (contact or organization) has been added to your Ortto account.
- Tag Added/Removed
Triggers when a tag has beed added to, or removed from, a record.
- Add Custom Field
Create a new custom field on the person or organization schema in Ortto.
- Create Record
Create a new record (person, organization), or update an existing record in your Ortto account.
- Delete Record
Archive, restore, or permanently delete a person or organization record in Ortto.
- Get Record
Fetches one or more people, or one or more accounts, by their Ortto ids, returning whichever fields you ask for.
- List Activities
Retrieve the activity feed for a given contact in Ortto.
- Opt Out From SMS
Opt out a person from all SMS communications.
- Search or Create Records
Search your Ortto data for a record based on the provided field or optionally create one if none is found.
- Tag/Untag Records
Adds or removes tags on a person or an account in Ortto, matching the record by email address or account name.
- Unsubscribe a Person
Unsubscribe a person from all emails.
- Update Audience Subscription
Subscribe or unsubscribe a person to/from an Ortto audience.
- 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.
- Add host
Adds a host to a Luma event, as a manager or as check-in staff, by email address.
- 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.
- 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.
- 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.
- Cancel event
Cancels a Luma event. The event is permanently deleted, all guests are notified, and paid guests can optionally be refunded.
- 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.
- 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.
- Get event
Returns the details of a Luma event, including its schedule, location, visibility, hosts and, for events you manage, guest counts by status.
- 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.
- Import contacts
Imports contacts into your Luma calendar so you can invite them to events and send them newsletters, optionally tagging them.
- List contacts
Returns the contacts (people) on your Luma calendar, optionally filtered by a name/email search, tags or membership status.
- List events
Returns the events on your Luma calendar, optionally filtered by date range, submission status, platform and access level.
- 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.
- List ticket types
Returns every ticket type set up for a Luma event, including its name, price and capacity.
- 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.
- 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.
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 Ortto
Ortto to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Ortto to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Ortto to StripeStripe is a payment processing platform for online businesses.
Ortto to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Ortto to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
Ortto to PipedrivePipedrive is a sales CRM and pipeline management tool.
More into Luma
HubSpot to LumaHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to LumaGoogle Sheets
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
Ortto and Luma, answered
What can start an automation from Ortto?
Any of Ortto's 4 triggers in the catalog, including Fields Updated, New Activity Occurred, New Record Created and Tag Added/Removed. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Luma when something happens in Ortto?
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 Ortto?
Luma has no triggers in the catalog today, so automations start in Ortto. 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 Ortto 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 Ortto 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.