Zendesk Support links: API Guide, Authentication
Note: You may be familiar with this as a Zendesk connection. It was renamed to Zendesk Support to distinguish it from the new Zendesk Sell connection.
1. Set up a Zendesk Support connection
Start establishing a connection to Zendesk Support in either of the following ways:
- From the Resources menu, select Connections. Then, click + Create connection at the top right.
– or – - While working in a new or existing integration, you can add an application to a flow by clicking a source or destination. In the resulting Application list, select Zendesk Support. Then, click the plus sign (+) to the right of Connection to edit the settings.
2. Provide required Zendesk Support settings
The Create connection dialog then asks you to name the new connection and supply standard authentication details.
Name (required): Provide a clear and distinguishable Name as soon as the connection is created. Throughout integrator.io imports and exports, you will have the option to choose this new connection, and a unique identifier will prove helpful later when selecting among a list of connections that you’ve created.
Application (read-only): the default value is Zendesk Support.
Authentication type (required): Select Basic.
Subdomain (required): Enter the unique portion of your zendesk.com domain (the URL where you log in to your Zendesk portal). The subdomain displays in the browser’s URL field. For example, if your portal is found at https://hugesuccess.zendesk.com, then enter hugesuccess for the subdomain.
Username (required): Enter the your Zendesk Support account email address.
Password (required): Enter the password for this Zendesk Support account.
3. Advanced
Borrow concurrency from (optional): Select another connection from the list....
Concurrency level (optional): Up to 25 allowed....
4. Save and test
Once you have configured the Anaplan connection, you have a few options for continuing:
- Save – click this button to test the connection, commit the new connection so that it will be available to all integrations for your account
- Save & close – click to test and save the connection and exit the Create connection pane
- Cancel – click to exit without saving any new changes
- Test connection – click this button to verify that your new connection is free of errors
When you test or save the connection, it is verified before continuing.
The new connection is now successfully added to your account. It will be applied to the current source or destination app, if you created it within a flow. Otherwise, you may proceed to register the connection with an integration.
Comments
Not sure if this is the correct place to ask this, but: Will the Zendesk Support connector support the Custom Objects API in the near future? See https://developer.zendesk.com/api-reference/custom-data/custom-objects/custom_objects for more info.
Notice: The old Custom Objects API (now called "Legacy Custom Objects") was not part of the same API namespace as the other endpoints, so it somewhat made sense to exclude that one, but the new Custom Objects API is now an integrated part of the REST API (the endpoints are prefixed with "/api/v2/custom_objects", comparable to "/api/v2/tickets", "/api/v2/organizations", etc), so it would make sense to include it in the available APIs under the Zendesk Support connector.
We can of course use the generic REST connector, but that will count against the number of endpoint apps we have available.
Thanks in advance.
Hi, Cristoffer. Sorry for the delay. I have received confirmation from our Connectivity engineering team that we'll be adding Custom Objects API support in an upcoming release, and your request here helps us prioritize that effort – thanks. The updated connector will be announced in the release notes, and I'll try to update this thread at that time.
Stephen Brandt Thanks a lot Stephen, that sounds great. Will it support all endpoints under the Custom Objects API, including the "Bulk Jobs" (/api/v2/custom_objects/{custom_object_key}/jobs) endpoint?
Sorry for the delay, Christoffer. We currently do not support bulk endpoints, though they're on the roadmap. Before committing, our engineering team needs a little more time to assess the feasibility of adding custom bulk endpoints. I'll let you know when I hear back, if they haven't replied here already.
Please sign in to leave a comment.