Mesa Script SDK

Automatically add JSON Content-Type headers and decode the response. Default: true

Parameters to append to the querystring.

Headers to send to the request.

Include headers in the response. The response format will be { "headers": {}, "body": {} }.

Log request information and response headers. Defaults to context.automation.debug.

Exclude headers from debugging information to keep secret keys a secret. An array of header keys (example: Content-Type).

If JSON response, and response has ints over the JS max int, will traverse entire payload and cast long ints to strings

Automatically add JSON Content-Type headers and decode the response. Default: true

Parameters to append to the querystring.

Headers to send to the request.

Include headers in the response. The response format will be { "headers": {}, "body": {} }.

Log request information and response headers. Defaults to context.automation.debug.

Exclude headers from debugging information to keep secret keys a secret. An array of header keys (example: Content-Type).

If JSON response, and response has ints over the JS max int, will traverse entire payload and cast long ints to strings

Automatically add JSON Content-Type headers and decode the response. Default: true

Parameters to append to the querystring.

Headers to send to the request.

Include headers in the response. The response format will be { "headers": {}, "body": {} }.

Log request information and response headers. Defaults to context.automation.debug.

Exclude headers from debugging information to keep secret keys a secret. An array of header keys (example: Content-Type).

If JSON response, and response has ints over the JS max int, will traverse entire payload and cast long ints to strings

Automatically add JSON Content-Type headers and decode the response. Default: true

Parameters to append to the querystring.

Headers to send to the request.

Include headers in the response. The response format will be { "headers": {}, "body": {} }.

Log request information and response headers. Defaults to context.automation.debug.

Exclude headers from debugging information to keep secret keys a secret. An array of header keys (example: Content-Type).

If JSON response, and response has ints over the JS max int, will traverse entire payload and cast long ints to strings

Automatically add JSON Content-Type headers and decode the response. Default: true

Parameters to append to the querystring.

Headers to send to the request.

Include headers in the response. The response format will be { "headers": {}, "body": {} }.

Log request information and response headers. Defaults to context.automation.debug.

Exclude headers from debugging information to keep secret keys a secret. An array of header keys (example: Content-Type).

If JSON response, and response has ints over the JS max int, will traverse entire payload and cast long ints to strings

One of GET, POST, PUT, PATCH, or DELETE

Automatically add JSON Content-Type headers and decode the response. Default: true

Parameters to append to the querystring.

Headers to send to the request.

Include headers in the response. The response format will be { "headers": {}, "body": {} }.

Log request information and response headers. Defaults to context.automation.debug.

Exclude headers from debugging information to keep secret keys a secret. An array of header keys (example: Content-Type).

If JSON response, and response has ints over the JS max int, will traverse entire payload and cast long ints to strings

The string to encode

The algorithm to use. Options: sha1, sha256, md5

The string to create the hash from

Should we base64-encode the raw value of the hash?

The algorithm to use. Options: sha1, sha256, md5

The string to create the hash from

Shared secret key used for generating the HMAC variant of the message digest

Should we base64-encode the raw value of the hash?

A default value to use if the secret cannot be found. If defaultValue is empty, the script will throw a fatal error if the secret is not found.

The credential key or id.

The value to save. This will be encrypted at rest, and can contained a stringified JSON array.

The SQL query to run

A default value to use if the storage key cannot be found. If defaultValue is empty, the script will throw a fatal error if the storage key is not found.

String representing a liquid template.

A keyed object of parameters to replace.

Type of webhook: json, shopify

Format of the returned data: string or array. If string, a full URL is returned. If array, URL will comprise two fields suffix and prefix

ID of the Automation

The key of the trigger

Parameters to send to the output, such as tokens to construct a Shopify API url

Defaults to false. Set to true if you are exploding multiple tasks that can be run in parallel.

Defaults to false. Set to true if you are exploding multiple tasks that can be run in parallel.

In the form ${automationKey}, this will trigger the first input in the Automation. In the form ${automationKey}/${inputKey}, this will trigger a specific input in the automation.

Typically passed from context.filename.

Typically passed from context.filename.

The xml file to be decoded

Namespace separator for replacing soapenv:Body type values with soapenv_Body

The object to be turned into xml.

Replace the default wrapping provided with another value

Namespace separator for replacing soapenv_Body: {} values with soapenv:Body

Defaults to true, which will return an object keyed by the first row in the CSV content. Set to false to return an array.

Defaults to true. Set to false to skip the header row when returning CSV.

The ID of the record to clear (returned as mesa_id in the Virtual Output).

The timezone identifier, like UTC or America/Los_Angeles. See a full list of TZ Database names.

The format of the outputted date string. See full list of options.

Defaults to now. Optional

All emails will be sent from [email protected]. The from email address will be used as the From name and reply-to email address.