Salesforce to zendesk integration without Managed package

When I authenticate my org from zendesk to salesforce, does zendesk automatically creates its own connected app?

Zendesk to salesforce connection error:- There was a problem connecting to your Salesforce account. Review your permissions to ensure you have modify access to Salesforce objects.


Which all objects we need permission and which all permissions, Also, do we need to provide Record type access as well and what abt FLS?

HeyO @hardik11 - It should be possible to connect our SFDC integration without installing a managed package. As mentioned in our installation documentation, the managed package installs various components used by the Ticket View feature, whereas it sounds like you're trying to use our Data Sync feature

The permissions required for this integration are listed in https://support.zendesk.com/hc/en-us/articles/4408843355290

Please feel free to contact our support team if you have further questions on this topic

Thanks for the response @dwight, It works for me now.

I was also trying to implement it using the API integrations, where I found the correct API to implement.
 
My question is about the authentication part, two ways one is basic authentication where we add the username/token and for the password, we create an API token. 
Question 1:- Is der any limitation or how long does the API token expire?
Question 2:- Do we have an article where I can authenticate Zendesk using clientid and secret. I created an OAuth app and got the clientid and secret but was unable to pull it from Postman. Please suggest.
Access token URL:- https://{domain}.zendesk.com/api/v2/oauth/token

See the image below:- 

There are several different kinds of tokens that can be used to authenticate API requests in Zendesk: 

1. API token - this can be paired with any user's email address to authenticate requests on behalf of that user. It will exist until it is manually deleted. 
   
   
2. OAuth token - this token is generated for a specific OAuth client and user. It can be manually revoked, or would cease to function if the OAuth client was removed. If the user in question is downgraded from agent/admin to end-user, their OAuth tokens are automatically revoked.

Neither of these tokens can be automatically expired - they exist until revoked (whether manually or as a result of downgrade/deletion).

Here is an article on how to authenticate API requests to Zendesk: https://developer.zendesk.com/api-reference/introduction/security-and-auth/ 

and another specifically on how to implement OAuth: https://support.zendesk.com/hc/en-us/articles/4408845965210 

If you run into issues making requests as documented therein, I recommend contacting our support team for help.

Thanks @dwight for sharing all the URL's, I will go through them.

One more question I had is that in the following documentation:- https://developer.zendesk.com/api-reference/ticketing/users/users/ and will be using the endpoint:-  

• POST /api/v2/users/create_or_update_many



Here what is the 'external_id' here, from which Field of user it is comparing with external_id, so that I will se sending from salesforce to match it.

Also, if this API runs a batch job in Zendesk, when will I update my Zendesk userid in salesforce synchronously as I need to pass the external_id from salesforce to Zendesk in API POST Body params.

Hi @hardik13 - the external_id field being used by that endpoint is the native user property documented here: https://developer.zendesk.com/api-reference/ticketing/users/users/ 

The create_or_update_many endpoint returns a job_status result: 

https://developer.zendesk.com/api-reference/ticketing/ticket-management/job_statuses/#show-job-status 

This response should include the Zendesk ID of the user that was created/updated

Yea, I got all these but I need to call another api for job status.

I wanted a synchronous process using api with around 200 users per call which I think the api is not supporting. (If available please provide). - As I need to update then returned userId in the same transaction to salesforce as the record can be updated as well just after creation.

Need to check if Streaming api passes all security measures.

@hardik13 - maximum for our APIs is 100 users per call. I recommend batching in 100-user sets. I believe that all of our bulk endpoints (create many/update many/create_or_update_many/destroy_many) return job-status links, so you're on the right track. 

This thread may not be the best place to have a back-and-forth discussion like : please contact our support team if you need more assistance.