> For the complete documentation index, see [llms.txt](https://docs.nalpeiron.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nalpeiron.com/zentitle2-docs/ui-administration/integrations/salesforce/connecting-salesforce-to-zentitle.md).
# Connecting Salesforce to Zentitle
Connect the Salesforce integration sample to your Zentitle2 account by configuring the Z2NCred named credential, the Z2ECred external credential, and a new API client.
Having carried out the required user configuration steps to connect the Salesforce integration sample to Zentitle, we are now in a position to establish this connection.
Go to Salesforce Setup. In the quick find box, search for **Named Credentials.**
Click the **Named Credentials** link. On the next page, select the Named Credential named **Z2NCred:**
Follow this link and click the Edit button that appears at the top right of the new page
which will take you to the Edit page for the Z2NCred Named Credential.
At this stage, you are required to enter into Salesforce some details about your Zentitle2 account. In a separate browser window, login to Zentitle2. On the sidebar, go to **Administration>API Credentials**. On the **API Credentials** page, click the **Management API** tab to view the **Management API Details**:
Take a note of the following information:
* Tenant ID
* API URL
* OAuth URL
Keep this browser window open at the current page as we shall return to it shortly.
Go back to the **Edit** page for Z2NCred in SalesForce.
Ensure that the form is populated as shown above. Set the URL to be the API URL from your Zentitle Account. (i.e., ) and click **Save.**
Back on the Zentitle API edit page, go to the **Custom Headers** section and click the **New** button.
Under the Custom Headers section click Edit to change the N-TenantId, and replace the value with the Tenant ID found in the API Credentials page of your Zentitle Account and click **Save**.
Go back to the **Named Credentials** page and click on the **External Credential** tab. Click on the External Credential named **Z2ECred** to go to the page for this item.
In the **Actions** dropdown, click **Edit** to update the External Credential. This will take you to the edit page.
Set the **Identity Provider URL** to be the **OAuth URL** value found on the API Credentials page of your Zentitle Account, appended by /protocol/openid-connect/token and then click **Save.**
Under the Principals section of the Z2ECred page, if the **Admin Perms** principal has been created, click the **Actions** dropdown .png?alt=media\&token=2cdc5b1d-6272-48a1-ab8c-cae51291575f) and select **Edit.**
If this principal does not already exist, create a new Admin Perms principal. Either way ensure that it has been configured as follows:
Now return to the go to the **API Credentials page** of your Zentitle Account and click **Add API Client.**
Set a name (Client ID) of your choosing and click **Save**.
You will now be asked to save the **Client Secret** as shown. Please do so.
Back in the Salesforce Principal edit page, enter the name you used for the **Client ID**, copy the **Client Secret** from Zentitle2, enter it and click **Save**. This completes the setup of our Salesforce integration sample.
Finally, on the Z2ECred page, create a **custom header** configured identically to the one you created on the Z2NCred page.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.nalpeiron.com/zentitle2-docs/ui-administration/integrations/salesforce/connecting-salesforce-to-zentitle.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
.png?alt=media&token=29e33e37-14af-44ed-ac47-7a1b5613430a)
.png?alt=media&token=0834c774-3c9a-49a8-a600-30d4a7b51ad8)
.png?alt=media&token=1d801940-c30e-4815-913d-5d48eb3ef38a)
.png?alt=media&token=657de0a5-c8cc-48df-8029-937d7549f11f)
.png?alt=media&token=dab799a0-9b25-49af-ad3b-7db6cb738dd8)
.png?alt=media&token=052ed313-0a06-41d2-a609-0c67fba9a8a9)
.png?alt=media&token=73a15f1c-355c-473a-a3b1-0fc5886106c5)
.png?alt=media&token=6bbcab31-323d-4dea-8ca1-123c775a7a68)
.png?alt=media&token=f70f729a-0048-423d-9b95-f0cd352a067e)
.png?alt=media&token=dfd742a8-8548-45a5-8bdc-f40404f5e6e6)
.png?alt=media&token=a64cd0d4-e2a1-4485-976f-1fd136e1cfad)
.png?alt=media&token=5519767a-77a1-493a-9e7c-93748616b034)
.png?alt=media&token=fe97a17d-33eb-4444-802a-c5cd1adbb689)
.png?alt=media&token=11a76b50-9dff-46fb-a7d7-08e159fbb1dd)