org.apache.nifinifi-zendesk-nar2.1.0org.apache.nifinifi-standard-shared-nar2.1.02.0.0rel/nifi-2.1.0main1org.apache.nifi.processors.zendesk.GetZendeskPROCESSORIncrementally fetches data from Zendesk API.zendeskweb-client-service-providerWeb Client Service ProviderController service for HTTP client operations.org.apache.nifi.web.client.provider.api.WebClientServiceProviderorg.apache.nifinifi-standard-services-api-nar2.1.0truefalsefalseNONEfalsefalsezendesk-subdomainSubdomain NameName of the Zendesk subdomain.truefalsetrueFLOWFILE_ATTRIBUTESfalsefalsezendesk-userUser NameLogin user to Zendesk subdomain.truefalsetrueFLOWFILE_ATTRIBUTESfalsefalsezendesk-authentication-type-nameAuthentication TypeType of authentication to Zendesk API.PasswordpasswordPassword of Zendesk login user.TokentokenAuthentication token generated in Zendesk Admin menu for API access.truefalsefalseNONEfalsefalsezendesk-authentication-value-nameAuthentication CredentialPassword or authentication token for Zendesk login user.truetruetrueFLOWFILE_ATTRIBUTESfalsefalsezendesk-export-methodExport MethodMethod for incremental export.Cursor BasedcursorIn cursor-based incremental exports, each page of results includes an "after" cursor pointer to use as the starting cursor for the next page of results.Time BasedtimeIn time-based incremental exports, each page of results includes an end time to use as the start time for the next page of results.truefalsefalseNONEfalsefalsezendesk-resourceResourceThe particular Zendesk resource which is meant to be exported.Tickets/api/v2/incremental/ticketsTickets are the means through which end users (customers) communicate with agents in Zendesk Support.Ticket Events/api/v2/incremental/ticket_eventsStream of changes that occurred on tickets. Each event is tied to an update on a ticket and contains all the fields that were updated in that change.Ticket Metric Events/api/v2/incremental/ticket_metric_eventsTicket metric events API can be used to track reply times, agent work times, and requester wait times.Users/api/v2/incremental/usersZendesk Support has three types of users: end users (customers), agents, and administrators.Organizations/api/v2/incremental/organizationsJust as agents can be segmented into groups in Zendesk Support, customers (end-users) can be segmented into organizations.Articles/api/v2/help_center/incremental/articlesArticles are content items such as help topics or tech notes contained in sections.NPS - Responses/api/v2/nps/incremental/responsesWhen a recipient responds to an NPS survey, their rating, comment, and last survey date are captured.NPS - Recipients/api/v2/nps/incremental/recipientsEvery NPS survey is delivered to one or multiple recipients. For most businesses that use Zendesk Support, the recipients are customers. Agents and admins will never receive surveys.truefalsefalseNONEfalsefalsezendesk-query-start-timestampQuery Start TimestampInitial timestamp to query Zendesk API from in Unix timestamp seconds format.truefalsetrueFLOWFILE_ATTRIBUTESfalsefalsesuccessFor FlowFiles created as a result of a successful HTTP request.falserecord.countThe number of records fetched by the processor.truetrue20 sec30 secWARNPaging cursor for Zendesk API is stored. Cursor is updated after each successful request.CLUSTERINPUT_FORBIDDENTIMER_DRIVEN1 min1org.apache.nifi.processors.zendesk.PutZendeskTicketPROCESSORCreate Zendesk tickets using the Zendesk API.zendesk, ticketweb-client-service-providerWeb Client Service ProviderController service for HTTP client operations.org.apache.nifi.web.client.provider.api.WebClientServiceProviderorg.apache.nifinifi-standard-services-api-nar2.1.0truefalsefalseNONEfalsefalsezendesk-subdomainSubdomain NameName of the Zendesk subdomain.truefalsetrueFLOWFILE_ATTRIBUTESfalsefalsezendesk-userUser NameLogin user to Zendesk subdomain.truefalsetrueFLOWFILE_ATTRIBUTESfalsefalsezendesk-authentication-type-nameAuthentication TypeType of authentication to Zendesk API.PasswordpasswordPassword of Zendesk login user.TokentokenAuthentication token generated in Zendesk Admin menu for API access.truefalsefalseNONEfalsefalsezendesk-authentication-value-nameAuthentication CredentialPassword or authentication token for Zendesk login user.truetruetrueFLOWFILE_ATTRIBUTESfalsefalsezendesk-record-readerRecord ReaderSpecifies the Controller Service to use for parsing incoming data and determining the data's schema.org.apache.nifi.serialization.RecordReaderFactoryorg.apache.nifinifi-standard-services-api-nar2.1.0falsefalsefalseNONEfalsefalsezendesk-comment-bodyComment BodyThe content or the path to the comment body in the incoming record.truefalsetrueFLOWFILE_ATTRIBUTESfalsefalsezendesk-record-readerRecord Readerzendesk-subjectSubjectThe content or the path to the subject in the incoming record.falsefalsetrueFLOWFILE_ATTRIBUTESfalsefalsezendesk-record-readerRecord Readerzendesk-priorityPriorityThe content or the path to the priority in the incoming record.falsefalsetrueFLOWFILE_ATTRIBUTESfalsefalsezendesk-record-readerRecord Readerzendesk-typeTypeThe content or the path to the type in the incoming record.falsefalsetrueFLOWFILE_ATTRIBUTESfalsefalsezendesk-record-readerRecord ReaderThe 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.FLOWFILE_ATTRIBUTESsuccessFor FlowFiles created as a result of a successful HTTP request.falsefailureA FlowFile is routed to this relationship if the operation failed and retrying the operation will also fail, such as an invalid data or schema.falserecord.countThe number of records processed.error.codeThe error code of from the response.error.messageThe error message of from the response.