Tealfabric

Solution delivery flow

Build → deploy → CDN → APIs → operate

01 Build02 Deploy03 CDN04 APIs05 Ops

Local dev · partner-portal-next/

AI-assisted build

Cursor + Claude scaffold Next.js app

Lovable prototype → export to repo

app/page.tsx · intake form component

lib/tealfabric-client.ts · OpenAPI types

POST /api/v1/webapps/... (server route only)

Simulated flow — AI-assisted Next.js app published to the platform; users on CDN WebApp; logic through controlled APIs

Build on Tealfabric

“Your language, our contract—build on workflows, WebApps, and connections without rebuilding the platform underneath.”

Platform

Developer platform and APIs — your solution workplace

Build customer solutions on one platform—REST APIs, OpenAPI, scoped keys, and developer tools so partners ship workflows, WebApps, and connections with the same history as the product UI.

Adoption context

You need this when
Builders ship solutions against real platform APIs—OpenAPI, scoped keys, developer tools—not informal knowledge and mocks.
Often bundled with
Governance for live workflows on one platform.
Not required if
Your team configures workflows in the UI only and does not extend via API or agent tooling yet.

Related workflow: Platform overview · Adoption path

Your team extends Tealfabric into customer solutions—using automation, data, connections, and apps the platform already provides.

Teams that adopt a platform still often build parallel stacks: custom API gateways, separate portal hosting, glue scripts that bypass safety rules, and AI experiments disconnected from real connections and data.

Tealfabric is designed so your solutions stay inside the platform boundary. Use HTTP APIs, the API explorer, and scoped API keys—the same surfaces the product UI uses—to wire portals, backends, CI pipelines, and AI-assisted tooling into controlled capabilities.

  • Build customer solutions on the platform—not beside it or inside its core codebase
  • HTTP and JSON from any stack; OpenAPI at /api/docs for contract-first development
  • Scoped API keys per solution and environment—server-side only
  • AI-assisted workflows with Cursor, Claude, and Lovable—ship via developer tools and WebApps API
  • Publish WebApps, CDN assets, public docs, and team skills with deliberate release steps
  • Workflow API plus built-in API helper inside step code
  • Trace AI, team playbooks, and platform tools within deployment safety rules
  • Operations logs for everything your team deploys to the account

Solution patterns

Typical ways customer teams deliver on the platform.

  1. cron → execute
    process API

    01. Nightly sync you own

    Your scheduler starts a workflow → connections run → Datapool updated → alerts on failure.

  2. CI publish
    custom domain

    02. Partner portal

    WebApp content in CI → publish on Tealfabric → your domain → workflow validates and writes to Datapool.

  3. api client
    in step code

    03. In-workflow enrichment

    TypeScript step calls connections and Datapools via the built-in API client—no middleware server.

  4. SKILLS/
    Trace AI

    04. Support AI with your playbook

    Deploy skills playbooks → Trace AI follows your rules → only platform-allowed tools run.

  5. Swagger
    scoped key

    05. Contract-first partner API

    Validate in the API explorer → implement in your service → scoped staging key → promote after CI checks.

End-to-end flow

Build with AI tools, publish to the platform, serve on CDN—logic through APIs.

A developer scaffolds a Next.js partner portal with Cursor and Claude, exports a Lovable prototype into the repo, and deploys through developer tools and the WebApps API. End users load the app on your domain with CDN assets; form submissions hit server-side routes that call workflows and connections—never exposing API keys in the browser.

Solution delivery flow

Build → deploy → CDN → APIs → operate

01 Build02 Deploy03 CDN04 APIs05 Ops

Local dev · partner-portal-next/

AI-assisted build

Cursor + Claude scaffold Next.js app

Lovable prototype → export to repo

app/page.tsx · intake form component

lib/tealfabric-client.ts · OpenAPI types

POST /api/v1/webapps/... (server route only)

Simulated flow — AI-assisted Next.js app published to the platform; users on CDN WebApp; logic through controlled APIs

Capabilities

One account, your solutions—automate inside and outside the platform.

No required vendor SDK—your HTTP clients are fine. Use OpenAPI for codegen if you want contract-first development.

  1. compose
    don’t fork core

    01. Extend, don't rebuild

    Build on ProcessFlow, WebApps, Datapools, and connections—not the platform core.

    Your team delivers customer solutions on top of Tealfabric: same account, same history, same connections and workflows—exposed through documented APIs and clear publish steps.

  2. /api/v1/*
    HTTP + JSON

    02. REST API — your main surface

    /api/v1/ for workflows, connections, Datapools, WebApps, documents, and logs.

    Run workflows and check queue status, execute connections, manage records and documents, create and publish WebApps, and read operational analytics—with consistent success and data response shapes.

  3. /api/docs
    Swagger

    03. OpenAPI API explorer

    Discover contracts at /api/docs before you implement in your repo.

    Inspect payloads, test calls with your API key, and target the documented contract—not reverse-engineering the UI. Contract-first partner integrations start in the explorer.

  4. X-API-Key
    scoped · rotate

    04. Scoped API keys

    Per-solution identity with scopes, expiry, rotation, and rate limits.

    API keys on server-side requests—for workflow runs, connection runs, record reads, and more. One key per solution or environment; rotate without breaking unrelated workloads. Keys stay in servers and CI, never in browser JavaScript.

  5. Cursor · Claude
    Lovable · MCP

    05. AI-assisted solution development

    Build faster with Cursor, Claude, Lovable—and ship on platform APIs.

    Use modern AI coding tools to scaffold Next.js portals, generate API clients from OpenAPI, and iterate WebApp content—then publish to your account via developer tools and the WebApps API. Trace AI, team playbooks, and platform tools connect AI to real connections and data.

  6. execute-process
    api in steps

    06. Workflow API and built-in client

    Run, queue, and chain platform capabilities from outside and inside steps.

    External schedulers call the workflow API; step code uses the built-in API client with account and execution context applied automatically—no hand-maintained auth headers in every step.

  7. WebApp vN
    CDN · SKILLS/

    07. Publication models that match reality

    WebApp versions, CDN assets, public docs, skills—each with its own go-live path.

    CI pushes WebApp content → publish version N → smoke test live URL. CDN for static assets; public docs for controlled downloads; skills folders for AI playbooks without redeploying the platform.

  8. alerts
    queue · logs

    08. Operate what you ship

    Alerts, queues, logs, and analytics for your account's workloads.

    When your nightly sync or partner portal fails, trace WebApp execution logs, linked workflow runs, and connection queue status in the same console—no separate monitoring stack required.

Languages and AI tooling

TypeScript / JavaScript

Node services, Next.js portals, workflow step code, serverless, CI pipelines

Python, Go, Java

ETL, microservices, partner gateways

Cursor, Claude, Lovable

AI-assisted scaffolding—publish via API and developer tools

Shell / curl

CI smoke tests and scheduled triggers

Platform capabilities you compose

ProcessFlow

Business rules, orchestration, file handling, OCR, AI steps

Integrations

CRM, ERP, email, files, HTTP, databases

Datapools

Structured storage and queries for workflows and apps

WebApps

User-facing UI bound to your workflows

Documents and CDN

Files, reviews, public static delivery

Operations

Queues, logs, and failures for what you deployed

Trace AI

Controlled AI with team playbooks and platform tools

Fits the platform

External callers hit WebApp URLs, webhooks, and CDN links. Your backends orchestrate what happens behind them with /api/v1/. Workflow steps chain capabilities with the built-in API client. AI uses Trace AI, team playbooks, and platform tools within safety rules.

WebApps Process Automation AI and agents Platform Ops and Observability

Deliver real solutions on a controlled platform

See APIs, developer tools, WebApp publish, and AI-assisted development on your account.

We walk through OpenAPI discovery, scoped keys, CI publish pipelines, AI-assisted workflows, and operations logs for what your team ships.

Book a demoDocumentationFor developers