Nodes/Phota API Nodes/Phota Delete Profile
ComfyUI Node

Phota Delete Profile

Permanently removing a Phota profile (and the latch that stops you by accident)

By photalabs·Created 3 months ago·Updated 3 months ago· 0
Phota Delete Profile
  • profile
  • status
profile_id
confirmfalse
api_key

The profile trash can

Every profile in Phota is the product of a billed training run - photos you uploaded and paid to have turned into a reusable subject. When you're done with one (that test dog you trained on forty shots, the client whose batch just shipped), PhotaDeleteProfile is how it leaves your account. It's the pack's cleanup node, and it's the one tool in here that refuses to do its job until you explicitly ask for it, twice.

How it works

The node calls the Phota API's delete endpoint for the profile you point at and returns a short status string like abc123: ok when it's gone. The interesting part is the confirm switch, which defaults to off. Leave it off and the node does nothing but raise a "Refusing to delete… flip the confirm toggle on" error. That's your dry-run mode: wire everything up, run once with confirm off to make sure you've got the right profile, then flip the toggle and run again for real. There's no trash bin and no undo, and the pack's own warning is blunt - deletion is permanent and unbilled training isn't refunded.

Two details worth knowing: it's an output node, and the profile_id field accepts comma-separated IDs, so you can sweep a whole batch of abandoned subjects in one run.

The inputs that matter

There are really only two you'll touch:

  • profile_id - paste an ID, or better, wire the profile socket from a Phota Profile Selector or Train Profile node. A connected socket overrides whatever you typed.
  • confirm - the safety latch. Must be flipped on to actually delete anything.

The optional api_key field behaves like everywhere else in this pack: leave it empty and use the PHOTA_API_KEY environment variable or a phota.ini file, because a key typed into a widget gets embedded in your workflow JSON/PNG the moment you share it.

Install & the shared setup

Identical to the rest of the pack. In ComfyUI Manager search for Phota API Nodes, or:

cd ComfyUI/custom_nodes
git clone https://github.com/photalabs/comfyui-phota

…then restart ComfyUI. The only dependency is requests, which ComfyUI already ships; nothing runs on your machine, so there's no GPU and no model download. You'll need an API key from the Phota developer portal (platform.photalabs.com), and deletion is a free call - no generation is billed here.

Gotchas

  • No undo, no refunds. Deletion is permanent, and if you trained without paying for it yet, that bill isn't reversed. Verify with confirm off before you commit.
  • A bad key surfaces as a readable 401 ("check your key"), and running out of credits is a 402 - the pack maps both to plain-language errors rather than a cryptic stack trace.
  • The node is a delete-by-default-cautious design, which is the right call for an API that can't be un-fired.
CategoryPhota

Inputs (4)

NameTypeDefaultDescription
profile_idSTRING
confirmBOOLEANfalseDeletion is permanent and unbilled training is not refunded. Flip on to proceed.
api_keyoptSTRINGLeave empty (recommended) to use the PHOTA_API_KEY environment variable or phota.ini. A key typed here is saved inside the workflow — do not share such workflows.
profileoptPHOTA_PROFILEProfile reference from a Phota Profile Selector or Train Profile node. Overrides profile_id.

Outputs (1)

NameTypeDescription
statusSTRING