Encoding Types

Overview

When defining an action for a custom connection, these encoding types are accepted:

• No encoding
• Full encoding (RFC 3986)
• UTF-8 encoding

By default, Full encoding (RFC 3986) is applied to all custom actions when creating.

Note: A trailing slash at the end of the relative path is removed by default. To preserve a trailing slash exactly as configured, enable the Preserve trailing slash option in the action's URL Settings.

No encoding

This option allows you to send query parameters without applying any additional encoding. Special characters and symbols are preserved exactly as provided.

However, for security and compatibility reasons, a syntactically valid URI is still required. This means certain reserved characters (such as #, ?, &, etc.) may still require manual encoding depending on their placement, especially if they interfere with URI parsing.

This mode should only be used when the receiving system expects and can correctly interpret raw or pre-encoded query strings.

Full Encoding (RFC 3986)

This option encodes the URL following the standards outlined in RFC 3986, which defines URL syntax. Below are examples of how the encoding is applied:

URL path example, with a dynamic and a static parameter:

Character Encoding:

UTF-8 Encoding

This encoding type encodes all dynamic query parameters, replacing all characters with UTF-8. It is typically used for handling special characters, internationalization, and extended character sets.

URL path example, with a dynamic and a static parameter:

Character Encoding: