Skip to main content

Links

A link is a way into your workflow.

Written by Jamie Gaynor

When a workflow serves a webpage, exposes an API, or listens for events from another service, each of those is reachable at a URL, and Tines 3B gathers those URLs together as the workflow's links. They're the front doors: the addresses people and systems use to reach what you've built.

A workflow's front doors

Most of a workflow is internal machinery, the steps that do the work. Links are the parts meant to be reached from outside. A form someone fills in, an endpoint another system calls, a webhook a service posts events to: each is a link.

Collecting them in one place answers a practical question at a glance, which is "how do you actually reach this workflow?"

Links are laid out as a gallery. Webpage links show a preview of the page, so the gallery doubles as a quick visual index of everything that's exposed.

Four kinds of link

Tines 3B sorts links into a few categories so it's clear what each one is for:

  • Webpage. HTML pages and forms that a person opens directly in a browser.

  • API. Endpoints called programmatically, usually returning JSON.

  • Webhook. Endpoints that receive events from external services like Slack, Stripe, or GitHub.

  • Other. Everything else, such as file downloads, redirects, and OAuth callbacks.

You can filter the gallery by these types, which makes it easy to answer "what pages does this workflow serve?" or "which endpoints can other systems call?" without hunting through the steps.

See every link in one place

For a view that spans your whole account, open the Links page.

It gathers every link you can reach across all the spaces you have access to into a single gallery, so you don't need to open each space to see what's exposed. Each card shows which space the link belongs to.

By default, the page shows links from the spaces you've joined. The page opens showing webpage links. To change what you see, use the controls at the top:

  • Types. Switch between Webpage, API, Webhook, and Other. Click the option that's already selected to show every type at once.

  • Space, connector, and creator filters. Narrow the gallery to particular spaces, workflows that use a given connector, or links created by a specific person.

  • Search. Find a link by its workflow name or its route.

  • Sort. Order the gallery by recently updated or by name.

You can also favorite an individual link using the heart on its card, which keeps the links you reach for most within easy reach.

Show links from spaces you haven't joined

Some links are meant for everyone in your account, even people who don't work in the space that hosts them: a status page, a shared intake form, an endpoint other teams call. To bring those into the gallery, turn on the Other spaces toggle at the top of the page.

With it on, the gallery adds links from spaces you haven't joined, in two forms:

  • Links your role lets you view. If your role already grants you read access to a space you're not a member of, its links appear as normal cards, without the space name.

  • Links shared with everyone in your account. Links that any signed-in member of your account is allowed to open show up even when you can't otherwise read their space. These are links set to open for your whole tenant, for anyone publicly, or for any signed-in user without a group restriction.

Turning the toggle on also adds a "Spaces you're not in" option to the space filter, so you can focus on just these out-of-space links.

For a link from a space you can't otherwise read, the card shows only the link itself: its title, route, type, and URL. The workflow, space, and creator behind it stay private, so the gallery never reveals more than the link's author chose to expose.

A space's own links tab

Each space has its own Links tab, next to its Workflows list, showing just the links for that space's workflows.

Your personal workflows have the same tab. These scoped tabs are handy when you're working inside one space and want its entry points without the rest of your account's links mixed in.

Where links come from

A link is a step that's been given a route, an HTTP path, and marked with the kind of link it is. Marking the type is what puts it on the links tab and tells the gallery how to present it. That marking is deliberate: it's how you say "this route is a front door people should know about," as opposed to an internal helper.

Because links are branch-aware, the gallery reflects the version of the workflow you're looking at, so you can see the entry points a draft would expose before you make it live.

Not everything is a link

A workflow can have routes that aren't links. Internal callbacks and helper endpoints keep working without appearing on the links tab, because they're plumbing rather than front doors. The tab stays focused on the entry points that matter to the people and systems using the workflow, so it reads as a clean list of ways in rather than an exhaustive dump of every route.

The result is that the Links tab tells you, and anyone you share the workflow with, exactly how to reach it: which pages to open, which endpoints to call, and which URLs to hand to the services that need them.

Did this answer your question?