--- title: Queue connector methods description: The Queue connector methods enable you to create and manage work items for queues in the RPA Hub. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/integrate-applications/connectors-queues-methods.html release: australia topic_type: reference last_updated: "2026-03-12" reading_time_minutes: 10 breadcrumb: [Queue, RPA Hub, Automation components, RPA Desktop Design Studio, Robotic Process Automation \(RPA\) Hub, Workflow Data Fabric] --- # Queue connector methods The Queue connector methods enable you to create and manage work items for queues in the RPA Hub. ## Prerequisites 1. Assign the bot process to the automation project by using the **Assign bot process** option from the **Design** tab of RPA Desktop Design Studio to access the work items. For more information, see [Assign bot process to an automation project](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/assign-bot-process.md). 2. Set the QueueName property by doing the following steps: 1. In the RPA Desktop Design Studio, navigate to **Toolbox** > **RPA Hub** > **Queue**. 2. Drag the Queue connector under Global Objects in the Project Explorer. 3. Double-click the Queue connector. 4. Under the Properties pane, in the QueueName property, enter the name of the Queue. **Note:** The name of the Queue must be the same as that defined in RPA Hub. ## CreateJSONWorkItem Creates a work item for the queue in the JSON format. - **Input** [Name](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/queue-connector-method-parameters.md) [Priority](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/queue-connector-method-parameters.md) - **Output** [WorkItemId](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/queue-connector-method-parameters.md) [IsNameExists](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/queue-connector-method-parameters.md) To create the key-value pairs in a JSON object, do the following actions: 1. On the CreateJSONWorkItem method bar, click the method settings icon \(\[Omitted image "component-settings-icon.png"\] Alt text: Method settings icon.\). 2. Enter the criteria as given in the table.
| Field | Description |
|---|---|
| CONFIGURATION | |
| INPUT FIELDS | |
| Type | The type of the work item. For example, for an accounting system queue, savings and current are types of accounts. To configure the input field, see [Configure port properties](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/configure-input-port-properties.md). |
| Stage | Updates the stage of the work item. Custom field to maintain different stages of the transaction. |
| SLA | Service Level Agreement \(SLA\) of the work item completion. |
| JSON PROPERTIES | |
| JSON PATH NOTATIONS | |
| Name | Key-value pair \(JSON content\) for the request content. To add a key, do the following: 1. Click the add key icon \(\[Omitted image "add-image-icon.png"\] Alt text: Add key icon.\). 2. Enter the key name in the field. 3. To add more keys, repeat the previous steps. 4. To pass the value to these fields, see [Configure port properties](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/configure-input-port-properties.md). |
| Sensitive | Sensitive content that is passed when the work item is created. Select this option as sensitive, then the data is encrypted and stored in the **Sensitive Request Content** field in the new work item in RPA Hub. For more information about the work item form, see [Work item form in RPA Hub](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/manage-work-queue-items.md). With this functionality, you can pass sensitive information through queues. For example, if you want customer data to be encrypted in the queue, you must use the **Sensitive** field to store customer details such as credit card number, address, and so on. |
| Field | Description |
|---|---|
| INPUT FIELDS | |
| SensitiveRequestContent | Stores sensitive content in encrypted format in the new work item. To configure the input field, see [Configure port properties](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/configure-input-port-properties.md). With this functionality, you can pass sensitive information through queues. For example, if you want customer data to be encrypted in the queue, you must use the **SensitiveRequestContent** field to store customer details such as credit card number, address, and so on. |
| Stage | Updates the stage of the work item. Custom field to maintain different stages of the transaction. |
| Type | The type of the work item. For example, for an accounting system queue, savings and current are types of accounts. To configure the input field, see [Configure port properties](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/configure-input-port-properties.md). |
| SLA | Service Level Agreement \(SLA\) of the work item completion. |
| Field | Description |
|---|---|
| INPUT FILTERS | |
| Name | Name of the work item. You can specify one of the following filters:- **Equals**: Name of the work item is exactly equal to the criteria you specify. - **Contains**: Name of the work item contains characters you specify. - **StartsWith**: The name of the work item starts with the characters you specify. - **EndsWith**: The name of the work item starts with the characters you specify. |
| Type | Type of the work item in string format. You can specify one of the following filters:- **Equals**: Type of the work item is exactly equal to the criteria you specify. - **Contains**: Type of the work item contains characters you specify. - **StartsWith**: The type of the work item starts with the characters you specify. - **EndsWith**: The type of the work item starts with the characters you specify. |
| Status | Status of the work item. |
| Stage | Updates the stage of the work item. Custom field to maintain different stages of the transaction. |
| Priority | Priority of execution:- **Critical** - **High** - **Medium** - **Low** The assigned robot executes the bot process as per the defined priority in the work queue. The default priority is always **High**. |
| DateType | Date type of the work item. If you provide inputs to this field, you must also provide inputs to the **FromData** and **ToDate** fields also. |
| FromDate | If the method is picking work items within a date range, starting date in the range. |
| ToDate | If the method is picking work items within a date range, ending date in the range. |
| Offset | Number of work items that will be retrieved after the set limit. For example, if the limit is 20, the next picked work item starts from 21. |
| OUT FIELDS | |
| OutRecords | Returns the details of the work items in an object form. |
| Field | Description |
|---|---|
| CONFIGURATION | |
| INPUT FILTERS | |
| Name | Name of the work item based on the following filters.- **Equals**: Name of the work item is exactly equal to the criteria you specify. - **Contains**: Name of the work item contains characters you specify. - **StartsWith**: The name of the work item starts with the characters you specify. - **EndsWith**: The name of the work item starts with the characters you specify. Selection exposes a Data In port. |
| Type | Type of the work item based on the following filters. - **Equals**: Type of the work item is exactly equal to the criteria you specify. - **Contains**: Type of the work item contains characters you specify. - **StartsWith**: The type of the work item starts with the characters you specify. - **EndsWith**: The type of the work item starts with the characters you specify. Selection exposes a Data In port. |
| Stage | Stage of the work item work item based on the following filters. - **Equals**: Stage of the work item is exactly equal to the criteria you specify. - **Contains**: Stage of the work item contains characters you specify. - **StartsWith**: Stage of the work item starts with the characters you specify. - **EndsWith**: Stage of the work item starts with the characters you specify. Selection exposes a Data In port. |
| Status | Status of the work item for the robot to select. |
| OUT FIELDS | |
| Name | Data out port that returns the name of the work item. |
| Type | Data out port that returns the type of the work item. |
| Remarks | Data out port that returns remarks on the work item. |
| Stage | Data out port that returns the stage of the work item. |
| RequestContent | String content for the work item. Picks the stored content when the work item is created. |
| SensitiveRequestContent | The sensitive content from this field is picked, decrypted and passed to the RPA Desktop Design Studio or robots. |
| JSON PROPERTIES | |
| JSON PATH NOTATIONS | Data out port that returns the JSON path notation of a work item.Click the add key icon \(\[Omitted image "add-image-icon.png"\] Alt text: Add key icon.\) to add a key name. JSON can be passed in both **RequestContent** and **SensitiveRequestContent** fields. While picking work item, the JSON data is picked from a work item. For example, if a key-value pair "City: Mumbai" \(City is key and Mumbai is value\) is in the **RequestContent** field and "City: Delhi" \(City is key and Delhi is value\) is created in **SensitiveRequestContent** field. When you try to pick the same work item, since the key is same for both fields, the **SensitiveRequestContent** field is given precedence and that output is retrieved from this field. |
| Field | Description |
|---|---|
| CONFIGURATION | |
| INPUT FIELDS | |
| Stage | Updates the stage of the work item. Custom field to maintain different stages of the transaction. |
| DeferredTill | Option to specify a time duration during which the same work item will not be picked. For example, 5 minutes. |
| Name | Name of the work item. |
| Type | The type of the work item. For example, for an accounting system queue, savings and current are types of accounts. To configure the input field, see [Configure port properties](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/configure-input-port-properties.md). |
| Remarks | Supporting remarks on the work item. |
| SLA | Service Level Agreement \(SLA\) of the work item completion. |
| ResponseContent | String content for the work item. Updates the stored content of a work item. |
| SensitiveRequestContent | Updates the sensitive content of a work item. |
| JSON PROPERTIES | |
| JSON PATH NOTATIONS | |
| Name | Key-value pair \(JSON content\) for the request content. To add a key, do the following: 1. Click the add key icon \(\[Omitted image "add-image-icon.png"\] Alt text: Add key icon.\). 2. Enter the key name in the field. 3. To add more keys, repeat the previous steps. 4. To pass the value to these fields, see [Configure port properties](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/configure-input-port-properties.md). |
| Sensitive | Sensitive content is updated for a work item. With this functionality, you can pass sensitive information through queues. For example, if you want customer data to be encrypted in the queue, you must use the **Sensitive** field to store customer details such as credit card number, address, and so on. When you add a key-value pair "City: Mumbai" in **SensitiveRequestContent** field and add another key-value pair "Country: India" in JSON Path Notation and the UpdateWorkItem is executed. Then, in the **SensitiveRequestContent** field, the output is combined to "City: Mumbai" and "Country: India". |