# Enqueue Multiple Items

Adds items to a Gradient Works Queue. The items may be of any type (e.g. Account, Lead, etc). This \*\*does not\*\* assign the items immediately, instead they are put in a pending state in the Queue.

If you specify a capacity using `capacityValue` or `capacityValueField`, that value will be used in capacity calculations when assigning the item to a user. For example, if you specify a `capacityValue` of 5, users must have an `availableCapacity` greater than or equal to 5 to be eligible for assignment.

Why use this instead of [Assign Multiple Items](https://docs.gradient.works/kb/automation-builder-kit-abk/actions/assignment/assignmultiitemaction)? In some cases it can be more efficient to add many items to the queue through various steps in a Flow and then perform the assignments all at once. You can explicitly trigger assignment for a particular queue by including [Assign Pending Items for Single Queue](https://docs.gradient.works/kb/automation-builder-kit-abk/actions/advanced/assignpendingsinglequeueaction) or [Assign Pending Items for Multiple Queues](https://docs.gradient.works/kb/automation-builder-kit-abk/actions/advanced/assignpendingmultiqueueaction) in your Flow. If you don't explicitly trigger assignment in your Flow, Gradient Works will assign the pending items at some point in the near future.

## Inputs

| Name               | Required | Type           | Description                                            |
| ------------------ | -------- | -------------- | ------------------------------------------------------ |
| queue              | Yes      | String         | The queue to add to. May be an Id or the queue name.   |
| capacityValue      | No       | Long           | Capacity value to apply to all items                   |
| capacityValueField | No       | String         | Retrieve capacity value from this field on each object |
| objects            | No       | List\<SObject> | List of items to add to the queue                      |