CreateZendeskTicketv1.0.0
A command event that is available to any service that wants to create a Zendesk ticket
Properties
userId* :
ID of the user that the ticket is related to.
userEmail :
Email of the user that the ticket is related to. If not provided, the ticket will be assigned to the system.
title* :
The title of the ticket.
content* :
The tickets content. An object that can take multiple keys and value pair. The value must either be type of string, boolean, or an array.
tag* :
The tickets tag. This value is used by the agents in order to filter and group specific type of tickets depending on the tag value.
flowchart LR
l-Feedback_Service[Feedback Service]:::producer-->CreateZendeskTicket[CreateZendeskTicket]:::event
classDef event stroke:#2c368f,stroke-width: 4px;
classDef producer stroke:#75d7b6,stroke-width: 2px;
classDef consumer stroke:#818cf8,stroke-width: 2px;
CreateZendeskTicket[CreateZendeskTicket]:::event-->r-Zendesk_Service[Zendesk Service]:::consumer
click l-Feedback_Service href "/services/Feedback Service" "Go to Feedback Service" _self
click r-Zendesk_Service href "/services/Zendesk Service" "Go to Zendesk Service" _self
click CreateZendeskTicket href "/events/CreateZendeskTicket" "Go to CreateZendeskTicket" _self
CreateZendeskTicket Schema (yml)
openapi: 3.0.0
info:
version: "1.0.0"
title: CreateZendeskTicket
paths: {}
components:
schemas:
CreateZendeskTicket:
type: object
required:
- metadata
- data
properties:
data:
$ref: "#/components/schemas/Data"
metadata:
$ref: "#/components/schemas/Metadata"
Data:
type: object
required:
- userId
- title
- content
properties:
userId:
type: string
userEmail:
type: string
title:
type: string
content:
type: object
tag:
type: string
Metadata:
type: object
required:
- serviceFunction
- version
properties:
serviceFunction:
type: string
version:
type: string
Edit this pageLast updated on 2024/4/2