• AI reference · Area drops

fetch_submission

Fetch submission. Get an upload's files: into a folder on this Mac, or a signed link per file elsewhere.

Where it is

In the drops area (upload links, people's uploads and share links): open it with tools_for { area: "drops" }, then call it with use_tool { name: "fetch_submission", args }.

Does it need a yes?

Reads only: it changes nothing. Here: read.

Inputs

InputTypeNeededAbout
subIdstringyesThe upload's id from list_submissions · format `^[a-f0-9]{24}$`
leasestringyesThe lease claim_submission gave you · format `^[a-f0-9]{32}$`
deststringnoOn this Mac: an absolute folder. Elsewhere leave it out: you get a signed link per file · 1 to 1,024 characters
overwritebooleannoReplace a different file there (default: refuse)
taskintegernoThe task this work is for, so the owner sees it there. · 1 or more
run_idstringnoYour run id from the connector's start, so the output ties back to this session · format `^[A-Za-z0-9_.:@-]{1,120}$`

Example

{
  "name": "fetch_submission",
  "arguments": {
    "subId": "subId",
    "lease": "lease"
  }
}

When it is refused

  • invalid: The input isn't right. The sentence names the field and the fix; nothing was done. Fix it and call again.
  • not_found: No such thing in this company (a task, file, person, record). Check the number or name, or list first.
  • not_allowed: Not without another step: the owner's yes, your own task held with pick_up, or a setting the owner turns on. The sentence says which.
  • taken: Someone else holds it (another AI on that task). Pick another task.
  • stale: It changed since you read it. Read it again and use the new version.
  • failed: On our side or a service's, never your input. Try again in a minute; if it keeps failing, call report_problem.