• AI reference · Area channel

record_post

Record post. Record a post made outside the platform (for example one the owner posted by hand), or correct one.

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_post", 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: a planned post's record; posting is a post yes.

Inputs

InputTypeNeededAbout
idstringyesThe piece's Media id · 1 to 160 characters
platform"instagram" | "youtube" | "linkedin" | "tiktok" | "website" | "other"yes
urlstringnoup to 2,048 characters
postedAtstringnoup to 40 characters
state"draft" | "scheduled" | "live" | "failed"no
scheduledForstringnoup to 40 characters
providerstringnoup to 40 characters
providerIdstringnoup to 240 characters
accountIdstringnoThe scheduler's account id for this company's channel (see channel_status) · up to 80 characters
titlestringnoup to 200 characters
thumbnailAssetIdstringnoup to 160 characters
errorstringnoup to 600 characters
pinNeededbooleanno
versionstringnoup to 20 characters
surfacestringnoup to 120 characters
visibility"public" | "unlisted" | "private" | "unknown"no
accountstringnoup to 120 characters
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_post",
  "arguments": {
    "id": "id",
    "platform": "instagram"
  }
}

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.