A notification state that appears when Tines 3B requires user input or action to continue. It signals that the AI has reached a point where it cannot proceed automatically and needs clarification, approval, or additional information from the user.

An interactive visual graph that shows the entire access control structure of a Tines 3B tenant. It shows who (members and groups) has access to what (connectors, skills, and spaces) and through which paths (direct grants, group memberships, or inherited permissions).

It is a workflow that has been published and has been executed at least once in the last 30 days.

The permission and functionality that allows users to create new connector configurations for authenticating with external services and APIs. This ability is controlled by the tenant:connected_app_create permission and determines who can register new connectors for use across workflows.

An inline action that appears when Tines 3B needs to access an external service or API during a conversation. It allows you to create or select a connector configuration on-the-fly without leaving the chat interface, enabling the AI to continue building with proper authentication.

We use a "Bring-Your-Own-Model" (BYOM) approach. You leverage your existing LLM investments for token consumption, allowing you to focus on the value of your workflows.

Comprehensive records of all user and system actions in Tines 3B. They capture who did what, when, with what parameters, and whether the action succeeded or failed. Every mutation, API call, authentication event, and provisioning action is automatically logged for security, compliance, and forensic purposes.

A feature that automatically attempts to repair workflow errors by analyzing failed executions, identifying the root cause, and applying fixes to the code or configuration. When a workflow step fails, autofix can diagnose the issue and make corrections without manual intervention.

An automated workflow improvement system where Tines 3B (the AI agent) continuously monitors live workflows and proactively creates improvement branches when it identifies opportunities to enhance reliability, capability, clarity, or performance.

Are isolated, forkable versions of a workflow that allow users to edit, test, and collaborate on changes before pushing them live to production.

Provides a browsable directory of 900+ pre-built connector templates (also called "connected apps") that enable workflows to authenticate and integrate with external services and APIs.

Provides a UI for exploring and managing files stored in workflow execution volumes. It's accessible through dropdown menus on spaces, workflows, personal items, and chats.

Native OS-level alerts that inform users when Tines 3B finishes working or needs input while the Tines 3B browser tab is in the background.

Is one of the main tabs in the workflow overview panel that provides an interactive preview and inspection interface for workflows that expose webpages or HTTP routes.

A gamified metric displayed in the space leaderboard that ranks team members based on their contribution and activity level within a space. It combines multiple weighted metrics to create a single numerical score.

A dedicated personal workspace for having standalone conversations with Tines 3B outside the context of workflows. It's accessible via the "Chat" item in the navigation sidebar.

A commit is a saved version of a workflow: a snapshot of everything in it at one moment, captured so you can look back at it, return to it, or build on it. Commits are how Tines 3B keeps a history of your work, so editing a workflow never means losing what came before. This article explains what a commit is and how commits fit together into a workflow's history.

The processing power used to run workloads, such as executing code, workflows, agents, or AI-related tasks.

A role that grants the ability to manage access for a specific connector

A role that allows using the connector's credentials in workflows and AI agents.

A role that grants read-only access to see connector details without ability to use or modify it.

Reusable authentication and configuration bundles that allow workflows and AI agents to integrate with external services and APIs. They encapsulate credentials, OAuth tokens, API keys, and connection details so they can be securely shared across multiple workflows.

All user code runs inside a gVisor sandbox. This is not just a container, but an isolated application kernel that intercepts every system call before it can reach the host. Each execution gets its own network, filesystem, and process space, completely walled off from the host, other tenants, and internal services. The worker spins up a fresh, short-lived sandbox for every execution with strict timeouts, read-only file access, and all outbound traffic routed through a security proxy that blocks access to internal infrastructure.

An action that copies the Git repository URL for a workflow, so you can clone or pull its step code into your local environment or external tooling.

When a workflow needs to call an external API with credentials, the secrets are never exposed to the user's code. Instead, a local security proxy injects credentials into matching outbound HTTP requests on the fly and deletes them from memory immediately after execution. Secrets are encrypted at rest with HPKE (asymmetric, browser-side encryption) and AES-256-GCM, and are only ever decrypted momentarily at the point of injection.

Credentials are the secrets that let your workflows talk to other tools. An API key, an OAuth token, a username and password, a client secret: whenever a workflow needs to prove who it is to an outside service, it uses a credential you've stored in Tines 3B.

Cron is a time-based scheduler for automatically triggering workflow steps at specified intervals or times. Steps with a cron field in their config file execute automatically on a recurring schedule using standard cron expression syntax.

Tenant-created, user-defined bundles of permissions that extend the built-in RBAC system. Unlike built-in roles, custom roles allow administrators to define granular permission sets tailored to their organization's needs for specific scope kinds (spaces, connectors, skills, networks, etc.).

A user preference setting that determines which page or space is shown when you first open the Tines 3B app or navigate to the root URL (/). It allows users to customize their landing page instead of always starting at the default "Recents" view.

A user preference that determines which space newly created workflows will be added to when created from the Recents view. It allows you to set your preferred destination space so you don't have to manually select it each time.

A user preference that allows you to customize the order in which tabs appear at the top of every workflow. These tabs provide different views and tools for working with workflows.

A piece of outside code your workflow relies on: a package from npm, a library from Python's ecosystem, or a base image a step builds from.

Spaces that anyone in the tenant can find and join themselves without needing an explicit invitation or grant from a space manager. When a space is marked as discoverable, it appears in the navigation sidebar for all tenant members with a special "discoverable space" icon, allowing them to self-join with a predefined role.

A menu option in the workflow's branch selector that allows you to export the entire conversation history (all chat messages, tool calls, and outputs) from the current branch as a JSON file.

A menu option in the workflow's branch selector that allows you to export the entire workflow source code as a .zip file containing all workflow files, step code, Dockerfiles, dependencies, and configuration.

The smallest unit of work in Tines 3B: one run of a single step's code. Every time a step does something, whether as part of a workflow, a scheduled job, or a quick test, that's an execution.

A feature that allows users to bookmark specific workflows or links for quick access. Favorited workflows appear in a dedicated "Favorites" view accessible from the left navigation panel.

"Follow 3B" is a feature that navigates your workflow view to follow Tines 3B as it works, jumping to whichever step and file the agent is currently editing. When active, the workflow view tracks the agent's actions in real-time, keeping you synchronized with what Tines 3B is building. It can be toggled on or off by default in the user preferences.

A menu option in the workflow's branch selector that creates a new branch from the current commit, allowing you to make experimental changes or work on variations without affecting the main workflow.

The single thing that decides who can do what in Tines 3B. Everything about access, every space you can open, every connector you can use, every member of a group, comes down to grants.

A role that allows users to create new user groups at the tenant level

A role that grants full administrative access to a specific group (can add/remove members, edit group details, manage access)

Basic membership in the group (can see group details but cannot modify).

Are collections of users within a tenant that allow bulk permission management. Instead of granting permissions to individual users one-by-one, you can grant permissions to a group and all members automatically inherit those permissions. Groups simplify access control, reflect organizational structure, and make it easy to onboard/offboard users.

A toggle option in the workflow builder that controls whether step code (scripts, Dockerfiles, configuration files) is visible in the step panels. When hidden, step panels show only high-level information; when shown, the full source code is displayed inline for quick reference and editing.

The connections between workflow steps that define the data flow and execution order. Links determine which steps receive output from other steps, creating a directed graph that represents how data moves through a workflow. They are the fundamental mechanism for composing multi-step workflows.

A tab that provides a visual graph representation of all steps and their connections. It displays the workflow as a node-and-edge diagram, showing data flow, execution dependencies, and the overall workflow architecture at a glance.

Any agent, app, or automation that is “pushed to live” in a Tines 3B space. Live workflows only matter in our Explore plan where they count towards your license.

Users or machines that have been granted access to a specific resource (space, connector, skill, network, or user group). Membership is established through role grants that give the member specific permissions on that resource. The concept of "members" represents who has access to what, and with which permissions.

A leaderboard metric that counts the total number of chat messages (prompts and responses) a user has exchanged with Tines 3B across all their workflow building sessions in that space. It measures engagement and interaction with the AI assistant.

A workflow health monitoring tab that provides real-time visibility into workflow execution status, error rates, performance metrics, and recent activity. It helps you track workflow reliability, identify issues, and understand execution patterns over time.

Visual annotations you can place on the workflow canvas to document your work, leave reminders, explain complex logic, add TODO items, or communicate with team members. They're like digital Post-it notes that live alongside your workflow steps.

When the account consumes more Tines units than allotted per month. Tines units incurred over plan allowance are charged at an overage rate per month. All new customers get a one month grace period before overages take effect.

A private workspace automatically created for each user when their account is created. It's a space that only the user can access (plus tenant admins), providing an environment for experimentation, learning, and personal workflows.

A toggle feature in the chat interface that changes how Tines 3B responds to your requests. When enabled, Tines 3B drafts a plan and presents it for your approval *before* taking any actions or making changes.

The "who" in Tines 3B's access control: the identity that holds access and acts on it. Whenever Tines 3B decides whether something is allowed, it's asking about a principal.

The action of deploying a workflow from a draft branch to the main branch, making it the active, production version that executes for real traffic (webhooks, cron schedules, etc.). It's the final step that takes your changes from development/testing and makes them live.

Your follow-up messages wait in line and send automatically once the agent finishes what it's doing.

The comprehensive permission system in Tines 3B that governs who can do what with which resources. It uses roles (bundles of permissions) granted to users, groups, and service accounts on specific resources (spaces, connectors, skills, networks, etc.) to control access and actions throughout the system.

A special markdown documentation file that lives at the root of a workflow, providing human-readable documentation about what the workflow does, how to use it, configuration requirements, and other important information. It appears as a dedicated tab in the workflow builder where you can write and view formatted documentation.

Predefined bundles of permissions that determine what actions a user, group, or machine can perform on specific resources. Roles are the central building block of Tines 3B's RBAC (Role-Based Access Control) system, grouping related permissions together for easier access management.

An HTTP-triggered entry point that makes a workflow step publicly or privately accessible at a specific URL path. Routes allow workflows to respond to web requests (browser navigation, API calls, webhooks) by mapping URL paths to workflow steps.

A logical group of step executions that tracks the progress of a workflow from a starting point through all linked downstream steps. It represents a single traversal through the workflow's dependency graph.

A dedicated view in the workflow builder that displays the complete execution history for a workflow. It shows all past and current runs (executions) of workflow steps, allowing you to view details, monitor status, debug failures, and rerun executions. It's the primary interface for observing workflow execution history and troubleshooting issues.

The target of a permission grant, the resource being protected. Every grant links three things together: a principal (a user or group), a role (a bundle of permissions), and a scope (the resource).

Is a non-human identity used for automation. It represents scripts, CI jobs, services, or other programmatic workloads that need to interact with the system. It is distinct from human users.

A role that allows a user to create new skills within the tenant.

Markdown-formatted text that Tines 3B loads into its context when it actively uses a skill. They provide detailed guidance on how to perform a specific task or handle a particular domain.

A role that grants full management access to a skill. They can read and modify the skill, including managing grants/access for others.

A role that grants read-only access to use a skill without the ability to modify it.

Custom, on-demand reference materials (instructions) that Tines 3B can load into its context when it needs specialized guidance for specific tasks or domains.

An isolated execution of a single workflow step that doesn't trigger downstream steps or persist as a permanent workflow run.

The primary organizational container for workflows in Tines 3B. It serves as a collaborative boundary where groups of users organize and control access to their automation work.

A role that allows a user to create new spaces within the tenant.

A role that grants full working access to a space. Access includes reading all workflows and content, creating and editing workflows, running code and executions and pushing changes to the live branch.

A gamified ranking system that tracks and displays member contributions within a space. It calculates a "Builder Score" for each user based on various development activities.

A role that grants full administrative access to a space. Access includes reading all workflows and content, managing the space itself (settings, deletion, etc.), managing access grants (adding/removing members and their roles) and all the capabilities of editors and viewers.

A role that grants read-only access to a space, viewing its workflows and their content.

An enterprise authentication method that allows users to sign in to Tines 3B using their organization's identity provider (IdP) instead of managing separate credentials. SSO is configured at the tenant level and supports both SAML and OIDC protocols.

The primary data flow mechanism in Tines 3B workflows. It's the input stream that each step reads to receive data from upstream steps or external triggers.

The primary data output stream from a workflow step. It's what a step writes to pass data to downstream steps or return results from the workflow.

Your message goes to the agent mid-turn, redirecting it while it's still working. Use this when you want to correct course or add context that should change what Tines 3B is doing right now

A step is the fundamental unit of execution in a Tines 3B workflow. Each step is represented as a directory in the workflow repository, and the directory name is the step's name.

The data that a workflow step produces when it executes. It's written to stdout (standard output) and can serve two purposes: (1) passing data to downstream steps via links, and (2) becoming the HTTP response body. Output is typically JSON but can be any text format.

Storage is where a Tines 3B workflow keeps files that outlive a single step. It's provided by named volumes.

The top-level organizational entity in Tines 3B. Each Tines 3B stack (deployment) has exactly one tenant, which represents the entire organization using that instance.

User role that grants the ability to create new connectors (connected apps) in the tenant.

User role that grants the ability to share connectors you create at the tenant level.

User role that grants the ability to create new user groups in the tenant.

A single, safe/secure environment for every team’s important agents, apps, and automation.

A command-line tool for interacting with Tines 3B workflows It enables you to work within your tool of choice (e.g. Claude Code, Codex, etc.).

Our runtime metric. They are a combination of compute, storage, and transfer costs. Each paid plan includes a monthly allowance of Tines units. The allowance resets every month on the first and does not roll over.

Data that leaves a system, cloud environment, or network and is transferred somewhere else.

Sets a workflow in motion. A workflow doesn't run on its own; something has to start it, and that something is a trigger. It might be a clock reaching a scheduled time, a request arriving at a URL, or an email landing in an inbox.

How Tines 3B reaches systems inside your private network, the databases, internal APIs, and services that live behind your firewall and were never meant to be exposed to the internet. It's a specific kind of network, built around a piece you run in your own environment.

Output from a preceding step that flows into the current step.

A speech-to-text chat input feature that allows users to dictate messages to Tines 3B using their microphone instead of typing.

A named, persistent storage directory that workflows can mount and use to share data across step executions and persist state between runs.

A webpage is an HTTP route step that serves HTML content to be viewed in a browser. Webpage routes appear on the Links page and are rendered as a thumbnail, marking the entry point a user should open first.

It is an automation, a collection of interconnected steps that process data and perform tasks in your proprietary systems.

It is a commit, a snapshot of a workflow's complete state at a specific point in time.

Allow you to expose any workflow as a reusable API that other workflows in your tenant can call. This turns your workflow into a connector that can be invoked like any other service.