Tealfabric calls out
Use this section when Tealfabric opens the connection: a process, an integration, or an agent calls another system. The connector catalog, OAuth2 setup, Nanites, and partner data APIs stay in their own sections. This page is the map.
Document information
| Field | Value |
|---|---|
| Canonical URL | /docs/03a_tealfabric-calls-out/00_introduction |
| Version (published date) | 2026-11-13 |
| Tags | integrations, connectors, outbound |
Choose the connection
| You need | Start here |
|---|---|
| A vendor that already has a connector | Connector catalog |
| An HTTP API with no dedicated connector | Generic REST API (restapi-generic-1.1.0) |
| A host that only your network can reach | Remote endpoints through a Nanite |
| Vendor login with OAuth2 | OAuth2 authentication |
| XML, SOAP, or a mixed response format | Choosing connectors for XML and other response formats |
| A vendor MCP server that Tealfabric should call | Remote MCP (remote-mcp-1.0.0) |
| A tested public dataset (countries, company registries, sanctions, open data) | Partner services |
| The call written inside a process step | Integration connectors, Webhook calls, Email sending |
Pull-style connectors, such as IMAP, belong here. Tealfabric initiates that connection on a schedule or from a step.
Where the detail lives
Connecting systems is the working section: authentication, workers, and the connector catalog. Read a connector page for parameters and operations, then create the Integration in the console and call it from ProcessFlow.
Partner services documents a short list of public APIs that have been tried with a normal REST integration. They are outbound calls, listed separately so the recipes stay easy to find.
See also
- External systems call Tealfabric — the other direction: API, WebApps, and the MCP server
- Automations and ProcessFlow
- Connect a system end-to-end — learning path for this direction