Taskade Genesis App URLs: Which Link to Share

Overview

Taskade links come in two families. The whole skill is to tell them apart. Public share links are the ones you send to a customer. Workspace links are the ones your browser shows while you build, and they need a Taskade account to open. If you copy the wrong one, your visitor lands on a sign-in screen instead of your app.

TL;DR: A published Taskade Genesis app lives on its own web address, either the one Taskade generates for you (something like your-app.taskade.app) or your custom domain. To share the app's public listing page use taskade.com/app/{name}-{id}, and for a kit use taskade.com/kit/{name}-{id}. The /spaces/{spaceId} link in your address bar is the builder, not the front door. See Publishing apps.

Tell the two families apart

Scan this box first. Everything above the line is safe to paste into an email. Everything below it opens the builder and asks for a login.

┌───────────────────────────────────────────────────────────────────────┐
│  PUBLIC: safe to share with anyone                                    │
├───────────────────────────────────────────────────────────────────────┤
│  Published app     your-app.taskade.app  (or your custom domain)      │
│                    share when…  people should USE the live app        │
│  App listing       taskade.com/app/{name}-{id}                        │
│                    share when…  people should SEE the app listing     │
│  Kit               taskade.com/kit/{name}-{id}                        │
│                    share when…  people should INSTALL a whole bundle  │
│  AI agent          taskade.com/a/{name}-{id}                          │
│                    share when…  people should CHAT with your agent    │
│  Public project    taskade.com/p/{name}-{id}                          │
│                    share when…  people should READ a project          │
│  Creator profile   taskade.com/@{handle}                              │
│                    share when…  people should FOLLOW you              │
├───────────────────────────────────────────────────────────────────────┤
│  WORKSPACE: needs a Taskade account                                   │
├───────────────────────────────────────────────────────────────────────┤
│  Workspace/app     taskade.com/spaces/{spaceId}                       │
│  Project           taskade.com/d/{projectId}                          │
│  Automation        taskade.com/flows/{flowId}                         │
└───────────────────────────────────────────────────────────────────────┘

Know what each public link does

Every public share link follows the same recipe: the kind of thing, a readable name, then its id. So taskade.com/app/client-portal-01JK82XFM2 is the app named Client Portal. The readable part is there for humans and for search results. The id at the end is what Taskade reads.

/app links work one more way. Cloning is the creator's choice, set with Share as kit in the Publish menu. A free or paid kit opens a listing page with the Clone button. A public app that is not a kit forwards to the running app.

Recognize the builder links

These three are the ones your address bar shows while you work. They are perfectly good for a teammate who is already in your workspace, and wrong for a customer.

The rule of thumb: /spaces, /d, and /flows are builder links. Everything in the public table is safe to send out.

When to share which

Pick by intent, not by what is open in your browser tab. Start at your goal and follow the arrow.

1. To let someone use your app, send the app's own web address. If you have a custom domain, send that instead. They land on the live app.
2. To let someone look at the app before they commit, send the /app link. It shows the listing page and a Clone button for a free or paid App Kit. Otherwise, the link forwards to the live app.
3. To hand over a whole working setup, send the /kit link. A kit install brings the projects, agents, and automations inside it into their own workspace. See Community Kits.
4. To let an outside system start your automation, use the webhook address from the automation itself. A webhook is a private web address that another system pings to start a run. It belongs to the automation, not to any of these links.

Keep old links working

You do not have to hunt down links you already sent. Taskade forwards the older shapes to the current ones automatically.

The readable name in a link is decoration. Drop it, keep the id, and the link still resolves. That is why an old bookmark or a link with a stale name keeps working after you rename something.

A custom domain gives the app a second front door on your own name. The address Taskade generated for it keeps working too.

Know which control is doing the work

The shape of a link and who can open it are separate things. Every link respects the access settings on the thing it points to.

• The role you give them gates workspace members, from Owner down to Viewer.
• You manage the people who sign in to a published app in App Users.
• You set password protection and sign-in requirements per app in Publishing apps.
• An app featured in the Community Gallery uses the same links as the private build.

Whether a leaked URL grants access depends on which control you set. A Private app, a password-protected app, or one that requires sign-in checks the visitor, so the link alone is not enough. A Secret app is different: it is shared by link and hidden from search, which means the link is the key. Treat a Secret URL like a password. Use password protection or sign-in for anything you do not want forwarded.

Related guides

• Publishing apps. Visibility, passwords, and the publish flow
• App SEO. Make the published address findable in search
• Custom Domains. Put the app on your own name
• Community Kits. What a kit contains and how installing works
• App Users. Manage who signs in to a published app
• Community Gallery. Publish so other makers can find your work
• App Gallery. Browse apps you can clone