---
title: "Connect Dastra to Luma - APIANT.ai"
description: "When \"New Task\" fires in Dastra, 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/dastra-to-luma"
---

# Connect Dastra to Luma

When **New Task** fires in [Dastra](https://apiant.ai/connections/dastra), 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.

Dastra **1** trigger Dastra **17** 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 Dastra 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 Dastra can start in Luma

- When **New Task** in Dastra then **Add ticket type** in Luma
- When **New Task** in Dastra 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 Dastra and Luma

## Triggers and actions 1 trigger · 34 actions

- Trigger

**New Task**

Triggers when a new task is created in the chosen Dastra workspace.

- Action

**Add asset**

Creates an asset (software, building, network, data store and so on) in a Dastra workspace and returns the new asset record.

- Action

**Add data processing**

Creates a new data processing activity in your Dastra record of processing activities, in the organizational unit you choose.

- Action

**Attach an Actor to a Data Processing**

Links one or more actors (vendors, internal services, third parties, data controllers) to a data processing activity in your Dastra register, as recipients, data controllers, stakeholders or referents.

- Action

**Create an Actor**

Creates an actor (a vendor, partner, processor or other third party) in a Dastra workspace and returns the new actor record.

- Action

**Create a Task**

Creates a task in a Dastra workspace, with its priority, dates, assignee, project and links to other Dastra records.

- Action

**Delete actor**

Deletes an actor (a controller, processor or other third party) from a Dastra workspace.

- Action

**Delete task**

Deletes a task from a Dastra workspace.

- Action

**Get actor**

Returns one actor (vendor, processor, controller or other third party) from a Dastra workspace by its id, including its contact details, tags, contracts and custom field values.

- Action

**Get data processing**

Returns a data processing activity from your Dastra register of processing activities, including its purposes, recipients, data subject rights and custom fields.

- Action

**Get task**

Returns a single Dastra task by its id, including its state, priority, deadline, assignee and custom field values.

- Action

**List assets**

Returns the assets (software, buildings, networks, data stores and other resources) in a Dastra workspace, optionally filtered by type, state, owner, tag, organizational unit or a search text.

- Action

**List tasks**

Returns the tasks in a Dastra workspace, optionally filtered by state, priority, assignee, project, linked object, dates or search text.

- Action

**Search Actor**

Returns the actors (vendors, data controllers, third parties and other organizations or people) in a Dastra workspace that match the search text and filters.

- Action

**Search Data Processing**

Searches the data processing activities in a Dastra workspace by text and optional filters, returning every matching activity with its full record.

- Action

**Update actor**

Updates an existing actor (vendor, partner or person) in a Dastra workspace. Fields you leave blank keep their current values.

- Action

**Update data processing**

Updates an existing data processing activity in a Dastra workspace, changing only the fields you fill in, and returns the updated record.

- Action

**Update task**

Updates an existing Dastra task. Fields you leave blank keep their current values.

- 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

- [ **Dastra** Dastra is a simple and guided data protection solution to make your entire organization accountable for...](https://apiant.ai/connections/dastra)
- [ **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 Dastra

- [ **Dastra to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/dastra-to-hubspot)
- [ **Dastra to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/dastra-to-salesforce)
- [ **Dastra to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/dastra-to-slack)
- [ **Dastra to Google Sheets** Google Sheets](https://apiant.ai/connect/dastra-to-google-sheets)
- [ **Dastra to Gmail** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/dastra-to-gmail)
- [ **Dastra to Google Calendar** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/dastra-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](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

## Dastra and Luma, answered

###

### What can start an automation from Dastra?

Any of Dastra's 1 trigger in the catalog, including New Task. Describe the moment in plain language and your agent picks the right one.

###

### What can your agent do in Luma when something happens in Dastra?

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 Dastra?

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