Zendesk Connector Reference | MuleSoft Documentation
# Zendesk Connector Reference
Zendesk is a help desk management solution providing tools for customer service.
## Connections
To connect to a system, whether it is a source of data or the target where you are sending data, you must create a connection with that system’s required credentials. You typically connect to different systems within a flow and can reuse each connection every time you need to connect.
This system requires the following credential information for its connections: 

Connection Name
    
Enter a connection name that will help you remember the details of this connection. You can reuse connections multiple times in a single flow, and in more than one flow, and the credentials are hidden after you create the connection. Therefore, it’s helpful to provide a name that easily identifies this connection from others.
Only you can see the connection. Other users in your Composer app must create their own connections. 

Connection Display Name
    
The Connection Display Name that you use to log in to Zendesk. 

Base URI
    
The Base URI that you use to log in to Zendesk.
## Triggers
Each flow starts with either a _scheduler_ or a _trigger_. Schedulers are set to a default frequency of 15 minutes. Triggers, such as "each time a new record is created", are defined by you and provide multiple options related to the data in your system.
Triggers use a polling process to actively check for new updates from an external system. The polling frequency is 15 seconds.
This system provides the following trigger options: 

New/updated ticket
    
Checks for a new or updated ticket. 

New/updated organization
    
Fires when a new organization is created or an existing organization is updated in Zendesk. 

New/updated user
    
Fires when a new user is created or an existing user is updated in Zendesk.
### Polling Frequency
For triggers in this connector, the **Polling Frequency** field is required. This field enables you to select how often Composer makes a request to the underling system API to look for changes to records in active flows. You can select a different polling frequency for each flow in your organization. With a shorter frequency, the flow executes more often; however, a shorter frequency consumes more API calls. For example, if you have an order management flow, you might require nearly real-time updates, which can be achieved with a 15-second polling interval (which equates to 5760 API calls per day). In contrast, if your flow updates a pricing catalog, you could poll the flow every hour (which equates to 24 API calls per day).
## Actions
After you connect to a system and define the trigger or configure a scheduler, you define the actions that the flow performs. For example, you can copy a record between different systems, such as Workday and Salesforce. The actions you can perform depend on which system you are connected to.
This system provides the following actions: 

Create a ticket
    
Creates a new ticket. Provide values for the following fields:



Update a ticket
    
Updates an existing ticket. Provide values for the following fields:
  * **Ticket ID**
  * **Description**



Search tickets
    
Searches for a ticket based on specified criteria. 

Create or update an organization
    
Creates a new organization or updates an existing organization. 

Create or update a user
    
Creates a new user or updates an existing user. Provide a value for the following fields: 

Search organizations
    
Searches for organizations based on specified criteria and returns a list of organizations matching those criteria. 

Get Organization by ID
    
Returns an organization based on specified ID search criteria. 

Search users
    
Searches for users based on specified criteria and returns a list of organizations matching those criteria.
## See Also
  * Mulesoft Composer: Overview
  * MuleSoft Composer: Getting Started
  * Composer Connector Reference
  * Knowledge Articles