Can I use triggers to automatically CC end users?

Return to top

13 Comments

  • SSL

    You can, but it's a bit of a smelly workaround.

    Set up an HTTP target in the Extensions menu:

    Then set a trigger to notify the target and add the JSON below:

    {
    "ticket": {
    "additional_collaborators": [{"user_email": "Email address goes here", "action": "put"
    }]
    }
    }

    Simples!

    ...but dirty.

    0
  • Morgan McCallum

    嘿,理查德,

    I'm trying your work around but it doesn't ever seem to update the CC's with my user that I am trying to add.

    What is the endpoint parameter you're using in the screenshot? I am assuming it's {{ticket.id}} but.. i'm not able to get it to update.

    I am also trying to manually update through postman with the direct ticket ID to test the JSON - the call goes through with a 200 but no actual updates..

    Though I'm wondering if they closed that gap since it's only supposed to be agents that are able to be added via automation? Any extra help you can offer would be awesome. I have a customer that needs one of their users CC'd on all their tickets. And the zendesk option of opening them up to the rest of the org doesn't work because they don't use the portal.. they only operate through email with us.

    0
  • 希瑟·隆美尔
    Community Moderator
    The Product Manager Whisperer - 2021

    The endpoint in the extension is something likehttps://YOURSUBDOMAIN.zendesk.com/api/v2/tickets/{{ticket.id}}.json+?ticket[additional_collaborators]=

    1
  • Morgan McCallum

    Thanks Heather... That doesn't seem to be working either. Still getting 200 but no updates to the ticket.

    BUT -

    I did get it to work with the following:
    I set the HTTP target endpoint to
    https://YOURSUBDOMAIN.zendesk.com/api/v2/tickets/{{ticket.id}}

    the body of the trigger I used was:

    {
    "ticket": {
    "additional_collaborators": [ user id, "user email", { "name": "user name", "email": "user email" } ]
    }
    }

    This created my new ticket and automatically added the end user as a CC

    2
  • 希瑟·隆美尔
    Community Moderator
    The Product Manager Whisperer - 2021

    Morgan McCallum

    Thank you so much for circling back with that! Very cool.

    0
  • 希瑟·隆美尔
    Community Moderator
    The Product Manager Whisperer - 2021

    Morgan McCallum

    I was just reminded that HTTP is being deprecated... have to move to webhooks. Here's what to do to set something up for Auto Private Comments:

    Set up the webhook athttps://YOURDOMAIN.zendesk.com/admin/apps-integrations/webhooks/webhooks

    endpoint
    https://YOURDOMAIN.zendesk.com/api/v2/tickets/{{ticket.id}}

    Set up a trigger with an Action at the bottom with Notify Webhook

    PUT

    {
    "ticket": {
    "comment": {
    "body": "TEST PRIVATE COMMENT",
    "public": false
    }
    }
    }

    The webhook test didn't go through for me, but when I set up the trigger it was good to go (?)

    Happy Zendesking!

    0
  • William Sedgwick

    希瑟·隆美尔

    bit of a dumb question but if i use the trigger body morgan has wrote:

    {
    "ticket": {
    "additional_collaborators": [ user id, "user email", { "name": "user name", "email": "user email" } ]
    }
    }

    how would i add multiple end users using this statement

    0
  • Korak

    Hi William,

    If you are using additional_collaborators property, you can provide an array of end user ids, their emails or objects with name and email property. The example below is going to add 3 new collaborators. You can also check the documentation:https://developer.zendesk.com/documentation/ticketing/managing-tickets/creating-and-updating-tickets/#setting-collaborators

    {
    "ticket": {
    "additional_collaborators": [
    562,
    "someone@example.com",
    {
    “名称”:“别人”,
    "email": "else@example.com"
    }
    ]
    }
    }

    Hope this helps.

    Cheers,
    Korak

    0
  • Tomer Ben-Arye

    I was able to achieve (almost) the same (but for 2+ users in the cc) with the Webhook target URL:

    描述:Use the API for tickets
    Method: PUT
    {
    "ticket": {
    "comment": {
    "body": "cc customer predefined emails when XYZ\nIMPORTANT:please verify the following emails in cc.\n tomer@glad.com willy.dont.com",
    "public": false
    },
    “email_ccs”:[{
    "action": "put",
    "user_email": "tomer@glad.com"
    },
    {
    "action": "put",
    "user_email": "willy.dont.com"
    }
    ]
    }
    }

    0
  • Dan Ratzlaff

    The webhook method works well for me adding a CC to a ticket on creation, but the newly-added CC does not automatically get the first notification that a ticket has been created. I believe it's the way the triggers get processed. I had to add a tag in the same trigger as the webhook, then add a new trigger that looks for Ticket->Updated and that tag present to send the requester and CC the notification that a ticket was created. It also removes the tag.

    1
  • Amy Gracer
    Community Moderator

    I'm new to webhooks, and therefore a bit lost by the comments in this conversation when not everything everyone tried worked.

    Has anyone put together a step by step for automatically cc'ing end users on tickets? It seems like this would be a feature lots of folks would want.

    Thank you so much to anyone who can assist!

    0
  • Zsa Trias
    Zendesk Customer Care

    Hello Amy,

    There isn't a trigger action to automatically add end-users as CCs/followers, but here's a workflow you may want to try:Workflow recipe: Notifying External Email Addresses

    0
  • Jeremy Sydney

    I need specifically to be able to add an End User as a CC on a ticket, because there are certain functions of the ticketing system that completely break if non-CC'd users communicate on tickets they're not CC'd on. For instance:

    We have a decision-maker subscribed to all ticket emails. She responds to a ticket without checking in the portal that it's closed. Her email generates a Follow-Up, her response becomes an Internal Note, and the Follow-Up is opened with the original ticket Requesters/CC's. We then have to manually add her as a CC. This is only one example of how the ticket flow doesn't really "care" about non-CC'd responders.

    She now has to check the portal for the status of the ticket before she communicates on it, which isn't the end of the world, but it adds overhead for her. Being able to add her as a CC would lower overhead for both her and us.

    0

Pleasesign into leave a comment.

Powered by Zendesk