Connect the systems your work depends on.
An automation platform is useful when it can do the work. Runfabric starts with broad protocol support and explicit execution profiles, so you can connect a system without waiting for a vendor-specific node.
Four ways to integrate.
| Capability | How it works |
|---|---|
| HTTP APIs | Configured REST or GraphQL operations with fixed hosts, methods, input mappings and credential references. Hosted or local. |
| MCP servers | Remote HTTP tool discovery and calls with explicit tool allowlists. Local stdio servers run on your worker. |
| Command-line tools | Fixed executables and argument mappings on your own worker. No shell interpolation or unrestricted command strings. |
| Model brokers and agents | Your OpenRouter or compatible endpoint, model, credential and allowed tools. Bounded iterative agent execution. |
Profiles turn a protocol into an operation.
An integration profile binds an activity kind to an operation. A GitHub issue lookup can be an HTTP GET with a fixed host and mapped repository and issue inputs. Company research can be an agent allowed to call only your configured search and CRM tools.
The workflow references the activity kind and passes structured input. Inspect the profile, test it and revoke access through the API or web app. Credentials are supplied separately and remain write-only in the management interface.
Choose where integrations execute.
| Capability | How it works |
|---|---|
| Public HTTP and remote MCP | Hosted runner or your own worker. |
| Model choice | Your broker, model and credential in either execution environment. |
| Local CLI and stdio MCP | Your worker only. Hosted execution cannot start local processes. |
| Hosted secrets | Encrypted in control-plane storage, separate from workflow definitions. |
| Private worker secrets | Your environment or secret manager. The worker submits run outputs, not its environment. |
Triggers bring the work in.
Create an authenticated webhook that starts a published version. Verify the configured secret or signature and record the provider delivery id. Repeated identical deliveries return the same run; conflicting content under one delivery identity is rejected.
Schedules store recurrence, timezone, version and input. They run independently of your browser or coding agent. Pause them and inspect occurrence history; delayed ticks follow a bounded catch-up policy.
Add your own handler.
Implement an activity handler with the SDK when a profile is not enough. A worker claims an activity, heartbeats its lease and reports a fenced result. This supports private SDKs, specialized runtimes and tools without HTTP or MCP interfaces.