Create Ticket Form in Zendesk
A documented Zendesk operation that changes something in your account. Describe the outcome you want in plain words — HumDay writes the program, proves it, and runs it.
What this operation does
Create Ticket Form
- POSTChanges data · Ticket Forms
{subdomain}.{domain}.com/api/v2/ticket_forms
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which Zendesk operations the program may use, and this is one of them.
- You approve access. Because this one changes data, it cannot run until you have explicitly granted it.
Other Zendesk operations
- Record a New Skip for the Current UserPOST · changes data
- Create Ticket or Voicemail TicketPOST · changes data
- Create Ticket from TweetPOST · changes data
- Create TicketPOST · changes data
- Create Task List TemplatePOST · changes data
- Create Task ListPOST · changes data
- Request User CreatePOST · changes data
- Create Or Update UserPOST · changes data
Questions
- Can HumDay create ticket form in Zendesk?
- Yes. This operation is published in Zendesk's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Will this change my Zendesk data?
- Yes — this is a POST operation, so it changes something in Zendesk. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Zendesk account.
Where this came from
Read from the API description Zendesk publishes themselves at developer.zendesk.com/zendesk/oas.yaml. The description above is the provider’s own wording, not ours.