POST - MinuteView API

Exposes a workflow as an HTTP POST endpoint that accepts a JSON body, starting execution when the endpoint is called.

Purpose

Use this trigger when an external system or integration needs to send structured data to a workflow over HTTP. The JSON body and any URL parameters are parsed and made available to downstream tasks immediately. This is the standard entry point for event-driven integrations where another application needs to push data into MinuteView without a file attachment.

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.
JsonBody	The parsed JSON body sent in the POST request, available as a structured object for downstream tasks.
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:

1. Leave Allowed IPs blank initially and run the workflow once from your external system.
2. Check the CallerIP output variable in the workflow run history to see the IP address that made the call.
3. Copy that IP into the Allowed IPs field and save the workflow.

Multiple IPs are supported — enter one per line.