---
title: "Connect DevCycle to Livestorm - APIANT.ai"
description: "When \"New Feature Created\" fires in DevCycle, your agent runs \"Create Event\" in Livestorm."
canonical: "https://apiant.ai/connect/devcycle-to-livestorm"
---

# Connect DevCycle to Livestorm

When **New Feature Created** fires in [DevCycle](https://apiant.ai/connections/devcycle), your agent runs **Create Event** in [Livestorm](https://apiant.ai/connections/livestorm). Describe the whole flow and it is built, tested on every scenario and kept running.

DevCycle **1** trigger DevCycle **12** actions Livestorm **15** actions

What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.

## What do you want DevCycle and Livestorm 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 DevCycle can start in Livestorm

- When **New Feature Created** in DevCycle then **Create Event** in Livestorm
- When **New Feature Created** in DevCycle then **Update Event** in Livestorm

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 DevCycle and Livestorm

## Triggers and actions 1 trigger · 27 actions

- Trigger

**New Feature Created**

Triggers when a new feature is created in a DevCycle project.

- Action

**Add feature**

Creates a new feature flag in a DevCycle project, with optional variations, variables and per-environment targeting.

- Action

**Add project**

Creates a new project in your DevCycle organization.

- Action

**Add variable**

Creates a new variable in a DevCycle project, optionally attached to a feature.

- Action

**Delete feature**

Deletes a DevCycle feature from a project, optionally deleting its associated variables too.

- Action

**Get feature**

Returns a DevCycle feature, including its variations, variables and environment targeting configurations.

- Action

**List environments**

Returns the environments (development, staging, production, etc.) in a DevCycle project, including their keys and SDK keys.

- Action

**List features**

Returns the features in a DevCycle project, optionally filtered by type, status, staleness, keys or a search term.

- Action

**List projects**

Returns the DevCycle projects the connected account has permission to view.

- Action

**List variables**

Returns the variables in a DevCycle project, optionally filtered by feature, type, status or search text.

- Action

**Update EdgeDB**

Turns EdgeDB on or off for a DevCycle project and returns the updated project.

- Action

**Update feature**

Updates an existing feature in a DevCycle project, such as its name, description, type, tags, variations, variables or environment targeting.

- Action

**Update variable**

Updates an existing variable in a DevCycle project, such as its name, description, type, tags or key.

- Action

**Create Event**

Creates a new Livestorm event with its first session, either from scratch or by duplicating the settings of an existing event.

- Action

**Create Registrant**

Registers a person for an upcoming Livestorm event session, with their email, name, registration fields and UTM tracking data.

- Action

**Create Session**

Schedules a new session for an existing Livestorm event. Returns the created session, including its room link, status and scheduled start time.

- Action

**Find People**

Finds people in your Livestorm workspace by email address, optionally limited to participants or team members.

- Action

**Find Session**

Finds event sessions in your Livestorm workspace whose name matches the one you give, optionally narrowed by status and date range. Returns the matching sessions and the first match.

- Action

**Get event**

Returns a single Livestorm event, including its title, status, registration link, settings, owner and registration fields.

- Action

**Get person**

Returns the details of a person in your Livestorm workspace, such as their name, email, role and timezone.

- Action

**Get session**

Returns a single Livestorm session, including its status, schedule, room link and attendee counts, optionally with its event, people, chat messages, questions or recordings.

- Action

**List events**

Returns the events in your Livestorm workspace, optionally filtered by title, scheduling status, tag, or creation and update dates.

- Action

**List sessions**

Returns the sessions across all events in your Livestorm workspace, optionally filtered by status, scheduled start date, creation date or last update date.

- Action

**Remove Event**

Deletes a single Livestorm event.

- Action

**Remove Registrant**

Removes a registrant from a Livestorm event session, cancelling their registration.

- Action

**Remove Session**

Deletes a single Livestorm event session.

- Action

**Update Event**

Updates an existing Livestorm event, changing only the details you fill in, such as its title, description, status or room settings.

- Action

**Update Session**

Updates a Livestorm session's name, start date/time or timezone. Fields left blank keep their current values.

## Each app on its own

- [ **DevCycle** DevCycle is a feature flagging platform that's easy to use, scalable and lightning fast.](https://apiant.ai/connections/devcycle)
- [ **Livestorm** Livestorm is an end-to-end engagement platform that enables you to connect, engage, and capture actionable...](https://apiant.ai/connections/livestorm)

Reviews

## What our customers say

## More from DevCycle

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

## More into Livestorm

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

Questions

## DevCycle and Livestorm, answered

###

### What can start an automation from DevCycle?

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

###

### What can your agent do in Livestorm when something happens in DevCycle?

Any of Livestorm's 15 actions, including Create Event, Create Registrant, Create Session and Update Event. Your agent maps the data both ways and tests every scenario before it ships.

###

### Can it also run from Livestorm to DevCycle?

Livestorm has no triggers in the catalog today, so automations start in DevCycle. If you need the other direction, ask: your agent reads Livestorm's API documentation and adds it.

###

### Do I have to build a connector for DevCycle or Livestorm?

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 DevCycle and Livestorm 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.
