Vor Kurzem aufgerufene Suchen


Keine vor kurzem aufgerufene Suchen

john.witt's Avatar

john.witt

Beigetreten 16. Apr. 2021

·

Letzte Aktivität 27. Okt. 2021

Folge ich

0

Follower

0

Gesamtaktivitäten

4

Stimmen

0

Abonnements

3

AKTIVITÄTSÜBERSICHT

Neueste Aktivität von john.witt

john.witt hat einen Kommentar hinterlassen

Community-Kommentar Feedback - Ticketing system (Support)

I'll admit I have not read all the replies, but I came up with a kludge that works and adds CC emails if you have access (not sure what subscription level uses Notify Targets).

- Go to Admin; Settings; Extensions.

- Create a new HTTP target.

- URL: https://trendkitehelp.zendesk.com/api/v2/requests/{{ticket.id}}.json

- Method: PUT

- Content Type: JSON

- Enable basic authentication. I use my username/password (password is hidden) but I have not tried using an API token instead. I don't think admin is needed and though the user access was enough, but it failed without this.

- Click "Update Target" at bottom right and submit.


Now create a trigger with your required parameters and for actions choose "Notify Target" using the target you created above. For the JSON add the following:

{

   "request": {
        "email_ccs": [
            { "user_email": "first@example.com","action": "put"},

            { "user_email": "second@example.com","action": "put"}

           ]
    }
}

You can add more CCs, but remember if you have just one to remove that comma.

I'd recommend you do step-testing first. For example, replace the {{ticket.id}} with a real ID and instead of update use "Test Target" and paste your JSON. Look at the result and make sure the email CC is updated and then check the ticket CC to ensure the API PUT is working. If that works works, "Update Target" and create a Trigger that updates that Ticket, this time with a different email address to ensure the Trigger is running the API PUT. If that works, update the target back to {{ticket.id}} and update your Trigger back to the correct parameters and emails addresses.

John

Kommentar anzeigen · Gepostet 23. Apr. 2019 · john.witt

0

Follower

4

Stimmen

0

Kommentare