PutZendeskTicket

Description:

Create Zendesk tickets using the Zendesk API.

Tags:

zendesk, ticket

Properties:

In the list below, the names of required properties appear in bold. Any other properties (not in bold) are considered optional. The table also indicates any default values, and whether a property supports the NiFi Expression Language.

Display Name	API Name	Allowable Values	Description
Web Client Service Provider	web-client-service-provider	Controller Service API: WebClientServiceProvider Implementation: StandardWebClientServiceProvider	Controller service for HTTP client operations.
Subdomain Name	zendesk-subdomain		Name of the Zendesk subdomain. Supports Expression Language: true (will be evaluated using flow file attributes and variable registry)
User Name	zendesk-user		Login user to Zendesk subdomain. Supports Expression Language: true (will be evaluated using flow file attributes and variable registry)
Authentication Type	zendesk-authentication-type-name	Password Token	Type of authentication to Zendesk API.
Authentication Credential	zendesk-authentication-value-name		Password or authentication token for Zendesk login user. Sensitive Property: true Supports Expression Language: true (will be evaluated using flow file attributes and variable registry)
Record Reader	zendesk-record-reader	Controller Service API: RecordReaderFactory Implementations: GrokReader JsonTreeReader WindowsEventLogReader ReaderLookup ParquetReader CSVReader Syslog5424Reader ExcelReader CEFReader XMLReader ScriptedReader SyslogReader JsonPathReader AvroReader YamlTreeReader	Specifies the Controller Service to use for parsing incoming data and determining the data's schema.
Comment Body	zendesk-comment-body		The content or the path to the comment body in the incoming record. Supports Expression Language: true (will be evaluated using flow file attributes and variable registry) This Property is only considered if the [Record Reader] Property has a value specified.
Subject	zendesk-subject		The content or the path to the subject in the incoming record. Supports Expression Language: true (will be evaluated using flow file attributes and variable registry) This Property is only considered if the [Record Reader] Property has a value specified.
Priority	zendesk-priority		The content or the path to the priority in the incoming record. Supports Expression Language: true (will be evaluated using flow file attributes and variable registry) This Property is only considered if the [Record Reader] Property has a value specified.
Type	zendesk-type		The content or the path to the type in the incoming record. Supports Expression Language: true (will be evaluated using flow file attributes and variable registry) This Property is only considered if the [Record Reader] Property has a value specified.

Dynamic Properties:

Supports Sensitive Dynamic Properties: No

Dynamic Properties allow the user to specify both the name and value of a property.

Name	Value	Description
The path in the request object to add. The value needs be a valid JsonPointer.	The path in the incoming record to get the value from.	Additional property to be added to the Zendesk request object. Supports Expression Language: true (will be evaluated using flow file attributes and variable registry)

Relationships:

Name	Description
success	For FlowFiles created as a result of a successful HTTP request.
failure	A FlowFile is routed to this relationship if the operation failed and retrying the operation will also fail, such as an invalid data or schema.

Reads Attributes:

None specified.

Writes Attributes:

Name	Description
record.count	The number of records processed.
error.code	The error code of from the response.
error.message	The error message of from the response.

State management:

This component does not store state.

Restricted:

This component is not restricted.

System Resource Considerations:

None specified.