Zendesk Trigger node error DeprecatedTargetType

Describe the issue/error/question

Get error when running Zendesk Trigger node on my newly setup n8n instance (running in Azure). The api credentials work if I use a Zendesk node to query tickets.
Also have a cloud n8n instance with Zendesk Trigger node which is displaying the same problem, but was working a few days ago.
Created a new api token in zendesk for the Azure instance in case this was the problem.
My zendesk instance is a trial instance, so not used by anyone else.

Also noticed this message in Zendesk → API → Target Failures:
“In February 2022, HTTP targets will no longer be supported. Active HTTP targets will be automatically converted to webhooks after this time, but inactive HTTP targets will not be converted.”

What is the error message (if any)?

ERROR RESPONSE
NodeApiError: Forbidden - perhaps check your credentials?
    at Object.zendeskApiRequest (/home/azureuser/.nvm/versions/node/v17.6.0/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Zendesk/GenericFunctions.js:43:15)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async Object.create (/home/azureuser/.nvm/versions/node/v17.6.0/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Zendesk/ZendeskTrigger.node.js:361:38)
    at async ActiveWebhooks.add (/home/azureuser/.nvm/versions/node/v17.6.0/lib/node_modules/n8n/node_modules/n8n-core/dist/src/ActiveWebhooks.js:32:17)
    at async TestWebhooks.needsWebhookData (/home/azureuser/.nvm/versions/node/v17.6.0/lib/node_modules/n8n/dist/src/TestWebhooks.js:97:17)
    at async /home/azureuser/.nvm/versions/node/v17.6.0/lib/node_modules/n8n/dist/src/Server.js:526:38
    at async /home/azureuser/.nvm/versions/node/v17.6.0/lib/node_modules/n8n/dist/src/ResponseHelper.js:89:26 {
  cause: Error: Request failed with status code 403
      at createError (/home/azureuser/.nvm/versions/node/v17.6.0/lib/node_modules/n8n/node_modules/axios/lib/core/createError.js:16:15)
      at settle (/home/azureuser/.nvm/versions/node/v17.6.0/lib/node_modules/n8n/node_modules/axios/lib/core/settle.js:17:12)
      at IncomingMessage.handleStreamEnd (/home/azureuser/.nvm/versions/node/v17.6.0/lib/node_modules/n8n/node_modules/axios/lib/adapters/http.js:269:11)
      at IncomingMessage.emit (node:events:539:35)
      at IncomingMessage.emit (node:domain:475:12)
      at endReadableNT (node:internal/streams/readable:1342:12)
      at processTicksAndRejections (node:internal/process/task_queues:83:21) {
    config: undefined,
    request: undefined,
    response: {
      status: 403,
      statusText: 'Forbidden',
      headers: [Object],
      config: [Object],
      request: [ClientRequest],
      data: [Object]
    },
    isAxiosError: true,
    toJSON: [Function: toJSON],
    cause: {},
    error: {
      error: 'DeprecatedTargetType',
      description: 'Deprecated target type'
    },
    statusCode: 403,
    options: {
      url: 'https://coremonthelp.zendesk.com/api/v2/targets.json',
      method: 'post',
      data: '{"target":{"title":"n8n webhook","type":"http_target","target_url":"https://n8n-tdsmsdn.northeurope.cloudapp.azure.com:5678/webhook-test/85060ea7-23a8-4545-8f54-31544ac63045/webhook","method":"POST","active":true,"content_type":"application/json"}}',
      headers: [Object],
      transformRequest: undefined,
      transformResponse: undefined,
      paramsSerializer: undefined,
      timeout: 300000,
      adapter: undefined,
      xsrfCookieName: 'XSRF-TOKEN',
      xsrfHeaderName: 'X-XSRF-TOKEN',
      maxContentLength: -1,
      maxBodyLength: -1,
      validateStatus: undefined,
      transitional: [Object],
      'axios-retry': [Object],
      httpsAgent: undefined
    }
  },
  node: {
    parameters: {
      authentication: 'apiToken',
      service: 'support',
      options: [Object],
      conditions: [Object]
    },
    name: 'Zendesk Trigger',
    type: 'n8n-nodes-base.zendeskTrigger',
    typeVersion: 1,
    position: [ 460, 300 ],
    webhookId: '85060ea7-23a8-4545-8f54-31544ac63045',
    credentials: { zendeskApi: [Object] }
  },
  timestamp: 1645975914864,
  httpCode: '403',
  description: 'DeprecatedTargetType'
}

Please share the workflow

Share the output returned by the last node

No output returned, just error.

Information on your n8n setup

  • **n8n version:**0.164.1
  • **Database you’re using (default: SQLite):**default
  • **Running n8n with the execution process [own(default), main]:**default
  • **Running n8n via [Docker, npm, n8n.cloud, desktop app]:**npm & n8n.cloud

Hey @timstockford,

That is odd it looks like the webhook is being sent as an HTTPS url so I would have thought it would work.

We will need to check to see if the API endpoint has checked, thanks for reporting this one.

2 Likes

Hey @timstockford,

I have had a quick look and it looks like we will have to redo a chunk of the trigger node to move over to webhooks instead.

I have created an internal ticket for this one as it won’t be a 5 minute job so that we can set the priority and get someone on it.

For now as a temporary solution what you can do is in n8n create a workflow that uses a webhook and set the Method to post then copy the URL it gives you.

In the Zendesk Admin Center go to Apps and Integrations > Webhooks, This will ask you for your End Point URL which is the value from the n8n webhook and set it to Post.

Hit Save at the bottom and it will guide you through configuring a rule to send data to the webhook.

How to add your webhook to a Support trigger or automation

Open Support Admin area in a new window 
Navigate to the business rules section and click Triggers or Automations
Select a trigger or automation, or create a new one
Under Actions, select Notify active webhooks and choose your webhook
Save the trigger or automation
Return to this window to finish setup

While this isn’t perfect it will at least get you up and running.

2 Likes

Thank you. I will try the workaround.

1 Like

Hi, have the same issue, would be a fix in N8n available ?

Hey @Stefan,

Nothing yet but it is still possible using the workaround above.

Morning,

This issue should be resolved on any version of n8n since 0.173.0

1 Like