Piping options?
Posted: Thu Apr 28, 2016 10:38 am
Are there any options that can be passed with email piping, such as determining the category, sender, reply to, etc.
I'm starting from another form and want to create a categorized ticket on behalf of that user (form submission). If I send a message to HESK it just creates a generic ticket with the raw contents of the email in the form.
I can populate everything the way I need it with http $post, but I'm trying to do this myself, not redirect the user to pre-populated web form for them to have to submit it.
In other words, is it possible to pre-define all those things that you can with $post url encoding, except through piping, so tickets can be generated based on input from another source?
I'm starting from another form and want to create a categorized ticket on behalf of that user (form submission). If I send a message to HESK it just creates a generic ticket with the raw contents of the email in the form.
I can populate everything the way I need it with http $post, but I'm trying to do this myself, not redirect the user to pre-populated web form for them to have to submit it.
In other words, is it possible to pre-define all those things that you can with $post url encoding, except through piping, so tickets can be generated based on input from another source?