Integration
Connect Mendato to Luma
When New Employee fires in Mendato, 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 Mendato 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 Mendato can start in Luma
When New Employee in Mendato
then Add ticket type in Luma
When New Subcontractor in Mendato
then Apply contact tag 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 Mendato and Luma
Triggers and actions 2 triggers · 42 actions
Trigger
New EmployeeTriggers when a new employee is added in Mendato. Optional filters limit which employees fire the trigger.
Trigger
New SubcontractorTriggers when a new subcontractor is added in Mendato.
Action
Add employeeCreates a new employee in Mendato.
Action
Add materialGraphQL mutation createMaterial.
Action
Add objectGraphQL mutation createObject (cleaning object/property).
Action
Add orderCreates a new order (Auftrag) for an object, with the services to perform, and optionally the materials used and the employees or subcontractors assigned.
Action
Add prospectCreates a new prospect (potential customer) in Mendato, optionally with contact persons and a first prospect object.
Action
Add quoteGraphQL mutation createQuote.
Action
Add supplierGraphQL mutation createSupplier.
Action
Add ticketCreates a ticket (a complaint, extra request, material demand or damage report) for an object in Mendato.
Action
Add time recordCreates a time record for an employee in Mendato, with start and end time, optional journey start, break duration and the object (site) worked at.
Action
Create Credit NoteCreates a credit note (Gutschrift) for a subcontractor in Mendato, with its line items, dates and texts.
Action
Create CustomerCreates a new customer (person or company) in Mendato with address, contact and billing details.
Action
Create EstimateCreates a new estimate
Action
Create InvoiceCreates an invoice for a customer in Mendato, with its line items, dates and texts, optionally completing and sending it right away.
Action
Create SubcontractorCreates a new subcontractor
Action
Find CustomerReturns up to 100 customers whose number, name, email address or contact person matches the search text.
Action
Find employees by criteriaReturns the employees that match the given criteria, such as name or personnel number, status, city or ZIP, supervisor or driving licence.
Action
Find invoices by criteriaReturns up to 100 invoices that match the search text, statuses, date ranges, payment state, customer, order, service or object you specify.
Action
Find SubcontractorReturns up to 100 subcontractors whose number, name or other details match the search text.
Action
Get customerReturns a single customer by id, including contact details, address, email addresses, tax details, note and tags.
Action
Get orderReturns a single order (Auftrag) by its id, including its object, status, dates, staffing requirements and services.
Action
Get prospectReturns a single prospect (lead) by its id, with address, contact details, outcome and contact persons.
Action
Get QuoteReturns a single quote (Angebot) by its id, including its number, status, dates, customer or prospect, texts and line items.
Action
Get SupplierReturns a single supplier (Lieferant) by its id, with name, address, contact and tax details.
Action
Get time recordReturns a single time record by its id, including its date, start and end times, breaks, employee and object.
Action
Update customerUpdates an existing customer's name, address, contact details and email addresses. Fields left blank keep their current values.
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 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 Mendato
Mendato to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Mendato to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Mendato to StripeStripe is a payment processing platform for online businesses.
Mendato to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Mendato to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
Mendato 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.
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
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
Mendato and Luma, answered
What can start an automation from Mendato?
Any of Mendato's 2 triggers in the catalog, including New Employee and New Subcontractor. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Luma when something happens in Mendato?
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 Mendato?
Luma has no triggers in the catalog today, so automations start in Mendato. 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 Mendato 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 Mendato 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.