• AI reference · Area channel

record_packaging

Record packaging. A film's packaging: two to four title and thumbnail options, and optionally your pick.

Where it is

In the channel area (the content pipeline, results and the YouTube channel): open it with tools_for { area: "channel" }, then call it with use_tool { name: "record_packaging", args }.

Does it need a yes?

Runs at once, no yes card: it changes only the office's own working state, and nothing reaches anyone. Here: title options.

Inputs

InputTypeNeededAbout
filmIdstringyes1 to 160 characters
optionsarray of objectyes2 to 4 items
options[].keystringyesformat `^[A-Z]$`
options[].titlestringyes1 to 100 characters
options[].thumbnailAssetIdstringyes1 to 160 characters
options[].anglestringnoup to 160 characters
options[].wordsstringnoup to 160 characters
options[].postingThumbnailUrlstringnoThe thumbnail's link at the posting service, when it gave one · up to 400 characters
chosenKeystringnoformat `^[A-Z]$`
appliedbooleanno
slotstringnoup to 40 characters
pickBystringnoup to 40 characters
expectedRevisionstringnoup to 200 characters
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": "record_packaging",
  "arguments": {
    "filmId": "filmId",
    "options": [
      {
        "key": "key",
        "title": "Follow up with Ana",
        "thumbnailAssetId": "thumbnailAssetId"
      }
    ]
  }
}

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.