Copilot Studio UiPath Connector "Add Queue Item"

Help Technology Integrations
1

I am playing around with the UiPath Connector “Add Queue Item” in MS Copilot Studio for an agent. I have all the inputs figured out and working but the specific content part. I cannot figure out how to get the “Specific Content” input to work. Has anyone had any success with it? I am getting “connectorPowerFxErrorEvaluating PowerFx expression resulted in error while invoking the connector : Expected to get object for property SpecificContent but got StringValue”. Thanks!

2

Hi @cmurray,

The error is coming because the SpecificContent field expects an object (record format), but a plain string is being passed. When the entire value is written inside quotes, Copilot Studio treats it as text, which causes the type mismatch error saying it expected an object but received a StringValue.

To resolve this, pass the data as a proper PowerFx record structure instead of a string. Do not wrap the whole structure in quotes. The format should look like this:

{
InvoiceNumber: “12345”,
Amount: 5000,
Vendor: “ABC Ltd”
}

If the values are dynamic, reference them directly without quotes around the full structure and convert numeric values properly where needed. For example:

{
InvoiceNumber: TextInput1.Text,
Amount: Value(TextInput2.Text),
Vendor: TextInput3.Text
}

Once SpecificContent is sent as a structured object and not as plain text, the Add Queue Item connector will work correctly without throwing the error.

3

Hi @cmurray,

This error usually indicates a data-type mismatch rather than a connector issue.
The SpecificContent parameter in the UiPath Add Queue Item action expects a structured object, but Copilot Studio is currently passing it as text. This often happens when the payload is enclosed in quotes or produced using JSON(), which converts the record into a string.

Instead of sending JSON text, construct and pass a Power Fx record directly, for example:

{
    InvoiceNumber: TextInput1.Text,
    Amount: Value(TextInput2.Text),
    Vendor: TextInput3.Text
}

As long as the value is provided as a record (not a string), the connector should accept it without errors.