Creating webhooks with the HTTP target Follow

Comments

18 comments

  • Avatar
    Ola Timpson

    I tried clicking on the 'Integrating with Slack' link in the examples, but it says I'm not authorised to view the page.  Is the example available elsewhere?

  • Avatar
    Jessie Schutz

    Hi Ola!

    It looks like that article has been archived. I'm going to follow up with our Docs team to find out what's going on!

  • Avatar
    Charles Nadeau

    It should work now. The post used to be part of a community topic about a beta feature. We archived the topic after the feature was released. I moved the post back into a public topic.

  • Avatar
    Jessie Schutz

    Thanks, Charles!

  • Avatar
    Rahulg

    Is there any way to remove signature from latest public comment data???

  • Avatar
    Dennis Lynn

    Hi Rahulg,

    Could you tell me a little more about your use-case here? I'd like to help, but I'm not sure what you're hoping to achieve. Thanks in advance!

  • Avatar
    Jehan (Edited )

    Incomplete documentation. No example for "Form Encoded" targets.

  • Avatar
    Nicole Relyea

    Thanks, Jehan. We'll let documentation know that this needs an update. 

  • Avatar
    Nathan Anderson

    Does anyone have an example for integrating with Asana?  I want to create an Asana task when a ticket is closed in Zendesk.

  • Avatar
    Nicole Relyea

    Hey Nathan - 

    It looks like Asana has an integration for creating tickets. I'm not sure whether it can be configured to create a task when a ticket is closed, but it does look like it can create a task when a new one is opened. 

  • Avatar
    Scott Russell

    Can someone explain how Target Failures are displayed? Is it the last trailing X days,  last X failure events, etc.? Thanks!

  • Avatar
    Kiran Madhav

    Hi Scott,

    Please follow below

    Admin --> Channels --> API --> Target Failures

     

    Here you can see all the target failure and reason.

    Thanks,

    Kiran.

  • Avatar
    Jessie Schutz

    Thanks for jumping in, Kiran!

  • Avatar
    Raoul de Grunt

    Hello,

    Can you please elaborate on the Basic Authentication option of the webhook? We have created a webhook to update a Zendesk ticket (to add a CC and custom field value) and we want to use a wildcard for the authentication user and the token for the password.

    Can I define "{{ticket.assignee.email}}\token" as username, with the token as the password?

    Thank you for answering

  • Avatar
    Jessie Schutz

    Hey Raoul!

    I don't actually know the answer to your question, but I'm going to check with some colleagues to see if I can find some info for you! Stand by!

  • Avatar
    Josh Rosenthal

    Hey Raoul!

    To step in and help Jessie on this one, you can't pass in that placeholder as a wildcard in your target/trigger workflow. It will pass over the placeholder string and not the value that would replace it in a ticket.

    That said, I also wanted to warn you that we don't recommend updating tickets using a target directly, as it's very likely you'll encounter conflicts when trying to update a ticket this way.

    I hope that clarifies that a little bit!

  • Avatar
    Raoul de Grunt

    Hello Jessie and Josh,

    Thanks for the feedback. For now we will use the trigger/webhook as we created it, with a fixed username.

    We are aware that using this method is not optimal and can lead to conflicts. The reason that we used this method is because it is not easy to achieve our desired behaviour via normal trigger actions. We believe we are safe, as we change a custom field value and add an email to the CC, which are both not used in any other trigger or automation.

    Just to give a sketch of our implemented behaviour: We have set the assignee to 2 fields: a custom field 'Last Worker' and add it to the CC. We do this, because we configure our system to unassign tickets after a period of assignee inactivity and an engineer can easily find back what they have been working on.

    If we were to do this in a trigger we would need to create a trigger per assignee, which means creating a trigger for every new support engineer. 

    FYI: We are looking into creating a script that will create a Zendesk agent and matching trigger, plus can delete a user and the matching trigger. Then we can get rid of this construction.

  • Avatar
    Jessie Schutz

    Thanks for sharing your use case, Raoul! It's a really interesting workflow. Even though placeholder token won't work for you, I'm glad you found something that works. :)

Please sign in to leave a comment.

Powered by Zendesk