| Info | |
|---|---|
| title | Usage note!Use this only in the case were attachment is needed, since the payload is different than regular application/json types. |
...
iHub can send attachments to external endpoints. This is done. by sending Content-Type: multipart/form-data.
Content-Type: multipart/form-data
The body will be included in the payload:
| Code Block |
|---|
Content-Disposition: form-data; name="file" filename="filename_A.xyz"
(content of filename_A.xyz)
Content-Disposition: form-data; name="file" filename="filename_B.xyz"
(content of filename_B.xyz)
Content-Disposition: form-data; name="body"
{the_body_section_of_the_config_page any content added in the body will be sent as a variable called body}
Content-Disposition: form-data; name="formVar_A"
{the_formVar_A_content the name of a form var and the content}
Content-Disposition: form-data; name="formVar_B"
{the_formVar_B_content the name of a form var and the content}
|
Do not include attachments - This is the standard way of just sending normal JSON data. | |
Latest - any added attachment during the issue event will be added. Attachments older than 5seconds after the event occurs will not be added. | |
All - Include all attachments in the payload multipart data | |
Incoming - When this integration is part of an incoming rule. Read more on incoming: Incoming REST Calls | |
Form variable value | The file parameter can be changed by changing the Form variable value. This can be needed for some APIs to accept attachments. Like Freshdesk needs the file var to be named attachments[] |
Skip sending variables that has an empty value | Will remove parameters with empty values from the payload |
Implementation of https://datatracker.ietf.org/doc/html/rfc7578 specification.
Mustache variables can be used in both Form vars as in the body.