--- title: "Connect TidyHQ to Luma - APIANT.ai" description: "When \"Contact Added to Group\" fires in TidyHQ, your agent runs \"Block contact\" in Luma." canonical: "https://apiant.ai/connect/tidyhq-to-luma" --- # Connect TidyHQ to Luma When **Contact Added to Group** fires in [TidyHQ](https://apiant.ai/connections/tidyhq), your agent runs **Block contact** in [Luma](https://apiant.ai/connections/luma). Describe the whole flow and it is built, tested on every scenario and kept running. TidyHQ **10** triggers TidyHQ **19** 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 TidyHQ 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 TidyHQ can start in Luma - When **Contact Added to Group** in TidyHQ then **Block contact** in Luma - When **Contact Created** in TidyHQ 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 TidyHQ and Luma ## Triggers and actions 10 triggers · 36 actions - Trigger **Contact Activated** Triggers when a contact has been activated (after new membership, or reactivated e.g. restored from trash). - Trigger **Contact Added to Group** Triggers when a contact has been added to a group. - Trigger **Contact Created** Triggers when a new contact has been created for the first time. - Trigger **Contact Deactivated** Triggers when a contact has been deleted. - Trigger **Contact Removed From Group** Triggers when a contact has been removed from a group. - Trigger **Event Deleted** Triggers when an event is deleted. - Trigger **Event Ticket Created** Triggers when an event ticket is created. - Trigger **Event Ticket Deleted** Triggers when an event ticket is deleted. - Trigger **Event Ticket Updated** Triggers when an event ticket is updated. - Trigger **Event Updated** Triggers when an event is updated. - Action **Add Contact Note** Adds a note to a TidyHQ contact. - Action **Add Contact To Group** Adds an existing TidyHQ contact to one of your groups. - Action **Add Event Ticket** Creates a new ticket type on a TidyHQ event. - Action **Add invoice** Creates a new invoice in TidyHQ with your own line items, optionally addressed to a contact. - Action **Create Contact** Creates a new contact in your TidyHQ organisation. - Action **Delete Contact** Deletes a contact from your TidyHQ organisation. - Action **Delete Contact Note** Deletes a note from a TidyHQ contact. - Action **Delete Event** Deletes an event from your TidyHQ organisation. - Action **Delete Event Ticket** Deletes a ticket type from a TidyHQ event. - Action **Find Contact** Finds contacts in your TidyHQ organisation whose details match the search text. - Action **Get contact** Returns a single TidyHQ contact by its id, including its custom field values. - Action **Get event** Returns a single TidyHQ event by its ID, with all of its details. - Action **List contacts** Returns the contacts in your TidyHQ organisation, optionally narrowed by search text. - Action **List event tickets** Returns the ticket types available on a TidyHQ event. - Action **List groups** Returns the contact groups in your TidyHQ organisation. - Action **Remove Contact From Group** Removes a contact from a TidyHQ group. - Action **Update Contact** Updates an existing TidyHQ contact's details. Only the fields you fill in are changed. - Action **Update Event** Updates an existing TidyHQ event's name, times, location or description. - Action **Update Event Ticket** Updates a ticket type on a TidyHQ event, such as its name, price, quantity or sales window. Fields left blank are not changed. - 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 - [ **TidyHQ** When your group needs to collect membership dues, communicate with everyone and keep track of your finances...](https://apiant.ai/connections/tidyhq) - [ **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 TidyHQ - [ **TidyHQ to Trello** Trello is a visual collaboration tool that organizes projects into boards, lists, and cards.](https://apiant.ai/connect/tidyhq-to-trello) - [ **TidyHQ to Zoom** Zoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...](https://apiant.ai/connect/tidyhq-to-zoom) - [ **TidyHQ to Twilio** Cloud communications platform for sending SMS/MMS messages, making and managing voice calls, and looking up...](https://apiant.ai/connect/tidyhq-to-twilio) - [ **TidyHQ to Typeform** Build and publish online forms, surveys, and quizzes with Typeform.](https://apiant.ai/connect/tidyhq-to-typeform) - [ **TidyHQ to Webflow** Webflow is a professional website builder and CMS for designing, building, and launching responsive...](https://apiant.ai/connect/tidyhq-to-webflow) - [ **TidyHQ to Wix** The Wix website builder gives businesses of any size the tools to create, manage and grow a fully integrated...](https://apiant.ai/connect/tidyhq-to-wix) ## 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 ## TidyHQ and Luma, answered ### ### What can start an automation from TidyHQ? Any of TidyHQ's 10 triggers in the catalog, including Contact Added to Group, Contact Created, Contact Removed From Group and Event Ticket Created. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in Luma when something happens in TidyHQ? 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 TidyHQ? Luma has no triggers in the catalog today, so automations start in TidyHQ. 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 TidyHQ 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 TidyHQ 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.