Integration
Connect Globaledit to Luma
When New Collection fires in Globaledit, 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 Globaledit 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 Globaledit can start in Luma
When New Collection in Globaledit
then Add ticket type in Luma
When New Collection in Globaledit
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 Globaledit and Luma
Triggers and actions 1 trigger · 50 actions
Trigger
New CollectionTriggers when a new collection or project is created in an account.
Action
Add Asset CommentsAdds a comment, or a reply to a comment, on one or more assets.
Action
Add Assets to CollectionAdds assets to a collection.
Action
Add Folder CommentAdds a comment, or a reply to a comment, on a folder.
Action
Apply Tags to AssetsApplies tags to one or more assets.
Action
Create CollectionCreates a collection in an account.
Action
Create FolderCreates a folder in a workspace, optionally inside a parent folder.
Action
Create TagsCreates one or more asset tags in the organization.
Action
Create WorkspaceCreates a workspace in an account.
Action
Delete AssetsDeletes assets from a workspace.
Action
Delete CollectionDeletes a collection.
Action
Delete TagsDeletes organization asset tags.
Action
Get Asset MetadataReturns the metadata field values of one metadata schema for the given assets.
Action
Get Asset PreviewReturns a temporary download link to an asset's preview image at the chosen size.
Action
Get Asset SummaryReturns an asset's summary: name, type, size, folder path, versions and properties.
Action
Get Collection AssetsReturns the assets in a collection.
Action
Get Collection SummaryReturns a collection's details by ID.
Action
Get Folder AssetsReturns the assets in a folder.
Action
Get FoldersReturns every folder and subfolder in a workspace.
Action
Get User InfoReturns the profile of the user the API key acts as, including the organizations it belongs to.
Action
Get WorkspacesReturns the accounts and workspaces the user can see in an organization.
Action
List CollectionsReturns the collections and projects the user can access in an account.
Action
List Organization UsersReturns the users in an organization.
Action
List TagsReturns every asset tag defined in the organization.
Action
Remove Assets from CollectionRemoves assets from a collection.
Action
Remove Tags from AssetsRemoves tags from one or more assets.
Action
Rename FolderRenames a folder in a workspace.
Action
Update Asset NameRenames an asset.
Action
Update CollectionUpdates a collection's name and description.
Action
Update MetadataSets metadata field values on one or more assets.
Action
Update RatingSets a rating (stars, color, status or a yes/no rating) on one or more assets.
Action
Update TagRenames an organization asset tag.
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 Globaledit
Globaledit to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Globaledit to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Globaledit to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Globaledit to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Globaledit to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Globaledit to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
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
Globaledit and Luma, answered
What can start an automation from Globaledit?
Any of Globaledit's 1 trigger in the catalog, including New Collection. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Luma when something happens in Globaledit?
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 Globaledit?
Luma has no triggers in the catalog today, so automations start in Globaledit. 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 Globaledit 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 Globaledit 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.