/build/static/layout/Breadcrumb_cap_w.png

Using a Google Form Email to create a ticket and assign owner

I have a Google form.  My google form will send an email to my K1000 and open a ticket.

What I can't figure out is how to assign an owner to the ticket.

I have in the email body of the message created:
@owner=myemail@domain.com

I've tried 
@owner=username too



5 Comments   [ + ] Show comments
  • We use a similar system (a contact form on our external site using Wordpress, which emails our K1000 and creates a ticket) and it seems to work well. Where in the email does the client callout happen?

    I have all of our various @ callouts at the top of the email, prior to the body/content of the email. Like this:

    -------------------------
    @client=[clientemail]
    @title=[emailtitle]
    @category=[category]
    @owner=john_doe@ourcompany.com

    [Message body] - tshupp 8 years ago
  • We also use a similar system (JotForm) No issues here and just like tshupp said. The "@" needs to be at the top before anything else. The other way you can do it is to set a title like "Form Ticket - TICKET TITLE" and then use a ticket rule to set the owner of the ticket when it comes in. Just by looking for the "Form Ticket" in the title. Also make sure that the email that is sent is in plain text not HTML. We found that HTML caused issues with the processing of the email. - smalls 8 years ago
  • The plain text thing came to me late last night because as I was looking at it I did notice that the @owner etc come through as a hyperlink. I'll do some more testing and see if there is a away to make it come through as plain text. I am not sure there is in a Google App Script. - ken2015 8 years ago
    • I just looked at some of my tests - the one where I used @owner=username shows in KACE as not a hyperlink. My account does have permissions to change ownership. - ken2015 8 years ago
  • the account I am using (mine) has full admin on the system and I can manually assign owners in the KACE GUI, so I suspect my account has the ability to change the owner via email. - ken2015 8 years ago
  • Ken - Can you share with how you got this Google Form to populate a ticket in Kace? - lbruschuk 4 years ago
    • There isn't any magic to it. You need to look up how to make a google form use the script mail function. The to will be your Kace email account. - ken2015 4 years ago
      • Excellent. We currently use a google form that staff fills out for their tech requests. I want to tie the fields in that form to auto populate a ticket. Any steps you have would be welcome. - lbruschuk 4 years ago

Answers (2)

Posted by: ken2015 8 years ago
Senior White Belt
0
Chuck's answer is correct: 
The submitter doesn't need to be an owner, but must have permissions to change the owner. That's a subtle distinction but important. You can set the permissions on each field separately.

I simply created a ticket rule that says any ticket created that starts with a subject of X gets assigned to a particular user.  That will work for me at this point.
Posted by: Hobbsy 8 years ago
Red Belt
0
I think you will find that you need to be a ticket owner to use the @ codes, so your incoming email, from your google form may need to be from an email address associated with a ticket owner in your K1000

Comments:
  • The submitter doesn't need to be an owner, but must have permissions to change the owner. That's a subtle distinction but important. You can set the permissions on each field separately. - chucksteel 8 years ago
    • So Chuck, how do you suggest the customer sets the values of his fields within the queue - User Modify? - Hobbsy 8 years ago
      • Yes, in order to set the owner the submitter (which in this case is the email address that the Google form sends as) needs to have modify access to the owner field. - chucksteel 8 years ago

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ