Christian Freitag

Hey all,

 

Was wondering if this workaround is still functional?

I've set this up recently to get around the Webform having no Name field - at present, the Widget captures a Default Name which then becomes the Requester id, which is great, but any users submitting a request through the Webform have no Name option (as there is no default Name field here).

I've added a Ticket field titled 'Name' into the Webform, with the notion of disabling the Default Name field from the Widget and just using the custom field I've created - and was hoping I could use this workaround to then ensure any input in the custom field then triggers updating the Requester name to match.

I set the target for the API as: https:// {{subdomain}}.zendesk.com/api/v2/users/{{ticket.requester.id}}.json?user[name]={{ticket.ticket_(field name)_(field id)}}

- is this correct? I have the 'field name' as the name of the custom field, and 'field id' as the unique ticket field number.

Have also set the trigger / automation up exactly as outlined & screenshotted in the start of the thread, however any webform submission keeps defaulting the requester to the email name, and not the input 'Name' data.

Testing the extension also results in the fail others have mentioned.

Any suggestion on this? Feel like I'm missing something obvious!

Thanks! :)

 

- Christian