Get flows

Returns one automation and its latest version.

GET /v1/auto/flows/{id}

Addresshttps://api.hanzo.ai/v1/auto/flows/{id}
MethodGET
Operationget_auto_flows_by_id
AuthAuthorization: Bearer $HANZO_API_KEY

Returns one automation and its latest version. That is the flow record plus the step tree the builder edits; a flow of another org answers not-found.

Request

1 field.

FieldInTypeRequiredDescription
idpathstringyesID is the flow to act on, from the path.

Response

StatusBodyMeaning
200auto.populatedFlowok
defaultproblem-detailsrefused

200 body — 45 fields.

FieldInTypeAlwaysDescription
createdbodyinteger (int64)—Created and Updated are unix milliseconds.
externalIdbodystring—ExternalID is the caller's own id for this flow, if it set one.
folderIdbodystring—FolderID groups the flow in the builder's tree.
idbodystring—ID is the flow's id.
metadatabodyany—Metadata is the caller's opaque JSON, stored and returned verbatim.
projectIdbodystring—Org is the owning org, which this surface names projectId.
publishedVersionIdbodystring—PublishedVersionID is the version a run executes when set; empty means the latest version runs.
statusbodystring—Status is ENABLED or DISABLED — whether the flow's trigger is armed.
updatedbodyinteger (int64)—
versionbodyauto.FlowVersion—
version.createdbodyinteger (int64)—
version.displayNamebodystring—
version.flowIdbodystring—
version.idbodystring—
version.schemaVersionbodystring—
version.statebodystring—
version.triggerbodyauto.FlowTrigger—
version.trigger.displayNamebodystring—
version.trigger.namebodystring—
version.trigger.nextActionbodyauto.FlowAction—
version.trigger.nextAction.displayNamebodystring—
version.trigger.nextAction.namebodystring—
version.trigger.nextAction.nextActionbodyauto.FlowAction—
version.trigger.nextAction.settingsbodyauto.StepSettings—
version.trigger.nextAction.settings.actionNamebodystring—
version.trigger.nextAction.settings.inputbodyobject—
version.trigger.nextAction.settings.input.*bodyany—
version.trigger.nextAction.settings.pieceNamebodystring—
version.trigger.nextAction.settings.pieceVersionbodystring—
version.trigger.nextAction.settings.triggerNamebodystring—
version.trigger.nextAction.skipbodyboolean—
version.trigger.nextAction.typebodystring—PIECE | CODE | ROUTER | LOOP_ON_ITEMS
version.trigger.nextAction.validbodyboolean—
version.trigger.settingsbodyauto.StepSettings—
version.trigger.settings.actionNamebodystring—
version.trigger.settings.inputbodyobject—
version.trigger.settings.input.*bodyany—
version.trigger.settings.pieceNamebodystring—
version.trigger.settings.pieceVersionbodystring—
version.trigger.settings.triggerNamebodystring—
version.trigger.strategybodystring—
version.trigger.typebodystring—PIECE_TRIGGER | EMPTY
version.trigger.validbodyboolean—
version.updatedbodyinteger (int64)—
version.validbodyboolean—

Failure carries the platform error shape — see Errors.

Examples

hanzo auto flows get <id>
import { Configuration, AutoApi } from 'hanzoai';

const api = new AutoApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getAutoFlowsById({ id: 'id' });
from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import AutoApi

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = AutoApi(client).get_auto_flows_by_id(id='id')
cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.AutoAPI.GetAutoFlowsById(context.Background()).Execute()
if err != nil {
	return err
}
use hanzo_client::apis::{configuration::Configuration, auto_api};

let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();

let result = auto_api::get_auto_flows_by_id(&cfg, Default::default()).await?;
import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.AutoApi;

ApiClient client = new ApiClient();
client.setBearerToken(System.getenv("HANZO_API_KEY"));

var result = new AutoApi(client).getAutoFlowsById();
curl https://api.hanzo.ai/v1/auto/flows/<id> \
  -H "Authorization: Bearer $HANZO_API_KEY"

MCP reaches auto through the auto tool, which names its 14 operations with its own verbs — this one among them, under a name only MCP declares. describe explains any of them:

curl -X POST https://api.hanzo.ai/v1/mcp \
  -H "Content-Type: application/json" \
  -d '{
       "jsonrpc": "2.0",
       "id": 1,
       "method": "tools/call",
       "params": {
         "name": "describe",
         "arguments": {
           "op": "list_auto_flows"
         }
       }
     }'

Auto API · All Hanzo APIs · Interactive reference

Was this page useful?