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
FieldValue
Canonical URL/docs/03b_external-systems-call-tealfabric/00_introduction
Version (published date)2026-11-13
Tagsapi, webapps, mcp, inbound

Choose the entry point

You needStart here
Your service calls workspace data or runs a process over HTTPAPI for developers, then API key management and the endpoint index
People use a page, form, or file you publishApps, webhooks, and surfaces and the WebApps user guide
End users sign in to that WebAppWebApps authentication
The WebApp is served on your domainWebApp custom domain
Cursor, Claude, Lovable, or Grok Bot calls this workspaceConnect external agents with the MCP server at POST /mcp, and the MCP server tool reference
You want the scopes and rotation rules for those keysAPI 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