> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/powershell-universal/powershell-commands/send-psuevent.md).

# Send-PSUEvent

Send-PSUEvent sends event data or remote commands to an event hub connection or a connected computer session.

## SYNOPSIS

Sends data or commands to an event hub, computer, or computer group.

## SYNTAX

```powershell
Send-PSUEvent -Hub <String> [-ConnectionId <String>] [-Data <Object>] [-Timeout <Int32>] [-ComputerName <String>] [-AppToken <String>] [-Credential <PSCredential>] [-UseDefaultCredentials] [-Integrated] [-TrustCertificate] [-Cookies]
Send-PSUEvent -Hub <String> [-ConnectionId <String>] [-Command <String>] [-Parameters <Hashtable>] [-Timeout <Int32>] [-ComputerName <String>] [-AppToken <String>] [-Credential <PSCredential>] [-UseDefaultCredentials] [-Integrated] [-TrustCertificate] [-Cookies]
Send-PSUEvent -Computer <String> [-Data <Object>] [-ScriptBlock <ScriptBlock>] [-Timeout <Int32>] [-ComputerName <String>] [-AppToken <String>] [-Credential <PSCredential>] [-UseDefaultCredentials] [-Integrated] [-TrustCertificate] [-Cookies]
Send-PSUEvent -Computer <String> [-Command <String>] [-Parameters <Hashtable>] [-Timeout <Int32>] [-ComputerName <String>] [-AppToken <String>] [-Credential <PSCredential>] [-UseDefaultCredentials] [-Integrated] [-TrustCertificate] [-Cookies]
Send-PSUEvent -ComputerGroup <String> [-Data <Object>] [-ScriptBlock <ScriptBlock>] [-Timeout <Int32>] [-ComputerName <String>] [-AppToken <String>] [-Credential <PSCredential>] [-UseDefaultCredentials] [-Integrated] [-TrustCertificate] [-Cookies]
Send-PSUEvent -ComputerGroup <String> [-Command <String>] [-Parameters <Hashtable>] [-Timeout <Int32>] [-ComputerName <String>] [-AppToken <String>] [-Credential <PSCredential>] [-UseDefaultCredentials] [-Integrated] [-TrustCertificate] [-Cookies]
```

## DESCRIPTION

Sends serialized data or requests command execution on connected agents. Select an event hub with `-Hub`, one agent with `-Computer`, or a group with `-ComputerGroup`. For an agent, use `-ScriptBlock` for a script invocation or `-Command` and `-Parameters` for a module command; these options belong to different parameter sets. `-Timeout` defaults to 30 seconds. `Invoke-PSUCommand` is an alias.

## EXAMPLES

```powershell
Send-PSUEvent -Hub 'MyHub' -Data @{ Name = 'Adam' }
Send-PSUEvent -ComputerGroup 'Build agents' -Command 'Get-Process' -Parameters @{ Name = 'pwsh' } -Timeout 30
```

## PARAMETERS

| Parameter                | Description                                                                            |
| ------------------------ | -------------------------------------------------------------------------------------- |
| `-Hub`                   | Event hub name; event data goes to all connections unless `-ConnectionId` is supplied. |
| `-ConnectionId`          | Send to a specific connection on the hub.                                              |
| `-Computer`              | Target a connected computer.                                                           |
| `-ComputerGroup`         | Target a connected computer group.                                                     |
| `-Data`                  | Object to serialize and send to a hub or computer.                                     |
| `-ScriptBlock`           | Script to run on a computer or computer group.                                         |
| `-Command`               | Module command to run on a computer, group, or hub.                                    |
| `-Parameters`            | Hashtable of parameters passed to `-Command`.                                          |
| `-Timeout`               | Time in seconds to wait for the result; default is 30.                                 |
| `-ComputerName`          | PSU server URL for a remote management connection; alias: `-Uri`.                      |
| `-AppToken`              | App token for a remote management connection.                                          |
| `-Credential`            | Credentials for the management API.                                                    |
| `-UseDefaultCredentials` | Use the current Windows credentials for the management connection.                     |
| `-Integrated`            | Use the in-process PSU management client when the cmdlet runs inside PSU.              |
| `-TrustCertificate`      | Allow a remote connection with an untrusted TLS certificate.                           |
| `-Cookies`               | Reuse and persist authentication cookies in this PowerShell session.                   |

## PERMISSIONS

The access token requires `apis.eventhubs/execute` to run this cmdlet remotely. This also applies when the command targets a computer or computer group.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.devolutions.net/powershell-universal/powershell-commands/send-psuevent.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.