V2NodesWebform Post
Webform Post
V2

Webform Post

Submit URL-encoded and multipart web forms from a Flowgear Workflow and return one normalized response row.

Revision History

0.0.0.1 - Initial release.

Connection

Use this Connection to store a reusable base URL and shared HTTP authentication settings for both form-post methods.

Property Type Description
URL String Optional base URL used when you supply a relative method URL.
Authorization HttpAuthorizationType Selects None, Basic, Bearer, or OAuth.
Username String Username used when Authorization is Basic.
Password Masked Password used when Authorization is Basic.
Bearer Token Masked Token used when Authorization is Bearer.
Auth URL String OAuth authorization endpoint used when Authorization is OAuth.
Token URL String OAuth token endpoint used when Authorization is OAuth.
Client ID Masked OAuth client identifier used when Authorization is OAuth.
Secret Key Masked OAuth client secret used when Authorization is OAuth.
Scope String OAuth scopes requested during authentication.
Access Token Masked OAuth access token populated after you connect the account.
Refresh Token Masked OAuth refresh token populated when the provider returns one.
Custom Headers String Additional headers in Key: Value format, one per line. Do not include Authorization when you also select an authentication mode.
Authentication Test Path String Relative or absolute path used by the Connection test action.
Authentication Test HTTP Method HttpTestMethod HTTP method used by the Connection test action: GET or OPTIONS.
Return Http Failure Responses Boolean When enabled, HTTP failures are returned as normalized response rows instead of being thrown as errors.

Setup Notes

  • Create a Connection when you want to reuse a base URL or shared authentication settings across multiple Workflows.
  • Enter a full URL on the Connection when the methods will call relative paths such as /submit or resource.
  • Select the Authorization mode that matches the upstream form endpoint. Leave it as None for anonymous forms.
  • For OAuth, complete the Flowgear connect flow first so the Access Token and Refresh Token are stored on the Connection before runtime calls.
  • If you want to validate the Connection in the designer, set Authentication Test Path to an authenticated endpoint that can safely handle GET or OPTIONS.
  • Use Custom Headers only for provider-specific headers. The Node manages Authorization, Cookie, User-Agent, Content-Type, and Content-Length.

Methods

Both methods submit one HTTP POST request and return one normalized response row.

Post Url Encoded

Use this method when the upstream form expects application/x-www-form-urlencoded data and no file upload is required.

Parameter Type Description
Connection Connection Optional Webform Post Connection with base URL and authentication settings.
URL String Relative or absolute URL for the target form endpoint. Relative URLs require Connection.URL.
Request Object Structured request object containing optional Headers, Cookies, UserAgent, and FormFields.
ReturnBodyAs WebformPostResponseBodyType Choose Text to decode the response body as text or Binary to keep the raw bytes.

The Request object lets you send form fields by name without building the encoded payload yourself. Header values, cookie values, and field values are sent as supplied.

Return Type Description
Response Object Normalized response object that includes statusCode, responseHeaders, and either responseBodyText or responseBodyBytes.

Post Multipart

Use this method when the upstream form expects multipart/form-data and you may need to include one file part.

Parameter Type Description
Connection Connection Optional Webform Post Connection with base URL and authentication settings.
URL String Relative or absolute URL for the target form endpoint. Relative URLs require Connection.URL.
Request Object Structured request object containing optional Headers, Cookies, UserAgent, FormFields, and one optional FilePart.
ReturnBodyAs WebformPostResponseBodyType Choose Text to decode the response body as text or Binary to keep the raw bytes.

The multipart Request.FilePart object contains Name, FileName, ContentType, and Content. If you omit ContentType, the Node uses application/octet-stream.

Return Type Description
Response Object Normalized response object that includes statusCode, responseHeaders, and either responseBodyText or responseBodyBytes.

Usage Notes

  • The Node always emits one response row per invoke. It does not split JSON payloads that contain items, results, or similar wrappers.
  • Successful calls return status = OK. Emitted failures return status = ERROR.
  • The Node only retries automatically for OAuth when the first response is a raw HTTP 401. Provider-specific authentication failures returned as 200 or 403 are surfaced without a generic retry.
  • Use Return Http Failure Responses when you want downstream Workflow logic to branch on failure rows instead of handling thrown errors.
  • If you need arbitrary HTTP verbs or raw request bodies, use the Web Request Node instead of Webform Post.

See also

Known Issues

  • The Node does not preserve a cookie jar across separate invokes. If the upstream form requires a stateful session, you must manage that state outside this Node.
  • The initial V2 surface supports zero or one multipart file part only.