Tealfabric documentation
Document information
| Field | Value |
|---|---|
| Canonical URL | /docs/00_introduction |
| Version (published date) | 2026-05-05 |
| Tags | library, index, navigation |
Summary
This documentation is the central entry point for Tealfabric users and developers. It is organized around practical goals such as learning the platform, building automations, connecting external systems, and integrating through APIs. By following this structure, you can move from orientation to implementation with less searching and more confidence.
What is Tealfabric?
Tealfabric is a platform for designing and running business automation workflows, data pipelines, integrations, and AI-assisted processes in one environment. Teams use it to connect services, transform and route data, orchestrate business logic, and expose outcomes through webapps, APIs, and event-driven execution. This documentation translates those capabilities into concrete guidance so you can apply them safely and effectively in production.
Foreword
Everyone is committed to their own journey and the missions they are pursuing. We want to support you on that journey by providing reliable tools and a robust runtime environment to develop, manage, and secure business data and processes. If you notice that something in this library is missing or incorrect, please reach out to us so we can resolve it promptly.
How to start by goal
If you are new to Tealfabric, begin with the User guide for the live product and core terminology, then use Navigating the Tealfabric Library when you need a documentation map, before configuring features in depth. If your immediate goal is automation development, continue with the ProcessFlow and writing-step-code pillars where execution patterns, sandbox behavior, and implementation recipes are grouped for practical daily use. If your focus is technical integration, start with the API and connecting-systems pillars so authentication, endpoint usage, and connector behavior are aligned from the first implementation step.
How to use this structure
Each numbered folder in this tree represents one documentation pillar. Most pillars include a 00_introduction.md page that defines scope and recommended next reads; Introduction and concepts uses the User guide and Navigating the Tealfabric Library pages for the same role. The published Library at /docs/... is generated from public/docs/main, which is the canonical source for end-user navigation and stable cross-linking in articles. Reading the pillar overview first and then moving to focused guides will usually give you the fastest path to correct implementation.
Sections (overview)
| Folder | Focus |
|---|---|
| Introduction and Concepts | User guide (UI and terms), Navigating the library (doc index) |
| Automations and ProcessFlow | Flows, steps, triggers, sandbox, async, keystore |
| Writing Step Code | Snippets, patterns, data/email/HTTP/DB/LLM in steps |
| Connecting Systems | OAuth2, integrations; connector catalog lives in connectors/ (300+ pages) |
| Apps, Webhooks, and Surfaces | Webapps, callbacks, uploads, library |
| Data and Documents | Datapool, documents, CDN-related content |
| AI Agents and MCP | Agents, MCP, guardrails |
| API for Developers | REST/OpenAPI, API keys, programmatic access |
| Security, Privacy, and Compliance | Keys, sandbox limits, checklists |
| Releases and Changes | Release notes and change-focused docs |
Popular starting points
Most users benefit from starting with a compact set of high-impact pages that reduce onboarding time and common implementation mistakes. For platform orientation, begin with the User guide and Navigating the Tealfabric Library, and for automation development continue with Writing step code and the Process sandbox tf API reference. For secure ProcessFlow implementation, review Sandbox guardrails and ProcessFlow Keystore, and for external integrations use OpenAPI / Swagger as the primary reference.
Staying current
Tealfabric evolves continuously, so production teams should review release-focused documentation regularly to track behavior changes and newly published guidance. The releases and changes pillar is the authoritative source for update history, migration context, and version-aware planning. Keeping implementation practices aligned with those updates is one of the most effective ways to preserve long-term reliability.