Queue

Represents a holding area for items before they are processed.

Declarative Metadata File Suffix and Directory Location

The file suffix for queue components is .queue and components are stored in the queues directory of the corresponding package directory. This component supports cases, leads, service contracts (if Entitlements are enabled), and custom objects.

Version

Queue components are available in API version 24.0 and later.

Fields

This metadata type represents the valid values that define a queue:

Field Name	Field Type	Description
doesSendEmailToMembers	boolean	Indicates whether emails are sent to queue members (`true`) or not (`false`) when a new record is added to the queue.
email	string	The email address of the queue owner.
fullName	string	The unique identifier for API access. The fullName can contain only underscores and alphanumeric characters. It must be unique, begin with a letter, not include spaces, not end with an underscore, and not contain two consecutive underscores. This field is inherited from the Metadata component. Corresponds to Queue Name in the user interface.
name	string	Required. The name of the queue. Corresponds to Label in the user interface.
queueSobject	QueueSobject[]	Indicates the supported entity types.

QueueSobject

QueueSobject represents an entity type that the queue supports.

Field Name	Field Type	Description
sobjectType	string	Valid values are: `Case` `Lead` `ServiceContract` Custom objects (e.g. `ObjA_c`)

Declarative Metadata Sample Definition

The following is the definition of a queue, which supports Case, Lead, and a custom object named ObjA.

Metadata API Developer Guide