So rather than sending a JSON object of the service item fields, it sends an HTML table.
I don’t really think much else needs to be said about why this is frustrating. Can this placeholder send a JSON object? Currently I have to manually build a JSON object using the individual fields. It would save me a lot of time setting up new integrations if I didn’t have to do this tedious task.
New Idea
Workflow Automator {{ticket.service_item_fields}} sends an HTML Table instead of JSON
+14- Top Contributor ⭐
So rather than sending a JSON object of the service item fields, it sends an HTML table.
I don’t really think much else needs to be said about why this is frustrating. Can this placeholder send a JSON object? Currently I have to manually build a JSON object using the individual fields. It would save me a lot of time setting up new integrations if I didn’t have to do this tedious task.
I guess you use this API end point https://api.freshservice.com/v2/#update_req_items_of_sr to get all fields?
+14- Top Contributor ⭐
This is about a webhook so the data is sent on events in the system.
Yes, but to get the fields for from a service item you can do a GET to the endpoint and then you get the fields as a JSON object.
It’s a workaround.
They could maybe add a new placeholder but then this need more traction >10 votes
I already have a thousand work around for all the caveats of the automation, this is the most annoying, that's why I'm in the feature request forum with a feature request.
Join the Community
Already have an account? Login
Welcome back to Freshworks Community
No account yet? Create an account
Social Login
Login for Freshworks Employees Login with LinkedInor sign up below
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.