Tines 3B connects to the tools your team already runs on, and to almost any other system you can reach on a network. Whether you're calling an API, querying a database, talking to an MCP server, or serving a webpage, this article explains the main ways Tines 3B talks to the outside world and points you to the detailed setup steps for each.
Connectors: your apps and their APIs
A connector is how Tines 3B reaches a tool you already use. It's a reusable, saved connection to a single app, such as Slack, GitHub, Jira, or Salesforce, that bundles the service address and the credentials needed to authenticate.
The important part is that your code never touches those secrets. In a step or a chat, you make a plain, unauthenticated request, and Tines 3B injects the right credentials as the request leaves. That keeps keys out of your workflows while still letting them call the services they need.
Tines 3B ships with a large library of connector types across categories like communication, development, security, and CRM. For anything that isn't in the library, a custom API key connector can front almost any HTTP API.
To learn how to set a connector up, read here.
MCP servers: connect in both directions
Tines 3B speaks the Model Context Protocol (MCP), and it works two ways:
Tines 3B as an MCP server. You can connect an external AI client, such as Claude, to Tines 3B over Streamable HTTP so it can use your workflows and data.
Read here to learn how to connect an AI client to Tines 3B with MCP.
A workflow calling out to a remote MCP server. Using the "MCP server" connector type, a workflow can list and invoke tools, prompts, and resources on an external MCP server.
Read here to learn how to connect a workflow to a remote MCP server.
Keep the two directions distinct when you plan a build: one lets a client reach into Tines 3B, the other lets your workflow reach out.
Databases and other networked services
Beyond named apps, Tines 3B connects directly to databases like Postgres and MySQL (look under the Data category in the connector library). Once saved, a database connection is available to your workflows through a connection string, so you can query it from your automations without wiring up credentials by hand.
The same connector model extends to other networked services you might run on, including email servers and other generic endpoints, so a connector can front a custom system just as well as a named product. The exact set available depends on your build, so check the library for what's listed.
Webpages: a human-facing front door
Webpages are a little different from everything above. Instead of Tines 3B reaching out to a system, a webpage is an inbound, human-facing route that serves HTML you can open in a browser. It's how people interact with your workflows, rather than how your workflows talk to another system. You control who can reach it with the route_auth setting, from space members only through to public.
Read here for the full details on webpages.
