External systems call Tealfabric
Use this section when something outside the workspace opens the connection: your own service, a vendor webhook, a browser, or an external agent. API reference, WebApps, and the MCP server stay in their own sections. This page is the map.
Document information
| Field | Value |
|---|---|
| Canonical URL | /docs/03b_external-systems-call-tealfabric/00_introduction |
| Version (published date) | 2026-11-13 |
| Tags | api, webapps, mcp, inbound |
Choose the entry point
| You need | Start here |
|---|---|
| Your service calls workspace data or runs a process over HTTP | API for developers, then API key management and the endpoint index |
| People use a page, form, or file you publish | Apps, webhooks, and surfaces and the WebApps user guide |
| End users sign in to that WebApp | WebApps authentication |
| The WebApp is served on your domain | WebApp custom domain |
| Cursor, Claude, Lovable, or Grok Bot calls this workspace | Connect external agents with the MCP server at POST /mcp, and the MCP server tool reference |
| You want the scopes and rotation rules for those keys | API key security best practices |
Trace AI, Autonomic Agents, and platform skills run inside the console. They are documented under AI, agents, and MCP. The inbound agent entry on this page is the hosted MCP server.
Incoming HTTP events
A public POST lands on a surface this workspace already exposes: a WebApp of type webhook or callback, or an HTTP API operation. WebApps and ProcessFlow and WebApp async process trigger describe how that request starts a process.
The linked process checks an HMAC with tf.utils.hmacSha256Verify and a secret from tf.keystore. The message is raw_input. That guide includes the step snippet.
Calling a vendor MCP URL is the other direction: Remote MCP (remote-mcp-1.0.0) is Tealfabric opening that connection. It is listed under Tealfabric calls out.
See also
- Tealfabric calls out
- Expose a WebApp safely — learning path for a published WebApp
- Security, privacy, and compliance