--- title: "Connect Copper to Luma - APIANT.ai" description: "When \"New Activity\" fires in Copper, your agent runs \"Add ticket type\" in Luma." canonical: "https://apiant.ai/connect/copper-to-luma" --- # Connect Copper to Luma When **New Activity** fires in [Copper](https://apiant.ai/connections/copper), 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. Copper **17** triggers Copper **22** actions Luma **17** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want Copper 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 Copper can start in Luma - When **New Activity** in Copper then **Add ticket type** in Luma - When **New Company** in Copper 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 Copper and Luma ## Triggers and actions 17 triggers · 39 actions - Trigger **New Activity** Triggers when a new activity is created. - Trigger **New Company** Triggers when a new Company is created in Copper. - Trigger **New Lead** Triggers when a Lead is created in Copper. - Trigger **New Opportunity** Triggers when an Opportunity is created in Copper. - Trigger **New Person** Triggers when a new Person is created in Copper. - Trigger **New Project** Triggers when a new Project is created in Copper. - Trigger **New Task** Triggers when a new Task is created in Copper. - Trigger **Updated Company** Triggers when a Person's Company is changed. - Trigger **Updated Contact Type** Triggers when a Person's Contact Type is changed. - Trigger **Updated Lead** Triggers when a Lead is changed. - Trigger **Updated Lead Status** Triggers when a Lead's status is changed. - Trigger **Updated Opportunity** Triggers when an Opportunity is changed. - Trigger **Updated Opportunity Stage** Triggers when an Opportunity's stage is changed. - Trigger **Updated Opportunity Status** Triggers when an Opportunity's status is changed. - Trigger **Updated Person** Triggers when a Person is changed. - Trigger **Updated Project** Triggers when a Project is changed. - Trigger **Updated Task** Triggers when a Task is changed. - Action **Associate to Project** This Action allows you to relate an existing Project to and existing CRM object; both objects have to exist before you run this Action. This Action expects two ID's for input: the ID of the CRM record you want to relate to and the Project ID you want to relate it with. This Action was designed to be used in multi-step Zaps, where you already have a Project ID and an related record ID (e.g. a Person) from previous steps. - Action **Create Activity** Logs a new Activity on a Person, Company, Opportunity, or Lead. - Action **Create Company** Creates a new Company. - Action **Create Lead** Creates a new Lead. - Action **Create Opportunity** Creates a new Opportunity. - Action **Create Person** Creates a new Person. - Action **Create Project** Creates a new Project. - Action **Create Task** Creates a new Task. - Action **Create/Update Company** Creates or Updates a Company depending on the match criteria. - Action **Create/Update Lead** Creates or Updates a Lead depending on the match criteria. - Action **Create/Update Opportunity** Creates or Updates an Opportunity based off of a match criteria. - Action **Create/Update Person** Creates or Updates a Person depending on the match criteria. - Action **Create/Update Project** Creates or Updates a Project depending on the match criteria. - Action **Search for a Company** Searches for an existing company in Copper. - Action **Search for an Activity** Searches for an existing activity in Copper. - Action **Search for a Opportunity** Searches for an existing opportunity in Copper. - Action **Search for a Person** Searches for an existing person in Copper. - Action **Search for a Project** Searches for an existing project in Copper. - Action **Update Company** Updates a Company depending on the match criteria. - Action **Update Opportunity** Updates an Opportunity based off of a match criteria. - Action **Update Person** Updates a Person depending on the match criteria. - Action **Update Project** Updates a Project depending on the match criteria. - 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 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 - [ **Copper** Copper is a Recommended for Google Workspace CRM that improves productivity and increases visibility across...](https://apiant.ai/connections/copper) - [ **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 Copper - [ **Copper to LeadSimple** LeadSimple is the CRM that property management and real estate companies use to scale and grow.](https://apiant.ai/connect/copper-to-leadsimple) - [ **Copper to Nvidia** API platform for deploying GPU-accelerated AI models, including inference microservices and a container...](https://apiant.ai/connect/copper-to-nvidia) - [ **Copper to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/copper-to-hubspot) - [ **Copper to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/copper-to-salesforce) - [ **Copper to Google Sheets** Google Sheets](https://apiant.ai/connect/copper-to-google-sheets) - [ **Copper to Google Drive** Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...](https://apiant.ai/connect/copper-to-google-drive) ## 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](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 ## Copper and Luma, answered ### ### What can start an automation from Copper? Any of Copper's 17 triggers in the catalog, including New Activity, New Company, New Lead and New Opportunity. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in Luma when something happens in Copper? 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 Copper? Luma has no triggers in the catalog today, so automations start in Copper. 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 Copper 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 Copper 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.