Search K
Appearance
POST - Multipart API ​
Exposes a workflow as an HTTP POST endpoint that accepts multipart form data, including file uploads, and starts execution when the endpoint is called.
Purpose ​
Use this trigger when an external system needs to push a file into a workflow along with accompanying form data. The trigger handles the file transfer and URL parameters so that downstream tasks can immediately work with the uploaded file and its metadata. It is the preferred entry point for workflows that ingest files from third-party tools, client applications, or automated scripts that communicate over HTTP.
Inputs ​
| Field | Type | Required | Description |
|---|---|---|---|
| Requires Authentication | Checkbox | No | When checked, the endpoint requires a valid MinuteView authentication token before the workflow runs. Leave unchecked to allow unauthenticated access. |
| Allowed IPs | Textarea | No | Enter one IP address per line. If any IPs are listed, only requests from those addresses will be accepted — all others receive a 403 response. Leave blank to allow requests from any IP. |
Outputs ​
| Name | Description |
|---|---|
| UrlParams | A key-value dictionary of the URL query parameters supplied with the request. |
| FormFields | A key-value dictionary of the form fields included in the multipart body. |
| (file name) | The local path to the uploaded file in the working folder. The key is the file's base name without extension. |
| CallerIP | The IP address of the system that called this endpoint. Use this to identify the caller's IP before adding it to the Allowed IPs list. |
IP Allowlisting ​
The Allowed IPs field lets you restrict which systems can trigger the workflow. When one or more IPs are entered, any request from an address not on the list is rejected with a 403 Access denied response before the workflow runs.
Recommended setup when locking down a workflow:
- Leave Allowed IPs blank initially and run the workflow once from your external system.
- Check the CallerIP output variable in the workflow run history to see the IP address that made the call.
- Copy that IP into the Allowed IPs field and save the workflow.
Multiple IPs are supported — enter one per line.