October 7, 2026

Build LaunchBay automations by just asking using AI

NEW FEATURE
MCP
Automations

Part of our 31 Customer Improvements series, where we ship one feature our customers asked for every day this month.

You already know what the automation should do: "When the client finishes the intake form, start the kickoff stage and email me." Now you can set it up by saying exactly that.

Building it by hand has always meant opening the automation builder, picking a trigger type, finding the right task in a dropdown, choosing a status, then doing it all again for each action. It's quick once you know the builder. It's slow when you're setting up onboarding automation across ten projects, or fixing the one automation that stopped doing what you meant.

What's new

An AI assistant connected to LaunchBay can now read, create, edit, and delete your project automations. That includes Claude or any other assistant that supports MCP. Ask in plain English, and the assistant builds the automation from your project's real tasks, stages, and pages.

It works on live projects and on templates. Build an automation into a project template once, and every project created from that template gets it, so every client implementation starts with the same safeguards. Your assistant can edit the template itself, too.

It can:

  • Show you what's running. Get a plain-English summary of every automation on a project: what triggers it, any delay, and what it does.
  • Build new automations. Describe the trigger, the delay, and the actions, and it creates the automation.
  • Change existing ones. Rename an automation, change its delay, or swap an action, and the rest stays as it was.
  • Clean up. Remove automations you no longer need.

Automations built this way are the same as the ones you build by hand. They show up in the Automations tab and open in the usual editor, so you can keep working on them there.

Try asking

Here are some things you can ask for, and what gets set up.

You askThe automation
"When the client completes 'Sign the proposal', activate 'Kickoff call' and make it due in 3 days." Trigger: a task is completed.
Action: activate a task, with a due date 3 days after activation.
"If they pick 'Premium' on the intake form, show the Premium Resources page and tag the project VIP." Trigger: a form field gets a specific answer.
Actions: show a portal page and add a project tag.
"Two days after the Design stage is done, bring in the Launch stage from our Web Build template." Trigger: a stage is completed.
Delay: 2 days.
Action: import a stage from a template.
"Whenever a task gets tagged 'Blocked', email ops@example.com." Trigger: a tag is added to any task.
Action: send an email notification.
"What automations are on the Acme onboarding project?" A plain-English list of each automation's triggers, delay, and actions.

If something is unclear, like which of two tasks called "Review" you meant, the assistant asks before it builds anything.

Get started

  1. Connect your AI assistant to the LaunchBay MCP server using our MCP setup guide. If it's already connected, you have the new tools now.
  2. Ask it to show a project's automations so you can see what's already there.
  3. Describe the automation you want, check the summary it gives you, and confirm.

Then open the project's Automations tab to see what you built. We'd like to hear what you automate first. If the assistant can't do something you ask, it can send us feedback directly.

‍

Get back to the work you're best at.

LaunchBay's AI-powered client portal handles the collecting, reminding, and following up, so your team spends less time chasing clients and more time delivering.

Ready to stop chasing?