---
title: "Connect Timely Time Tracking to Luma - APIANT.ai"
description: "When \"New Client\" fires in Timely Time Tracking, your agent runs \"Add ticket type\" in Luma."
canonical: "https://apiant.ai/connect/timely-time-tracking-to-luma"
---

# Connect Timely Time Tracking to Luma

When **New Client** fires in [Timely Time Tracking](https://apiant.ai/connections/timely-time-tracking), 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.

Timely Time Tracking **8** triggers Timely Time Tracking **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 Timely Time Tracking 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 Timely Time Tracking can start in Luma

- When **New Client** in Timely Time Tracking then **Add ticket type** in Luma
- When **New or Updated Person** in Timely Time Tracking then **Create Calendar Person** 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 Timely Time Tracking and Luma

## Triggers and actions 8 triggers · 36 actions

- Trigger

**New Client**

Triggered when a new client is created

- Trigger

**New or Updated Person**

Triggered when a person is created or updated in Timely

- Trigger

**New or Updated Project**

Triggers when a project is created or updated.

- Trigger

**New or Updated Time Entry**

Triggers when time entries are created or updated.

- Trigger

**New Project**

Triggered when a new project is created

- Trigger

**New Time Entry**

Triggered when a new time entry is created

- Trigger

**New Workspace**

Triggers when a workspace is created.

- Trigger

**Project Updated (Only Admin Users)**

Triggers when any project is updated in Timely. Fires for ALL project changes (name, budget, rate, archive, labels, users, etc. Can only be used by Timely Admin users. WARNING: avoid chaining this trigger to actions that write back to the same project (e. g. via "Update Project Name") in the source system without a guard — that can create an infinite update loop.

- Action

**Add tag**

Create a tag.

- Action

**Create Client**

Creates a Client

- Action

**Create Person**

Creates a new person in the workspace.

- Action

**Create Project**

Creates a project.

- Action

**Create Task**

Creates a task.

- Action

**Delete project**

Delete a project.

- Action

**Delete time entry**

Delete a time entry.

- Action

**Find Client**

Returns the clients in a Timely workspace whose name matches the given text.

- Action

**Find Project**

Returns the projects whose name contains the specified text.

- Action

**Find Tag List and Tag**

Finds a tag list and a specific tag if specified.

- Action

**Find time entries by criteria**

Search time entries by date range, user, project.

- Action

**Find User**

Finds a User

- Action

**Get Task**

Retrieves a single task (forecast) by its id.

- Action

**Log Time Entry**

Logs a new time entry against a project.

- Action

**Start timer**

Start the timer on a time entry.

- Action

**Stop timer**

Stop the running timer on a time entry.

- Action

**Update client**

Update a client.

- Action

**Update Project Name**

Updates only the name of an existing project. Look up the project by Timely Project ID or by External ID (recommended when the source-of-truth system stores the Timely external_id, e.g. NetSuite).

- Action

**Update time entry**

Update a logged time entry.

- 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

- [ **Timely Time Tracking** Timely Time Tracking automates company time tracking, so everyone can focus on the work that matters.](https://apiant.ai/connections/timely-time-tracking)
- [ **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 Timely Time Tracking

- [ **Timely Time Tracking to Zelothorn** Zelothorn publishes plain-English explanations of US public companies built from SEC filings and earnings...](https://apiant.ai/connect/timely-time-tracking-to-zelothorn)
- [ **Timely Time Tracking to Trello** Trello is a visual collaboration tool that organizes projects into boards, lists, and cards.](https://apiant.ai/connect/timely-time-tracking-to-trello)
- [ **Timely Time Tracking to Zoom** Zoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...](https://apiant.ai/connect/timely-time-tracking-to-zoom)
- [ **Timely Time Tracking to Twilio** Cloud communications platform for sending SMS/MMS messages, making and managing voice calls, and looking up...](https://apiant.ai/connect/timely-time-tracking-to-twilio)
- [ **Timely Time Tracking to Typeform** Build and publish online forms, surveys, and quizzes with Typeform.](https://apiant.ai/connect/timely-time-tracking-to-typeform)
- [ **Timely Time Tracking to Webflow** Webflow is a professional website builder and CMS for designing, building, and launching responsive...](https://apiant.ai/connect/timely-time-tracking-to-webflow)

## 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

## Timely Time Tracking and Luma, answered

###

### What can start an automation from Timely Time Tracking?

Any of Timely Time Tracking's 8 triggers in the catalog, including New Client, New or Updated Person, New or Updated Project and New or Updated Time Entry. Describe the moment in plain language and your agent picks the right one.

###

### What can your agent do in Luma when something happens in Timely Time Tracking?

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 Timely Time Tracking?

Luma has no triggers in the catalog today, so automations start in Timely Time Tracking. 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 Timely Time Tracking 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 Timely Time Tracking 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.
