Run a webhook automation on posted files
No key: the token is the credential, shown on the automation’s page and as its trigger_url. Post a file (multipart file), or JSON with url or urls (up to 20). Each file is one run, on the workspace’s credits, and its results go where the automation sends them. inputs fills its steps’ {{names}} for this request, over the ones it stores — JSON, or form fields inputs[title]. An automation whose first step makes its own file takes no file, only its inputs. 413 over an upload page’s own largest file. 429 past 120 posts from one network in 10 minutes, or once it has started most_runs_a_day runs in 24 hours, or when not even its cheapest run fits under most_credits_a_month, when it has those limits.
Authorizations
Headers
Retry this POST safely: the first request with a key runs and its answer is kept for a day; a retry with the same key and the same request gets that answer again, marked Idempotent-Replayed: true, instead of running twice. 1–255 printable characters — a UUID is a good one.
1 - 255Body
Values for the steps' {{names}}, like {"title": "Summer sale"}. A required input with no default has to be sent; a name the steps don't use is refused. describe_recipe, or GET /api/v1/recipes/{ref}, lists them under inputs. In a multipart form, send a JSON string or one field per input, inputs[title].

