Langflow: connection and validation
Limited coverage · Reviewed 2026-09-07
The runnable component passes actual lfx 1.12.0 invocation over authenticated managed MCP, including prepare, owned checkpoint and explicit approved resume with independent target-receipt verification.
Connect Langflow through the managed companion
Create a workspace for Langflow Open Langflow setup · Start with the free sample
- Create your free workspace and verify your email. On the dashboard, run the local allow/block sample and inspect the saved audit and actual signing status. This requires no model or external target; it does not connect a client or create independently verified proof.
- Return to your saved Langflow setup. Create its real
managed-mcpinstallation, then download the configuration and local package commands bound to that installation. Agent association is optional. Configuration starts read-only. - Load the creator’s scoped API credential on the controlled companion host and run the one-use connection challenge there. Credentials never belong in a public workflow, model prompt or exported configuration. Recorded credential proof does not attest native installation or a target effect.
- Install
managed-mcp/clients/pythoninto the same Python environment as Langflow. Loadclients/langflow/praesidia-managed-action.pyfrom the matching checkout as a custom component, set the companion endpoint and Secret input, and start with connection. Keep host retries disabled. - Inspect connection from the native client. To execute, bind an authorized registered target and obtain its public signing key independently. Preparation stops for a different human reviewer. Resume needs the exact stored approval, request commitment and explicit confirmation; ambiguous attempts must not be retried blindly.
- Refresh the workspace and inspect the server-returned action bound to this installation. A successful connection or copied guide is not execution evidence.
For n8n, Dify and Langflow, the operator supplies a reachable authenticated HTTPS companion endpoint and a separate companion bearer in the client secret store. One companion has one creator and installation; workflow or chat identities do not establish separate delegated users.
Exact local package, credential and native client instructions · Read-only public configuration template
Source paths in those instructions refer to the matching checkout supplied by your deployment operator. No public package or marketplace release is assumed. Free setup remains available; protected execution requires proof.actions and the appropriate role and scopes. Payments are currently unavailable. Provider usage may have separate charges.
Connection acceptance comes before a coverage claim
This distribution profile is separate from native runtime enforcement. Check the exact client version, transport, authentication, and tool surface with the operator. No marketplace listing or automatic interception is implied.
Setup instructions for this profile come from the SDK documentation your deployment operator provides.
- Configure a dedicated test connection with minimum scopes. Never paste a runtime secret into a public workflow or repository.
- Discover the tools and allow only the intended tool set. Confirm the exact transport supported by your installed client.
- Make one harmless managed call. Check denial and revoked credentials; a client that continues after a failed policy hook does not enforce that hook.
- Inspect the action ID in Praesidia. Report whether the test covered a managed call, native interception, or observation only.
- Only explicit tools on the configured Praesidia companion are governed; unrelated native tools remain outside this boundary.
- Packages are local release candidates. Real API/backend datastore installation-bound acceptance is pending the combined customer run; publication and deployed customer workspaces need separate acceptance.
- One companion uses one operator-configured creator and installation. It does not infer end-user delegation from a workflow or chat identity.
- Acceptance loads the actual component and resolves its output; a deployed Langflow editor, secret store and hosted flow scheduler have not been exercised.
- Install the bundled Python client into the same environment as Langflow. The token uses SecretStrInput and host retries must remain disabled.
Alternative: earlier narrow source example
This separate example is not the managed companion setup above and does not establish an installation-bound connection. Preserve its narrower scope when evaluating it.
Download langflow-praesidia-checkpoint.py · All source instructions
Provide your operator's endpoint, registration, and credential reference. No secret belongs in these files. This example only prepares registered HTTP requests and reads owned checkpoints. It does not approve or resume them. Configuration and isolated fixture checks do not establish a completed client authentication run.
Set up this alternative
Paste langflow-praesidia-checkpoint.py into a new custom component in a disposable Langflow flow. It uses the actual lfx==1.12.0 component API and a SecretStrInput. Store the caller credential through that secret input; keep it out of exported flows and prompts. The origin is an operator-controlled class constant, fixed to https://api.praesidia.ai; it is not an agent input. The same caller permissions and registered-target requirements above apply.
For prepare, provide the organization UUID, registered target ID, exact JSON object through the request-body input, and a unique stable workflow run ID. The output contains the pending checkpoint. Retain it and the original request for separate review. For checkpoint, provide the organization UUID and returned approval UUID. Each output resolution reads fresh state. The component never approves or resumes requests, follows redirects, or retries a failed request automatically. It preserves an unknown outcome as unknown.
This custom component is used because Langflow's generic OpenAPI Agent is a broader HTTP tool; importing a schema there alone does not establish this component's fixed-origin and secret-input behavior. This is an explicit workflow step, not a host-wide enforcement hook or a marketplace publication.
Validation on 2026-09-06: Python 3.12 with lfx==1.12.0 evaluated the source and built its real input/output template. Seven tests use the actual component output resolver and HTTPX's local mock transport: exact preparation, fresh checkpoint reads, input rejection before network access, denial/redirect handling, no retry on timeout, unknown/malformed outcomes, and the secret-input template. No real Langflow deployment, account, or API request was used.
To reproduce from this source directory in a disposable environment:
python3.12 -m venv .example-venv
.example-venv/bin/python -m pip install 'lfx==1.12.0'
.example-venv/bin/python test_langflow_checkpoint.py -v
Primary contracts: Langflow component source and generic OpenAPI Agent, read 2026-09-06.