Skip to main content

Manual Trigger

Type ID: manualTrigger  ·  Kind: Trigger  ·  Trigger style: manual  ·  Ports: 0 in, 1 out

Starts a workflow run on demand. The payload passed to the start-execution call becomes the initial item emitted to downstream nodes.

Credentials​

None

Properties​

PropertyKeyTypeRequiredDefaultPossible valuesApplies when
Payload SchemapayloadSchemaarrayNo[]Array of payload entries (see below). Used by the UI to validate test payloads.Always

payloadSchema → payload (array)​

Each payload entry declares one expected payload key:

PropertyKeyTypeRequiredDefaultPossible valuesApplies when
KeykeystringYes''Payload key to validateAlways
TypetypeoptionsYesstringstring (String), number (Number), boolean (Boolean), dateTime (Date & Time), options (Options), json (JSON), file (File)Always
Display NamedisplayNamestringYes''Form label for the payload fieldAlways
RequiredrequiredbooleanNofalseRequire a value before submitting the formAlways
Defaultdefaultstring / number / booleanNotype-dependentValue used to prefill the inputtype = string/dateTime/options/json (string default), number (number default), or boolean (boolean default)
DescriptiondescriptionstringNo''Helper text shown under the fieldAlways
Minimum LengthminLengthnumberNo-Minimum number of characters acceptedtype = string
MinimumminnumberNo-Minimum accepted valuetype = number
MaximummaxnumberNo-Maximum accepted valuetype = number
OptionsoptionsarrayNo[]Choices available for the field - each entry has name and value (both required strings)type = options
AcceptacceptstringNo''Comma-separated MIME types or file extensions accepted by the file inputtype = file
Max Size (MB)maxSizeMbnumberNo10Client-side file size cap; the server limit is always 10 MBtype = file

Notes​

  • If the test payload includes a binary key, it's split off into the item's binary slot; the rest is emitted as json.
  • payloadSchema only drives UI validation of the test payload — it doesn't filter or alter the emitted data.