Skip to main content
RemoteWorkflow allows you to run workflows that are hosted on a remote AgentOS instance. It provides the same interface as a local workflow, making it easy to integrate remote workflows into your applications.

Installation

Basic Usage

Parameters

ParameterTypeDefaultDescription
base_urlstrRequiredBase URL of the remote AgentOS instance (e.g., "http://localhost:7777")
workflow_idstrRequiredID of the remote workflow to execute
timeoutfloat300.0Request timeout in seconds
config_ttlfloat300.0Time-to-live for cached configuration in seconds

Properties

id

Returns the workflow ID.

name

Returns the workflow’s name from the remote configuration.

description

Returns the workflow’s description from the remote configuration.

db

Returns a RemoteDb instance if the workflow has a database configured.

Methods

arun

Execute the remote workflow asynchronously.
Parameters:
ParameterTypeDefaultDescription
inputstr | Dict | List | BaseModelRequiredThe input for the workflow
additional_dataOptional[Dict]NoneAdditional data to pass to the workflow
user_idOptional[str]NoneUser ID for the run
run_idOptional[str]NoneCustom run ID
session_idOptional[str]NoneSession ID for context persistence
session_stateOptional[Dict]NoneSession state dictionary
imagesOptional[List[Image]]NoneImages to include
audioOptional[List[Audio]]NoneAudio to include
videosOptional[List[Video]]NoneVideos to include
filesOptional[List[File]]NoneFiles to include
streamboolFalseWhether to stream the response
stream_eventsOptional[bool]NoneWhether to stream events
auth_tokenOptional[str]NoneJWT token for authentication
Returns:
  • WorkflowRunOutput when stream=False
  • AsyncIterator[WorkflowRunOutputEvent] when stream=True

cancel_run

Cancel a running workflow execution.
Parameters:
ParameterTypeDefaultDescription
run_idstrRequiredID of the run to cancel
auth_tokenOptional[str]NoneJWT token for authentication
Returns: bool - True if successfully cancelled

get_workflow_config

Get the workflow configuration from the remote server (always fetches fresh).
Returns: WorkflowResponse

refresh_config

Force refresh the cached workflow configuration.
Returns: WorkflowResponse

A2A Protocol Support

RemoteWorkflow can connect to any A2A-compatible server using the protocol="a2a" parameter:

Connecting to Agno A2A Servers

Protocol Options

Protocola2a_protocolUse Case
"agentos"N/ADefault. Connect to Agno AgentOS REST API
"a2a""rest"Connect to A2A servers using REST endpoints
"a2a""json-rpc"Connect to Google ADK or pure JSON-RPC A2A servers

Using in AgentOS Gateway

Remote workflows can be registered in a local AgentOS to create a gateway:
See AgentOS Gateway for more details.

Streaming Example

Error Handling

Authentication

For authenticated AgentOS instances, pass the auth_token parameter:

Notes

Remote Workflows via WebSocket are not yet supported. Use HTTP streaming instead.