The specified module could not be foundregarding the
edge-jslibraries when accessing the
maxAllowedContentLengthproperty in the WorkflowGen
web.configfile. The following example shows how to configure this property as 1 MB (note that the value should always be specified in bytes, so the value in the example is 1,024,000 bytes). The default value is 30,000,000 bytes.
HooksInputFileAllowedFoldersparameter in the WorkflowGen
HooksInputFileAllowedHttpUrlsparameter in the WorkflowGen
HooksMaxInputFileSizeparameter in the WorkflowGen
HooksMaxInputFileContentSizeparameter in the WorkflowGen
node.exeinstance will handle HTTP requests. This should be sufficient in most cases, but you can optimize performance if needed by adjusting these values based on the number of potential concurrent requests.
operationrefers to the name of the operation to execute, and
inputnode that groups all of the request parameters to perform the operation.
processNameparameter is required. The
processVersionparameter is optional and is used to find the correct process you want to use to create your request.
:operationwith the name of the incoming webhook operation (e.g.
:operation: Name of the incoming webhook operation defined in the URI ✏️ Note: The operation name is not required inside the request payload.
x-wfgen-hooktoken: Webhook token value specified in the HTTP request header, which is the same token value as used in a classic incoming webhooks URL
*next to their name
createRequestoperation payload. Be aware that a data with the same name and data type must previously exist in the process for each parameter in the array to store the parameter's value. The following example shows how to send parameters corresponding to the four supported data types (TEXT, NUMERIC, DATETIME, and FILE).