Using placeholders

Return to top

61 Comments

  • Scott Davis

    currently,

    {{ticket.url}} does not render as a clickable URL in email notifications. is there a way to do this?

    0
  • Beto
    Zendesk Customer Care

    Hi there Scott!

    This happens sometimes because the {{ticket.url}} placeholder does not include "http://" or "https://" as you can see on our Placeholder Reference article. This might affect if the url is clickable.

    The easiest solution is to use the {{ticket.link}} placeholder, which does include this, or add the missing section yourself, like this:
    http://{{ticket.url}}
    https://{{ticket.url}}

    I hope this helps!

    1
  • Andy M

    I've tried every variation of trying to get anything in the organization to come back and its always blank

    {{custom_fields.custom_cust_id}}},
    {{ticket.organization.name}}
    {{ticket.requester.organization.name}}
    {{ticket.requester.organization.external_id}}
    {{ticket.requester.org..custom_cust_id}}
    {{ticket.requester.organization.custom_fields..custom_cust_id}}
    {{ticket.requester.organization.custom_cust_id}}

    0
  • Dave Dyson

    Hi Andy,

    Where are you attempting to use these? I created a macro in my test account that adds a comment including these two placeholders:

    {{ticket.organization.name}}
    {{ticket.requester.organization.name}}

    If the ticket requester has an associated Organization, the placeholders resolve and display the organization name. I also added these placeholders to the notification text box in my "Notify requesters and CCs of comment update" trigger, and they worked there as well. I think your custom field placeholders above should also work, so long as you're substituting the field ID into the placeholder as instructed in the documentation above. 

    If you're still not able to get these to work, I'd suggest chatting with our support team (Option 1 here: Contacting Zendesk Customer Support), so they can help you troubleshoot.

    0
  • Conor Quarry

    Hi,

    Is it possible to create custom Zendesk Placeholders within our Macros, which can then be updated through the API? I'm noticing no API call I make, despite success, changes the field value within, ie, I want to add {{iban}} and {{phone_number}}.

    0
  • Karyn Close

    I'm not able to get this placeholder to work in a macro. I've tried substituting the key name for the ID as well and neither work. The Org Custom field (text) is correct and has data. The Org is also associated with the requester. Logically, it should work but does not.

    {{ticket.organization.custom_fields.<key_name>}}

    0
  • Arkadiusz Szafraniec

    Hi Everyone!

    Does {{ticket.ticket_field_<field ID number>}}  works with a text field? 
    I've tried on macro and it didn't work. Value in a comment is always blank.

    0
  • Diogo Maciel
    Zendesk Customer Care
    Hi Arkadiusz! Unfortunately text fields don't work on macros. For macros, dropdown fields are the preferred option.
     
    I encourage you to create a new post in the General Product Feedback topic in our community to engage with other users who have similar needs and discuss possible workarounds. Conversations with a high level of engagement ultimately get flagged for product managers to review when they go through roadmap planning.
     
    Specific examples, details about impact, and how you currently handle things are helpful for our product teams to understand the full scope of the need when working on solutions. You may also want to review the Product feedback guidelines and how to write an effective feedback post [https://support.zendesk.com/hc/en-us/community/posts/360004391547-Product-feedback-guidelines-how-to-write-a-good-feedback-post].
     
    We truly value customer feedback and your voice and votes in the forums help influence future Zendesk functionality.
     
    0
  • Arkadiusz Szafraniec

    Hi Diogo, 
    thank you for the answer. To be clear, text fields doesn't work only for macros? Did they work for automatic notifications via triggers and automations?

    0
  • Diogo Maciel
    Zendesk Customer Care
    Hi Arkadiusz! I have just tested this in my test account and with a text field in a macro and it worked using Agent Workspace. For us to investigate further it would be better to serve you via messaging where we can get details of your account and the fields and macros involved. Please check below how to contact us via your Support interface. Thank you!

    https://support.zendesk.com/hc/en-us/articles/4408843597850-Contacting-Zendesk-Customer-Support
    0
  • Jose Mª

    Hi,

    I am using a drop-down control.
    When using the placeholder: ticket.ticket_field_option_title_id, I see that I am getting the display value and not the internal label value.

    How can I get the internal label, or is it not possible?

    Regards

    0
  • Diogo Maciel
    Zendesk Customer Care
    Hi Jose! I am sorry, but I am not clear what you mean differentiating "internal label value" and "display value". Could you try contacting us in support via the instructions below so we can have a better look at the account and your flow? Thank you!

    https://support.zendesk.com/hc/en-us/articles/4408843597850-Contacting-Zendesk-Customer-Support
    0
  • Jose Mª

    Hi Diogo,

    I am referring to the values and the tags of the field values:

     

    1: is the value the customer sees

    2: is the tag, the internal value of the field value

    Regards.

    0
  • Diogo Maciel
    Zendesk Customer Care
    Hi Jose!

    Ah I see, thank you for clarifying. Yes, unfortunately placeholders will only display the value of the field and not the associated tag. The tag present in dropdown fields' values serve mainly to have a referenceable value internally for things like searches, viewsa and reports. I am sorry for the inconvenience.
    0
  • Jose Mª

    Thanks, Diogo!

    0
  • Sydney Neubauer

    Is there a placeholder for the current users custom field? There is "ticket.requester.custom_fields.<key_name>" but this pulls in the requester's custom field and not the current User making the comment.

    0
  • Sabra
    Zendesk Customer Care

    Hey Sydney! You can use the following placeholder format to pull the current user custom user field information:

    {{current_user.custom_fields.<key_name>}}

    For drop-down custom user fields, you'll want to use this format:

    {{current_user.custom_fields.<field_key>.title}}
    2
  • mccabe.tonna
    Community Moderator

    the checkbox logic should actually be swapped.

    {% if ticket.ticket_field_<insert field_id here> contains 0 %}
    checkbox is unchecked
    {% else %}
    checkbox is checked
    {% endif %}

    should actually be

    {% if ticket.ticket_field_<insert field_id here> contains 1 %}
    checkbox is checked
    {% else %}
    checkbox is unchecked (or null)
    {% endif %}

    reason: when a checkbox is not visible on a form; it returns null value. This accounts for explicitly checked boxes

    1
  • Dave Dyson
    Thanks McCabe, I've alerted our docs team. Good catch!
    0
  • Konstantin

    @Administrador and Diogo Maciel,

    It is possible to list the "tag" value (natively) for drop-down options, by utilizing " ticket.ticket_field_id ". To clarify, for drop-down options, this is the behavior:

    • "ticket.ticket_field_id" displays the Tag associated with the field option
    • "ticket.ticket_field_option_title_id" displays the Label/Name associated with the field option

    This is not true for all Field types, but it is possible for single-select drop-down fields.

    ~Konstantin

    4
  • Marc Iacobino

    Hello, what is the correct format for the "phone" placeholder? For example, for as French number such as ... (+33) 12 45 78 78

    0
  • Joyce
    Zendesk Customer Care
    Hey Marc,
     
    Are you looking for the placeholder to use to pull the phone number value on the ticket requester's user field? If so, you can use the placeholder {{ticket.requester.phone}},  which pulls the ticket requester's phone number on file. Check our Zendesk Support placeholders reference for more information.
     
    If it is about the acceptable phone number format that you are inquiring about, phone numbers should be formatted with the internationally standardized E.164 format. E.164 numbers can have a maximum of fifteen digits and are usually written as follows: [+][country code][subscriber number including area code].
    1
  • Rudolph Beaton
    Zendesk Luminary

    Shoutout to Konstantin for that perfect solution! Exactly what I needed. That info should be added to the article, Anton de Young / Joyce

    1
  • Jeff Killian

    Hi Joyce,
    I am trying to use a custom user field in a macro but the format is coming back reading:

    2022-01-15 00:00:00 +0000

    The data in the customer profile shows "January 15, 2022" which matches the format I want to use in my Macro.  Can you help me solve this please?   

    0
  • Dane
    Zendesk Engineering
    Hi Jeff,
     
    If you can share to use the placeholder that you are using, maybe we can determine what could be causing this behavior. 
    0
  • Amit Chinchane

    Is there any place holder like  {{user_email}} which can display the user email id on the help center page.

    For example:

    {{#if signed_in}}
          <div class="user-info dropdown">
            <button class="dropdown-toggle" aria-haspopup="true">
              {{user_name}}

     

    This show the full name of the user who is logged in on the help centre

    0
  • Mike DR
    Zendesk Customer Care
    Hey Chinchane,
     
    I see you have an open ticket for this, will reach out to you there!
    0
  • Chin Sin

    Hi, is it possible to use the place holder in the request body of the webhook?

    Background:

    I am using webhook to trigger an update to the ticket to populate a custom ticket field with the requester's external_id.

    API Request Body

    {
        "ticket": {
            "custom_fields": [
                {
                    "id": 8706713219609,
                    "value": "{{ticket.requester.id}}"
                }
            ]
        }
    }

    Result

    The ticket field will be updated with the text {{ticket.requester.id}} instead of the value.

    If I did not include the opening and closing quotes, I get the following error.

    {
        "error": "Unprocessable Entity",
        "message": "Server could not parse JSON"
    }

    0
  • Tipene Hughes
    Zendesk Developer Advocacy

    Hi Chin Sin,

    Placeholders cannot be used to populate custom ticket fields, unfortunately. In addition, we advise against using triggers and webhooks to update tickets using the API as this can potentially lead to race conditions which may result in unexpected behavior. Here’s an article which goes in to more detail:

    

https://support.zendesk.com/hc/en-us/articles/4408882855578-Can-I-use-a-trigger-and-a-webhook-to-update-tickets-

    One possible way you could achieve the same result is using a background ZAF app that makes a PUT request to the tickets API in response to an event. You can find out more about the apps framework here:

    https://developer.zendesk.com/documentation/apps/app-developer-guide/using-the-apps-framework/

    I hope this helps! Feel free to reach out with any questions.

    Tipene

    Edit: See following comment for clarification around testing custom fields and placeholders

    0
  • Chin Sin

    Hi Tipene Hughes,

    It seems that the test webhook does not work for placeholder but the placeholder works with the actual trigger + webhook.

    The solution was actually proposed by Zendesk technical consultant due to the limitation that no custom field or tags can be included in the tickets created via messaging.

    For the race conditions, we are only using it when ticket is created and if the custom field is empty.

    Thank you.

    CS

    0

Please sign in to leave a comment.

Powered by Zendesk