In order to perform more tasks, perform tasks more precisely and in-time, Workers interact with TaskQueues. Workers always listen to multiple TaskQueues or no Queue at all. When a task is feeded to TaskQueue, based on eligibility, capability and role of a Worker, a task is assigned to Worker to perform it. For example, a Worker can be a person in a call center, a web service endpoint that listens to instructions, or an expert fixing the system failure. Parameter | Type | Default | Description --------- | ------- | ------- | ----------- WorkspaceSID | String | '' | The SID of the Workspace with the Worker to update WorkerSID | String | '' | The SID of the Worker to be updated FriendlyName | String | '' | (optional) Human readable friendly name. It can be 512 characters long Activity | String | '' | (optional) Activity for `Worker`. A worker needs to be in `idle` activity to receive a suitable `Task` Attributes | String | '' | A URL-encoded JSON string with the features and skills of a Worker. This value is used for deciding which TaskQueues the Worker can receive `Task`s from. When you update this value , the related `TaskQueue`s of this Worker are updated RateLimitProfileSid | String | '' | (optional) The SID of the new `RateLimitProfile` for the `Worker` In order to perform more tasks, perform tasks more precisely and in-time, Workers interact with TaskQueues. Workers always listen to multiple TaskQueues or no Queue at all. When a task is feeded to TaskQueue, based on eligibility, capability and role of a Worker, a task is assigned to Worker to perform it. For example, a Worker can be a person in a call center, a web service endpoint that listens to instructions, or an expert fixing the system failure. ### Worker Properties * **sid** - The unique string that we created to identify the Worker resource. * **account_sid** - The SID of the Account that created the Worker resource. * **workspace_sid** - The SID of the Workspace that contains the Worker * **available** - Whether the Worker is available to perform tasks. * **friendly_name** - The string that you assigned to describe the resource. Friendly names are case insensitive, and unique within the Rindap Workspace. * **attributes** - A JSON String for describing the Worker and its features such as skills and information. This value is used for deciding which TaskQueues the Worker can receive Tasks from * **activity** - This Activity determines the Worker's current state in the system, as well as whether the Worker can accept new Task assignments. There are 4 types of Activities a Worker can be set to: * **idle:** the Worker is availabe and is waiting for Task Assignments * **busy:** the Worker is not available. The Worker is set to this Activity when a Reservation for this Worker is accepted. * **offline:** the Worker is not available. * **reserved:** This is a system Activity. At this stage, the Worker is paired with a Task and a reservation is created. * **date_created** - The date and time in GMT when the resource was created, specified in ISO 8601 format. * **date_status_changed** - The date and time in GMT when the Activity of the Worker was last updated, specified in ISO 8601 format. * **date_updated** - The date and time in GMT when the resource was last updated, specified in ISO 8601 format. * **url** - The absolute URL of the resource * **links** - The URLs of related resources. ### Worker Attributes A worker's attributes are used to simply and accurately represent a working entity on Rindap. These attributes can be skills and information about a person , in the case of a human Worker. Or it can be some identifying data and hard-coded parameters for a digital entity like a web service. When populating this field, you should keep in mind that the value in some of these fields might be used for creating the TaskQueue relations of this Worker, according to the `worker_requirements` field of TaskQueues , which is simply a JsonLogic rule. For example , a worker with attributes such as the one below: { "name" : "john doe" "age": 44 "department" : "support" "location": "Utah" } would be receiving Tasks from a TaskQueue with worker_requirements as such: { "==":[{"var":"department"},"support"] } Because the requirement rules for the TaskQueue would be matching the attributes of the Worker.