---
schema_version: "1"
id: 7aea1c412059bb7cfe2a1355796fa5caa96ca07d866e65b32d9646304ac7b06a
title: Zendesk Connector
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/automate_flow_ref_third_party_zendesk.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.automate_flow_ref_third_party_zendesk.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 2e2b67da8be4a5797f8d7975479a7930ac71d31e48756844f2480f1bda516629
description: Connect to an external Zendesk account. Perform tasks like creating tickets or updating comments. Use Zendesk as a data source (trigger) or a data target (action).
products:
  - Flow Builder
  - Salesforce Platform
release: "264"
---
# Zendesk Connector

Connect to an external Zendesk account. Perform tasks like creating tickets or updating comments. Use Zendesk as a data source (trigger) or a data target (action).

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;"><a href="https://help.salesforce.com/s/articleView?id=platform.flow_ref_supported_editions.htm&amp;release=264.0.0&amp;type=5" title="Learn about the editions and user interfaces that support Flow Builder. Some Flow Builder features integrate with other Salesforce products that require additional licenses.">View supported editions.</a></td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">This feature requires the MuleSoft for Flow: Integration add-on. Exceptions are segment-triggered flows, activation-triggered flows, and broadcast flows, which don't require the MuleSoft for Flow: Integration add-on. <strong>Professional</strong> Edition requires the API access add-on. To purchase an add-on, contact your Salesforce account executive.</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">MuleSoft for Flow: Integration features used with Agentforce require the Foundations or Agentforce 1 edition. To purchase these editions, contact your Salesforce account executive.</td></tr></tbody></table>

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/images/icon_note.png)

Note You can edit or delete connections only in the Automation app.

## Connections

Connect to a source or target system by using its standard connection or an existing external named credential. You can connect to multiple systems within a flow and reuse each connection. You can create connections in the [Integrations tab](https://help.salesforce.com/s/articleView?id=platform.automate_ala_connections.htm&release=264.0.0&type=5 "The Integrations tab includes a list of all the connections for your org.") or in Flow Builder.

**Standard Connection**

This system uses Basic authentication.

Basic authentication enables the user to provide a username and password when logging in to an external system.

This system requires this credential information for its [connections](https://help.salesforce.com/s/articleView?id=platform.automate_ala_connections_create_connection.htm&release=264.0.0&type=5).

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d83972e109">FIELD</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d83972e112">DESCRIPTION</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="FIELD" class="slds-cell-wrap" style="vertical-align:top;" headers="d83972e109 ">Connection Name</td>

            <td data-label="DESCRIPTION" class="slds-cell-wrap" style="vertical-align:top;" headers="d83972e112 ">
              <p dir="ltr">Enter a unique connection name that helps you remember the details of this
                connection. Salesforce hides the credentials after you create the connection. Reuse
                connections as needed.</p>
              <p style="margin-bottom:0;" dir="ltr">Anyone with the Manage Integration Connections permission can see and use all
                connections in the org.</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="FIELD" class="slds-cell-wrap" style="vertical-align:top;" headers="d83972e109 ">Username</td>

            <td data-label="DESCRIPTION" class="slds-cell-wrap" style="vertical-align:top;" headers="d83972e112 ">
              <p style="margin-bottom:0;">Enter the username to use to authenticate the requests.</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="FIELD" class="slds-cell-wrap" style="vertical-align:top;" headers="d83972e109 ">Password</td>

            <td data-label="DESCRIPTION" class="slds-cell-wrap" style="vertical-align:top;" headers="d83972e112 ">
              <p style="margin-bottom:0;">Enter the password to use to authenticate the requests.</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="FIELD" class="slds-cell-wrap" style="vertical-align:top;" headers="d83972e109 ">URL</td>

            <td data-label="DESCRIPTION" class="slds-cell-wrap" style="vertical-align:top;" headers="d83972e112 ">
              <p style="margin-bottom:0;">Enter the URL of your instance.</p>
            </td>

          </tr>
        </tbody>
      </table>

**Named Credential Connection**

Select a pre-existing named credential from Setup to use for your external system connections.

Before connecting to your external system with a named credential, first create or use an existing authenticated [named credential and external credential that is enabled for your users.](https://help.salesforce.com/s/articleView?id=xcloud.nc_named_creds_and_ext_creds.htm&type=5&language=en_US)

To ensure a successful [connection](https://help.salesforce.com/s/articleView?id=platform.automate_ala_connections_create_connection.htm&release=264.0.0&type=5 "Select a named credential from Setup to use for your external system connections.") for use in a flow, use only one principal for each named credential.

- Use the same name for the named credential and its related objects, such as the external credential and external authentication identity providers. Labels for these objects can differ.
- Assign the user creating the connection the required user permission for the principal. Without this permission, the connection test fails and the connection remains inactive.

![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/images/icon_important.png)

Important

When you create a connection with an existing named credential, note these behaviors:

- Manage the named credential’s read-only details in Setup, not the Integrations tab. On the Integrations tab, you can only edit the connection's Connection Name and Description.
- Perform reconnections for the named credential in Setup. The Reconnect button isn’t visible on the Details page.
- Delete associated named credentials in Setup. Deleting a connection doesn't remove the credential.

![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/images/icon_important.png)

Important

To establish a Zendesk connection, note the following required values:

- In the Username field, enter `<username>/token`. Enter the word `token`, not the actual API token.
- The value entered in the Password field must be an API token. An API token is a unique string of characters used to authenticate API requests, ensuring secure access to Zendesk services. If you don't have an API token, you can obtain one from your Zendesk instance.

## Triggers

A trigger initiates the flow when a specified event occurs. Triggers are important for automating business processes because they react to real-time data changes in various systems. For more information about triggers, refer to [Create a Flow with a Connector as a Trigger](https://help.salesforce.com/s/articleView?id=platform.automate_build_flow_esct_third_party_as_trigger.htm&release=264.0.0&type=5 "To trigger a flow when a change happens in a third-party system, use an External System Change-Triggered flow. A poller checks for new records on a schedule and creates flow interviews when records are found. Create the flow from scratch or from a template.").

These Zendesk triggers are available in Flow Builder.

- On Create Comment On Ticket
- On Create Organization
- On Create Ticket
- On Create User
- On New Or Updated Record Trigger
- On New Record Trigger
- On New Or Update Organization
- On New Or Update Ticket
- On New Or Update User

## Actions

An action performs a specific task or operation within a target system. Use actions to automate tasks across different systems without manual intervention, based on conditions set in the flow. For more information about actions, refer to [Create a Flow with a Connector as an Action](https://help.salesforce.com/s/articleView?id=platform.automate_build_flow_esct_third_party_as_action.htm&release=264.0.0&type=5 "To integrate your flow with an external system, add MuleSoft for Flow: Integration connectors as actions to all existing flow types. You can add connectors to flows that trigger external system changes, records, schedules, Data Cloud-triggered flows, or autolaunched flows.").

These Zendesk actions are available in Flow Builder.

- Create Custom Object
- Create Group
- Create Group Membership
- Create Many Tickets
- Create Organization
- Create Organization Membership
- Create Organization With Custom Fields
- Create Ticket
- Create Ticket With Custom Fields
- Create User
- Create User With Custom Fields
- Delete Custom Object
- Delete Group
- Delete Group Membership
- Delete Organization
- Delete Organization Membership
- Delete Ticket
- Delete User
- Get Custom Object By ID
- Get Group By ID
- Get Group Membership By ID
- Get Records
- Get Organization By ID
- Get Organization Membership By ID
- Get Ticket By ID
- Get User By ID
- List Audit Logs
- List Audits For A Ticket
- List Custom Objects
- List Group Memberships
- List Groups
- List Organization Memberships
- List Organizations
- List Ticket Comments
- List Tickets
- List Users
- Search Articles
- Show Audit
- Update Custom Object
- Update Group
- Update Organization
- Update Organization With Custom Fields
- Update Ticket
- Update Ticket With Custom Fields
- Update User
- Update User With Custom Fields

## Get Records Action

Query searchable objects from each connector by using custom filter logic in the MuleSoft for Flow: Integration Get Records action, which functions like the Salesforce Flow's [Get Records element](https://help.salesforce.com/s/articleView?id=platform.flow_ref_elements_data_get.htm&release=264.0.0&type=5 "The Get Records element finds all Salesforce or Marketing Object records that meet the filter and sort conditions and stores values from the retrieved records in variables. You can retrieve Salesforce standard and custom object records, or Marketing Object records, by using the Get Records element.").

The MuleSoft for Flow: Integration Get Records action:

- Defines queried object to ensure flexibility and adaptability across different data sources.
- Specifies available operators and enables the selection of fields, addition of conditions, and sorting of results.
- Defines the logical operator types.
- Includes other metadata to describe the operators available for each field when the available operators differ based on the object type.
- Runs the query request, processes the response, and formats the retrieved data accurately.

![Tip](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/images/icon_tip.png)

Tip For more information about the API, see the external system's API documentation.

![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/images/icon_important.png)

Important

For information about specific limitations for connections and third-party connectors, see [MuleSoft for Flow: Integration Limits & Considerations](https://help.salesforce.com/s/articleView?id=platform.automate_flow_considerations_mulesoft_for_flow_limits.htm&release=264.0.0&type=5 "When establishing connections to external systems, keep these limitations in mind.").