PoYo Submit Job

Every other generation node in this pack submits and waits, blocking your graph until the pixels come back. PoYo_SubmitJob is the one that just submits. You hand it a model ID and the model's input JSON, it posts to PoYo, and you get back a task_id - that's it. The job runs on their servers while your workflow keeps going, and you decide later whether to wait on it, check on it, or walk away entirely.

That makes it the odd one out and genuinely useful in two situations. First, when you want to batch: queue up several jobs in one run without sitting through each one, then collect them afterward with PoYo_AwaitJob or PoYo_GetJobStatus. Second, when you want a webhook instead of a poll: the optional callback_url input hands PoYo a URL to ping when the job is done, so nothing in your graph has to babysit anything.

Mechanism. It needs two things: model_id - the catalog model ID as a plain string, not a dropdown, since the whole point is to run any model in PoYo's catalog including ones without a friendly node - and input_json, the JSON object that model expects. The pack's README is explicit that input_json follows the selected model's own catalog schema, so grab the schema for your model from the catalog before you guess. There's also an optional prompt field that, if you fill it, gets injected as the prompt key in the input - handy when your model's schema lives in input_json but you want the prompt visible in the workflow. Every submit carries a fresh idempotency key, and the node is marked non-idempotent, so ComfyUI won't cache it and each run does submit for real.

Outputs. Three STRINGs: task_id (feed this to PoYo_AwaitJob or PoYo_GetJobStatus), status (usually not_started right after submission), and response_json (the raw submit response).

Install. Part of poyo-comfyui, which needs ComfyUI 0.32.0+ (native node system). ComfyUI Manager (search "PoYo"), comfy node install poyo-nodes, or:

cd ComfyUI/custom_nodes
git clone https://github.com/PoyoAPI/poyo-comfyui.git

then restart. No models, no dependencies beyond ComfyUI's own.

Where people get burned. The big one is submitting without realizing nothing will wait for you - if you submit and the workflow ends, that job is still running (and still billing) on PoYo's side. Queueing a batch and forgetting about it is a great way to discover the concept of "metered" the expensive way. Second, the input_json schema: guess it wrong and you get an immediate 400. And as always in this pack, your API key comes from POYO_API_KEY or python -m poyo_nodes.configure - never from a node field.