> 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/es/comandos-de-powershell/set-psutrigger.md).

# Set-PSUTrigger

Set-PSUTrigger actualiza un desencadenador de automatización existente en PowerShell Universal, incluidos su tipo de evento, script, panel y entorno.

## SYNOPSIS

Actualiza un desencadenador existente de PowerShell Universal Automation.

## SYNTAX

### Id

```
Set-PSUTrigger [-Id] <Int64> [-Name <String>] [-EventType <EventType>] [-Script <String>]
 [-TriggerScript <String>] [-Environment <String>] [-Dashboard <String>] [-ComputerName <String>]
 [-AppToken <String>] [-Credential <PSCredential>] [-UseDefaultCredentials] [-Integrated] [-TrustCertificate]
 [-Cookies] [<CommonParameters>]
```

### Desencadenador

```
Set-PSUTrigger [-Trigger] <Trigger> [-Name <String>] [-EventType <EventType>] [-Script <String>]
 [-TriggerScript <String>] [-Environment <String>] [-Dashboard <String>] [-ComputerName <String>]
 [-AppToken <String>] [-Credential <PSCredential>] [-UseDefaultCredentials] [-Integrated] [-TrustCertificate]
 [-Cookies] [<CommonParameters>]
```

## DESCRIPTION

Actualiza un desencadenador de automatización existente por Id o pasando un objeto de desencadenador a través de la canalización.

## EXAMPLES

### Ejemplo 1

```powershell
PS C:\> Set-PSUTrigger -Id 4 -Name "Server Startup" -EventType ServerStarted
```

Actualiza el desencadenador 4 para que use el tipo de evento ServerStarted.

## PARAMETERS

### -AppToken

Especifica el token de aplicación que se utilizará al autenticarse en la API de gestión de PowerShell Universal.

```yaml
Type: String
Parameter Sets: (All)
Aliases:

Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```

### -ComputerName

Especifica la URL o el nombre de host de la instancia de PowerShell Universal de destino. Los nombres de host simples se normalizan a una URL `http://<host>:5000`.

```yaml
Type: String
Parameter Sets: (All)
Aliases: Uri

Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```

### -Dashboard

Especifica el panel de destino.

```yaml
Type: String
Parameter Sets: (All)
Aliases:

Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```

### -Environment

Especifica el entorno de ejecución que se utilizará.

```yaml
Type: String
Parameter Sets: (All)
Aliases:

Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```

### -EventType

Especifica el tipo de evento que activa el desencadenador.

```yaml
Type: EventType
Parameter Sets: (All)
Aliases:
Accepted values: JobCanceled, JobFailed, JobCompleted, JobStarted, JobFeedbackRequested, ServerStarted, ServerStopped, DashboardStarted, DashboardStopped

Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```

### -Id

Especifica el Id numérico del recurso.

```yaml
Type: Int64
Parameter Sets: Id
Aliases:

Required: True
Position: 0
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```

### -Name

Especifica el nombre del recurso.

```yaml
Type: String
Parameter Sets: (All)
Aliases:

Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```

### -Script

Especifica el script de destino.

```yaml
Type: String
Parameter Sets: (All)
Aliases:

Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```

### -Trigger

Especifica el desencadenador de destino.

```yaml
Type: Trigger
Parameter Sets: Trigger
Aliases:

Required: True
Position: 0
Default value: None
Accept pipeline input: True (ByValue)
Accept wildcard characters: False
```

### -TriggerScript

Especifica el script que se ejecuta cuando se activa el desencadenador.

```yaml
Type: String
Parameter Sets: (All)
Aliases:

Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```

### -UseDefaultCredentials

Utilizar las credenciales predeterminadas al conectarse a la API de gestión

```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:

Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```

### -Integrated

Ejecuta el comando internamente en lugar de usar la API de gestión. Solo funciona cuando se ejecuta el script desde dentro de PowerShell Universal.

```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:

Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```

### -Credential

Credenciales para iniciar sesión en la API de gestión de PowerShell Universal.

```yaml
Type: PSCredential
Parameter Sets: (All)
Aliases:

Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```

### -TrustCertificate

Indica si el cmdlet debe ignorar los problemas de certificado.

```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:

Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```

### -Cookies

Reutiliza y conserva las cookies de autenticación para la sesión actual de PowerShell.

```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:

Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```

### CommonParameters

Este cmdlet admite los parámetros comunes: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutBuffer, -OutVariable, -PipelineVariable, -Verbose, -WarningAction, -WarningVariable y -ProgressAction. Para más información, consulte [about\_CommonParameters](http://go.microsoft.com/fwlink/?LinkID=113216).

## INPUTS

### UniversalAutomation.Trigger

## OUTPUTS

### System.Object

## NOTES

## RELATED LINKS

## SYNOPSIS

Actualiza un desencadenador de automatización.

## SYNTAX

```powershell
Set-PSUTrigger -Id <Int64> [-Name <String>] [-EventType <EventType>] [-Script <String>] [-Scripts <String[]>] [-TriggerScript <String>] [-Parameters <Hashtable>]
Set-PSUTrigger -Trigger <Trigger> [-Name <String>] [-EventType <EventType>] [-Script <String>] [-Scripts <String[]>] [-TriggerScript <String>] [-Parameters <Hashtable>]
```

## DESCRIPTION

Actualiza un desencadenador por ID u objeto de canalización. `-Scripts` reemplaza su selección de scripts y admite varios scripts. `-Parameters` es una tabla hash que se pasa al script del desencadenador cuando este se activa.

## EXAMPLE

```powershell
Set-PSUTrigger -Id 4 -Scripts 'Build.ps1','Deploy.ps1' -Parameters @{ Channel = 'ops' }
```


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.devolutions.net/powershell-universal/es/comandos-de-powershell/set-psutrigger.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.