Custom API
Import an OpenAPI description or define an HTTP operation, configure its connection, and expose the approved action to workflows.
OpenAPIAuthenticationInputsResponses
Integrations
Give workflows the tools they need—and nothing more.
Turn approved API operations and data transformations into reusable workflow tools with explicit connections, inputs, and outputs.
Tool catalog
Reliable building blocks for connected workflows.
Keep external actions and data shaping explicit, testable, and reusable across workflow definitions.
JSON extractor
Select specific values from structured output using explicit paths, then give downstream nodes a smaller, stable result.
Field selectionStable outputsReusable operation
JSON transformer
Reshape data between systems with a defined transformation and preview the result before using it in a workflow.
JSONataPreviewVersioned operation
Python tool
Perform focused computation with Python, NumPy, and pandas inside a network-isolated sandbox.
Pure computeImmutable revisiongVisor sandbox
Connection lifecycle
From API description to governed workflow action.
Taskmesh separates the reusable operation, organization-specific connection, workflow mapping, and individual invocation.
Describe
Define the API operation and its request and response shapes.
Configure
Attach the organization’s endpoint and authentication method.
Grant
Approve the operation and resources the installation may use.
Map
Bind workflow data to explicit tool inputs.
Invoke
Execute in the context of a versioned workflow run.
Integration policy
Use the interface the system was designed to expose.
Taskmesh works through published APIs. This preserves the external platform’s validation, permissions, lifecycle rules, and audit boundaries.
No direct database access
External application databases remain behind the application’s own service boundary.
Explicit resource grants
An installation can be limited to approved operations and resources.
Validated runtime context
Accepted context is checked against the selected published workflow before execution.
Credential boundaries
Connect without passing secrets through the graph.
Credentials belong to configured connections and remain outside broadly readable workflow definitions and routine node output.
Review the security model- Organization-scoped connection configuration
- Explicit credential requirements per operation
- Server-side tool invocation
- Workflow and run context attached to execution