Outputs to a user defined API endpoint.
Body Content Types
|
Type |
Description |
||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Item Metadata Json (application/json) |
Preconfigured output in JSON format. |
||||||||||||||||||
|
Item Metadata XML (text/xml) |
Preconfigured output in XML format. |
||||||||||||||||||
|
Item Metadata CSV (text/xml) |
Preconfigured output in CSV format. |
||||||||||||||||||
|
Attachment Template (application/json) |
Custom output in JSON format. You must construct a valid JSON payload manually. Example:
If only one attachment exists, the output will be: JSON
If multiple attachments exist, the output will be:
|
||||||||||||||||||
|
Per Attachment Request (application/json) |
When this type is specified, a new request is sent separately for each attachment. Supports the following attachment placeholders:
Example:
|
||||||||||||||||||
|
Custom Json (application/json) |
Custom output in JSON format. You must construct a valid JSON payload manually. Example:
|
||||||||||||||||||
|
Custom XML (text/xml) |
Custom output in XML format. You must construct a valid XML payload manually. Example: HTML
|
||||||||||||||||||
|
Custom Text (text/plain) |
Custom output in just a string output. Use this to just send plain text to the end point. Example:
|
||||||||||||||||||
|
Custom Form (application/x-www-form-urlencoded) |
Custom output in XML format. Example:
|
Parse response as JSON
Enabling this option means the return properties are generated from the JSON payload.
Example Return Payload:
{
"FirstName": "Bobby",
"LastName": "Brown",
"Age": 22
}
This would create the following return properties
|
Property |
Example Placeholder |
Returned Value |
|---|---|---|
|
FirstName |
|
Bobby |
|
LastName |
|
Brown |
|
Age |
|
22 |