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?"
You'll find a workflow's links on its Links tab, laid out as a gallery. Webpage links show a preview of the page, so the gallery doubles as a quick visual index of everything the workflow exposes.
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.
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.