Skip to content

What is TripWorks Studio?

Studio lets you build your own dashboards, manifests and tools inside TripWorks by describing them, using your live data. No hosting needed.

Written By Melanie Gannone (Super Administrator)

Updated at November 17th, 2026

Studio lets you build your own tools inside TripWorks just by describing them. Type something like "a dashboard of today's departures with the guide, pickup location and any add-ons for each one," and Studio builds it on your live TripWorks data in a minute or two. You can share it with your team, pin it to your menu, and ask for changes in plain words whenever you need them.

There's nothing to host, no code to maintain, and no separate login. Your apps live in TripWorks, next to the rest of your account.

Studio is in early access. We're opening it to companies by request, in small groups. If you'd like to try it, contact TripWorks support or your account manager and we'll add you to the list. Studio is free during early access. Pricing will come later, with plenty of notice before anything changes.
Learn how beta features work
Before you begin. Building and opening Studio apps requires the Use TripWorks Studio permission. Studio settings, including sharing limits, connections and usage, require the Setup integrations catalog permission. Both come with the built-in Owner group, or any custom permission group that includes them. If Studio doesn't appear under More, ask an account admin to add the permission to your group.
Learn how to manage permission groups

In this article

  • What Studio is, and how it differs from the API, webhooks and AI assistants
  • How to build an app by describing it, or start from the catalog
  • What data your apps can use, and the tools they can connect to
  • Who can see your apps, including people outside your company
  • Permissions, limits and what's coming

How Studio fits with the API, webhooks and AI assistants

Many operators already build their own automations with the TripWorks API, webhooks and outside tools like Google Apps Script or Zapier. That works well, and it's not going away. Studio is a different route to the same goal: instead of hosting a dashboard on your own website or a script in another service, you describe the screen and it runs inside TripWorks.

  • Studio is best for screens your team looks at and works from every day: a dispatch board, a check-in manifest, a crew schedule, an owner report. It builds, hosts and keeps the app inside TripWorks for you.
  • The API and webhooks are best when another system needs to react to TripWorks automatically, such as sending a booking to your accounting software the moment it's made.
  • AI assistants (MCP) are best for one-off questions and quick changes, typed into Claude, ChatGPT or Gemini. See Connect TripWorks to your AI assistant.

You can use all of them together.

Where to find Studio

Once Studio is turned on for your company, open it from More in the top menu: under Studio, choose Library to see your apps, or Settings if you're an admin. People who can manage your company profile can also start a new app from Studio under AI & Assistance in the same menu. Studio has two views, switched with the toggle at the top of the page:

  • Catalog has ready-made apps from TripWorks that you can install and then make your own.
  • Apps is your company's library: everything your team has built or installed.
TripWorks Studio catalog page with the Catalog and Apps toggle and the Build your own button
The Studio catalog. Use Build your own to describe a new app.

Most of the catalog is a preview of what's coming. Apps marked Showcase can't be installed yet. Apps marked Available can be installed today. Turn on Available now only to see just those.

Build an app by describing it

  1. Open Studio and start a new app. Click Build your own on the catalog, or use the box at the top of the Apps page.
  2. Describe what you want in your own words. Be specific about what should appear, for which dates, and what should stand out. You can attach a screenshot, a sketch or a PDF (PNG, JPG or PDF up to 10 MB) to show what you mean. Or pick one of the starter ideas below the box and adjust it.
    TripWorks Studio Apps page with the describe box and starter ideas
    Describe an app in plain words, or start from an idea.
  3. Answer any questions. Studio may ask a few follow-up questions before it builds, such as which experiences to include. Answer them, or choose Skip, just build it.
  4. Review the preview. Studio shows a live preview using your real TripWorks data, usually within a minute or two.
  5. Ask for changes. Type what you'd like different, or click Edit, point at a part of the app and say what to change. Each change is saved as a new version. If a change doesn't work, you keep the last version that did.
  6. Share it when it's ready. Nothing reaches your team or your customers until you choose. See Who can see your apps.

The more detail you give up front, the closer the first version will be. Name the fields you care about, the rules ("flag any departure with no guide assigned"), and any exceptions. It's the same habit that makes any AI tool work well: sketch out the idea with real examples before you build.

What your apps can do

Use your live TripWorks data

Apps read your account as it is right now: trips and bookings, guests, experiences and timeslots, the manifest, resources, guides, waivers, reviews, reports and more. They can also make changes when you build them to, such as updating a guest's details, changing a booking status, adding a trip note or adjusting resource availability. Every change is checked by TripWorks first, so the app can show you what will change before it's applied.

An app always works with the permissions of the person using it. If someone can't see revenue in TripWorks, they won't see it in a Studio app either.

Connect the tools you already use

Under Studio settings, an admin can connect company services such as HubSpot, Google Sheets, Slack, QuickBooks, Notion and Airtable, so apps can read and update them. Personal accounts like a mailbox or calendar are connected by each person, for their own use.

Apps can also call other web services using Variables & Secrets, for things like a weather or tide feed. Secrets can be saved but never read back.

Run without any AI cost per view

Only building an app uses AI. Once an app is built, opening it and reading your data doesn't involve AI at all, so your team can use it all day.

Who can see your apps

Every app has its own Share settings:

  • Only you. Just you and your account admins.
  • Everyone at your company. Anyone at your company who has access to Studio.
  • Anyone with the link. For people outside your company, such as a boat owner, a partner or a caterer. You can send a snapshot link, a read-only copy of today's data that expires after 1, 7 or 30 days, or invite a guest, who signs in with a code sent to their email and sees live data, read-only, for up to 90 days. Every outside view is recorded, and you can extend or revoke a link at any time.

Outside sharing is only available for apps that just show information. Apps that change data, or that use saved notes, files or secrets, stay inside your company.

You can also pin an app to the top menu, or make one app your company's home page.

Limits to know about

  • Apps can't charge cards or issue refunds. Take card payments and refunds in TripWorks as usual.
  • Apps don't send messages from TripWorks. An app can read your message history, and it can send email through a mailbox you've connected, but it doesn't use TripWorks messaging.
  • Apps work online only. Studio needs an internet connection.
  • Descriptions can be up to 6,000 characters, and attachments up to 10 MB.
  • Removing an app is reversible for 30 days. Remove hides it from everyone, including menu pins and share links, and you can bring it back from Removed apps. Delete permanently can't be undone.

Example apps

  • Build a daily departure board that lists every departure with its guide, pickup location and add-ons, and flags any trip with no guide assigned.
  • Build a catering prep list for the next 48 hours, grouped by vendor, with each trip's pickup location and departure time.
  • Build a weather go/no-go board that checks wind and sea state for each departure against limits you set.
  • Build a waiver chaser that lists every unsigned waiver for today's departures.
  • Build an owner summary for a boat or vehicle you run for someone else, and share it with them as a read-only link.
  • Build a gear fitting planner that sizes wetsuits, helmets or harnesses from guest details before they arrive.

FAQ

How do I get access to Studio?

Studio is in early access and we're adding companies by request, in small groups. Contact TripWorks support or your account manager and ask to join. Once it's available for your company, an admin who can manage your company profile turns it on from the Studio banner at the top of Setup > Integrations.

Does Studio cost anything?

Studio is free during early access. Pricing will come later, and we'll give plenty of notice before anything changes. Admins can see how much your company is building under Studio settings, which shows an estimated cost for each build so you can follow usage. You aren't charged for it during early access.

Do I need to host anything or know how to code?

No. Studio builds, stores and runs your apps inside TripWorks. You describe what you want and ask for changes in plain words.

I've already built tools with the API and webhooks. Should I move them to Studio?

You don't have to. Tools you've built with the API, webhooks or scripts keep working. Studio is worth trying for screens your team looks at every day, because it removes the hosting and login work. Automations that run in the background, such as sending an email to a vendor at a set time, are still a good fit for webhooks and scripts.

Can my apps change data in TripWorks?

Yes, when you build them to. An app can update things like guest details, booking status, trip notes and resource availability, and it shows what it will change first. It always works within the permissions of the person using it. Apps can't charge cards or issue refunds.

Can I share an app with someone outside my company?

Yes, if the app only shows information. Send a snapshot link that expires after 1, 7 or 30 days, or invite a guest by email for live, read-only access for up to 90 days. An admin can turn outside sharing off for the whole company under Studio settings > Sharing.

Who can see an app I build?

Only you and your admins, until you change its Share setting. You choose for each app whether it stays private, goes to everyone at your company with Studio access, or can be shared outside.

What happens if a change breaks my app?

You keep the last version that worked. Each change is saved as a new version, so ask Studio to try again or describe the change differently.

Can I install an app from the catalog and change it?

Yes. Installing a catalog app gives you your own copy, which you can change like any app you built. When TripWorks improves the catalog version, you can choose Update to the latest version and review the result before it goes live.

Where do I send feedback or ideas?

Tell TripWorks support or your account manager what you're trying to build and where you got stuck. Early access feedback directly shapes what we build next.

Built for attractions, tours & activities

Build the screen your operation needs

See how operators describe a dashboard or manifest in plain words and have it running on their live TripWorks data in minutes. Book a demo.

Still stuck?

Tell us what you're trying to do and our support team will get back to you as soon as possible.