Developers
API-first: build on ProcessFlow, WebApps, connections, and team playbooks on one account—inside the platform boundary, not beside it.
Solution delivery flow
Build → deploy → CDN → APIs → operate
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)
Build → deploy → CDN → APIs → operate — see developer platform for all eight API surfaces.
Start here
Sign in, provision a sandbox, discover contracts before you write code.
Automate workflows, call connections, publish WebApps, and extend AI with team playbooks—all on one account with reviewable history. Target the documented contract at /api/docs, not reverse-engineering the UI.
API
/api/v1/ for workflows, connections, Datapools, WebApps, and logs—API key server-side only.
External schedulers start workflows; step code uses the built-in API client. Keys stay in servers and CI, never in browser JavaScript.
curl -X POST https://acme-ops.tealfabric.io/api/v1/processes/vendor_intake/execute \
-H "X-API-Key: $TF_API_KEY" \
-H "Content-Type: application/json" \
-d '{"vendor_name":"Acme Parts","tax_id":"FI-12345"}'Ship
AI-assisted portals, WebApp versions, CDN, skills folders—each with its own go-live path.
Scaffold with Cursor or Claude, publish via developer tools and the WebApps API. When nightly sync or partner portals fail, trace execution in the operations console—no separate monitoring stack for typical workloads.
Processflow skeletonCursor toolsClaude toolsLovable toolsWebApps →Operations →
AI
Team playbooks loaded on demand—with tool safety rules and human approval.
Author skills folders for when to load context, which connections may run, and what needs human input before a connection executes.
Pilot
One production workflow, one playbook pack, safety rules—not login alone.
Sandbox account, top connections, ProcessFlow template, skills playbooks, tool safety config, scoped API keys, operations alerts.
Essentials
Nightly sync you own
Your scheduler starts a workflow → connections run → Datapool updated → alerts on failure.
Partner portal
WebApp content in CI → publish on Tealfabric → your domain → workflow validates and writes to Datapool.
In-workflow enrichment
TypeScript step calls connections and Datapools via the built-in API client—no middleware server.
Support AI with your playbook
Deploy skills playbooks → Trace AI follows your rules → only platform-allowed tools run.
Contract-first partner API
Validate in the API explorer → implement in your service → scoped staging key → promote after CI checks.
Platform capabilities you build on
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
AI coding tool plugins
Full capability breakdown on Developer platform and APIs →
Ship on Tealfabric
Provision a sandbox, wire your top connections, and ship one production workflow with scoped API keys—then add team playbooks when AI joins the loop.
