--- title: "Connect COR to Luma - APIANT.ai" description: "When \"Create Brand\" fires in COR, your agent runs \"Add ticket type\" in Luma. Describe the whole flow and it is built, tested on every scenario and kept running." canonical: "https://apiant.ai/connect/cor-to-luma" --- # Connect COR to Luma When **Create Brand** fires in [COR](https://apiant.ai/connections/cor), your agent runs **Add ticket type** in [Luma](https://apiant.ai/connections/luma). Describe the whole flow and it is built, tested on every scenario and kept running. COR **12** triggers COR **24** actions Luma **19** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want COR and Luma to do together? Give your AI client this address. `https://mcp.apiant.ai` One 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.ai` Start Claude Code there, approve the server, and sign in in the browser page it opens. [Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code) ### 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)](https://apiant.ai/docs/mcp) ### 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)](https://apiant.ai/docs/mcp) ### Zed Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### 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)](https://apiant.ai/docs/mcp) ### 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)](https://apiant.ai/docs/mcp) Example flows ## What COR can start in Luma - When **Create Brand** in COR then **Add ticket type** in Luma - When **Create Client** in COR 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 COR and Luma ## Triggers and actions 12 triggers · 43 actions - Trigger **Create Brand** Triggers when a new brand is created in COR. - Trigger **Create Client** Triggers when a new client is created in COR. - Trigger **Create Hour** Triggers when a new time entry is logged in COR. - Trigger **Create Invoice** Triggers when a new transaction is recorded in COR. COR has no separate invoice record, so this watches all transactions, invoices included; use the type field to tell them apart. - Trigger **Create Product** Triggers when a new product is created in COR. - Trigger **Create Project** Triggers when a new project is created in COR. - Trigger **Create Task** Triggers when a new task is created in COR. Returns the new task's details. - Trigger **Create User** Triggers when a new user is created in COR. - Trigger **Updated Client** Triggers when an existing client is changed in COR. - Trigger **Updated Project** Triggers when an existing project is updated in COR. - Trigger **Updated Task** Triggers when a task is changed, such as a new title, status, priority or deadline. Also fires when a new task appears. - Trigger **Updated User** Triggers when a user in COR is created or changed, such as their name, email, role, position or labels. - Action **Add brand** Creates a new brand under a client in COR. - Action **Add team** Creates a new team in COR with a name and, optionally, a description and workspace. Returns the team that was created. - Action **Create Client** Creates a new client in COR with its company details and primary contact, and returns the new client's id. - Action **Create Fee** Creates a fee for a client in COR, with its name, estimate and work order, and optional details such as dates, status and currency. Returns the new fee. - Action **Create Hour** Logs a time entry against a task in COR and returns the new entry's id. - Action **Create Invoice** Creates an invoice (a COR transaction) for the given date, total and currency, optionally linked to a client, and returns the new transaction. - Action **Create Project** Creates a new project for a client in COR and returns the created project. - Action **Create Task** Creates a new task in COR, optionally within a project, and returns the created task. - Action **Delete Project** Deletes a project in COR by its ID. - Action **Delete task** Deletes a task in COR by its ID. - Action **Find clients by name** Returns the clients whose name matches the specified name. - Action **Find projects by name** Returns the COR projects whose name matches the name you search for, including each project's client, project manager, status and budget details. - Action **Get client** Returns a single COR client by its id, including its business name, contact details, website and description. - Action **Get project** Returns a single COR project by its id, including its client, project manager, dates, status, budget figures and assigned labels. An error occurs if the project is not found. - Action **Get task** Returns a single COR task by its id, including its title, project, deadline, status and priority. - Action **List clients** Returns all clients in the COR account, optionally narrowed by filter criteria. - Action **List fees** Returns the fees in the COR account, including each fee's name, estimate, status and dates. - Action **List hours** Returns the time entries logged in the COR account, optionally narrowed by date range, client, project, user, label or team, and sorted as you choose. - Action **List products** Returns all products in the COR account, each with its name, client and brand. - Action **List projects** Returns the company's projects, optionally narrowed by client, team, user, brand, product, dates, status, health or archived state. - Action **List tasks** Returns the tasks in your COR account, optionally narrowed by project, project manager, status and other criteria, and sorted the way you choose. - Action **List teams** Returns the teams in the COR workspace, including each team's name and description. - Action **Update Project** Updates an existing project in COR, changing only the fields you fill in, and returns the updated project. - Action **Update Task** Updates an existing task by its id, changing its title, project, description, deadline, status, priority or archived state, and returns the updated task. - Action **Add event** Adds 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 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. - Action **Add host** Adds a host to a Luma event, as a manager or as check-in staff, by email address. - Action **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. - Action **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. - Action **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. - Action **Cancel event** Cancels a Luma event. The event is permanently deleted, all guests are notified, and paid guests can optionally be refunded. - Action **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. - Action **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. - Action **Get event** Returns the details of a Luma event, including its schedule, location, visibility, hosts and, for events you manage, guest counts by status. - Action **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. - Action **Import contacts** Imports contacts into your Luma calendar so you can invite them to events and send them newsletters, optionally tagging them. - Action **List contacts** Returns the contacts (people) on your Luma calendar, optionally filtered by a name/email search, tags or membership status. - Action **List events** Returns the events on your Luma calendar, optionally filtered by date range, submission status, platform and access level. - Action **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. - Action **List ticket types** Returns every ticket type set up for a Luma event, including its name, price and capacity. - Action **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. - Action **Update event** Updates 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 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. ## Each app on its own - [ **COR** COR is the all-in-one management solution for creative agencies that automate timesheets, through AI, to...](https://apiant.ai/connections/cor) - [ **Luma** Luma is an event management app that gives you the tools to host delightful events.](https://apiant.ai/connections/luma) Reviews ## What our customers say ## More from COR - [ **COR to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/cor-to-hubspot) - [ **COR to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/cor-to-salesforce) - [ **COR to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/cor-to-slack) - [ **COR to Google Sheets** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/cor-to-google-sheets) - [ **COR to Gmail** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/cor-to-gmail) - [ **COR to Google Calendar** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/cor-to-google-calendar) ## More into Luma - [ **HubSpot to Luma** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-luma) - [ **Salesforce to Luma** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-luma) - [ **Slack to Luma** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-luma) - [ **Google Sheets to Luma** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-luma) - [ **Gmail to Luma** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-luma) - [ **Google Calendar to Luma** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-luma) Questions ## COR and Luma, answered ### ### What can start an automation from COR? Any of COR's 12 triggers in the catalog, including Create Brand, Create Client, Create Hour and Create 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 COR? 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 COR? Luma has no triggers in the catalog today, so automations start in COR. 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 COR 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 COR 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.