I keep rebuilding the same little bit of logic in different workflows and it feels like there should be a better way. How do I reuse logic across multiple workflows in 3B? I’m curious how shared pieces are structured and how one workflow hands work off to another. A pointer to the recommended pattern would be great.
Hi there,
The recommended pattern in Tines 3B is to build the shared logic once as its own workflow, expose it as a connector, and have your other workflows call it. That gives you one place to maintain the logic and a clear contract for every caller.
- Put the shared logic in its own workflow, with a step that has a route on it — that route is the entry point other workflows will call. See: Route | Tines 3B Docs
- Open that workflow and click use this workflow as a connector in the workflow header. 3B creates a workflow-backed connector and opens the connector settings.
- In the connector settings, open the exposed links section and click Ask 3B to set up links. This marks the link as an API endpoint, secures it so it’s reached through the connector, and writes a description of the expected request and response so callers know what to send and what comes back.
- Use the copy button on the exposed link to grab the URL, then call it from your other workflows the same way you’d use any other connector.
- Push the shared workflow live to the main branch. If a route returns 404, that’s usually the cause, along with a mismatched HTTP method.
Full steps: Use a workflow as a connector | Tines 3B Docs
Two things worth knowing alongside this. The connector button only appears if you have permission to create connectors and to edit the workflow’s space — if it’s missing, ask an admin. And if what you’re repeating is instructions for 3B rather than runtime logic, a skill is the better fit: a reusable packet of instructions and files 3B pulls in when a task matches ( Use skills to give Tines 3B new expertise | Tines 3B Docs ).