--- title: "Connect Concord CLM to Luma - APIANT.ai" description: "When \"New agreement\" fires in Concord CLM, your agent runs \"Add ticket type\" in Luma." canonical: "https://apiant.ai/connect/concord-clm-to-luma" --- # Connect Concord CLM to Luma When **New agreement** fires in [Concord CLM](https://apiant.ai/connections/concord-clm), 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. Concord CLM **1** trigger Concord CLM **18** 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 Concord CLM 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 Concord CLM can start in Luma - When **New agreement** in Concord CLM then **Add ticket type** in Luma - When **New agreement** in Concord CLM 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 Concord CLM and Luma ## Triggers and actions 1 trigger · 37 actions - Trigger **New agreement** Triggers when a new agreement appears in the selected Concord organization. - Action **Add agreement** Creates a new agreement in a Concord organization, either as a blank draft, template or contract, or from an existing template or contract. Returns the new agreement's identifiers. - Action **Add attachment** Uploads a file and attaches it to a Concord agreement, and returns the ID of the new attachment. - Action **Add folder** Creates a new folder inside an existing folder of a Concord organization and returns the new folder. - Action **Add member to agreement** Invites a person to an agreement by email with the chosen permission level and sends them an invitation message. Returns the agreement's id, unique identifier and status. - Action **Create a New Document From a Template** Creates a new Concord document from an automated template, filling in its variables and optionally inviting people to it. - Action **Create an Executed Document** Creates an agreement in Concord with the status of an executed contract, rather than a draft or template. Returns the new agreement's identifiers. - Action **Create webhook - Document Fully Approved** Creates a Concord webhook integration that calls the given URL when an agreement is fully approved. - Action **Create webhook - Document Fully Signed** Creates a Concord webhook integration that calls the given address when an agreement is fully signed. - Action **Create webhook - Signature Provided** Creates a Concord webhook integration that calls the given address whenever a new signature is added to an agreement. - Action **Delete agreement** Permanently deletes an agreement from a Concord organization. - Action **Get agreement** Returns one Concord agreement by its UID, including its title, status, folder, tags, permission and creation details. An error occurs if the agreement is not found. - Action **List agreements** Returns the agreements in a Concord organization's inbox, filtered by stage and optionally by creator, tags, dates, parties and search text. - Action **List automated templates** Returns the automated templates available in a Concord organization, with each template's id, title and description. - Action **List folders** Returns the folder tree of a Concord organization: the root folder with its nested subfolders, access settings and document counts. - Action **List organizations** Returns every Concord organization the connected user belongs to, including each organization's name, subscription, and the user's role in it. - Action **Move agreement** Moves an agreement into a different folder in a Concord organization. - Action **Request signature** Requests signatures on an agreement from its signers. Colleagues are added to the agreement, external signers are emailed an invitation, and when a signing order is enabled the request goes to the next signer in that order. - Action **Update agreement** Updates the status of an existing Concord agreement, setting it to Signing or Broken. - 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 - [ **Concord CLM** Concord is a full contract lifecycle management platform with drafting, approvals, e-signature and storage -...](https://apiant.ai/connections/concord-clm) - [ **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 Concord CLM - [ **Concord CLM to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/concord-clm-to-hubspot) - [ **Concord CLM to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/concord-clm-to-salesforce) - [ **Concord CLM to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/concord-clm-to-slack) - [ **Concord CLM to Google Sheets** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/concord-clm-to-google-sheets) - [ **Concord CLM to Gmail** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/concord-clm-to-gmail) - [ **Concord CLM to Google Calendar** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/concord-clm-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 ## Concord CLM and Luma, answered ### ### What can start an automation from Concord CLM? Any of Concord CLM's 1 trigger in the catalog, including New agreement. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in Luma when something happens in Concord CLM? 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 Concord CLM? Luma has no triggers in the catalog today, so automations start in Concord CLM. 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 Concord CLM 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 Concord CLM 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.