PowerShell Plugin

PowerShell event plugin for the xyOps Workflow Automation System.

---

Requirements

• PowerShell 7+ (Cross-Platform)

For detailed instructions on installing PowerShell, please review the Microsoft Learn Documentation.

Platform Support:

• Windows/Linux/macOS: PowerShell 7+

---

Parameters

• Code Block - Your PowerShell script code
• Enable Time in Output [optional] - Adds timestamps to each log line (enabled by default)
• Output xyOps JSON Data [optional] - Displays job configuration as formatted JSON (admin only)
• Process Module Files [optional] - Import all .psm1 files attached to the job input. These files can be uploaded on a manual job run or added to a bucket to be referenced by a 'Fetch Bucket' action.
• Data Passthrough [optional] - If checked, data output from one event will pass through automatically to its output. Note that if an event outputs the same data property as existing data that was passed in, it will overwrite what was passed into it.
• Bucket API Key Variable Name [optional] - The variable name used for the API Key used for accessing buckets. (See Setting Up Cache Bucket)
• Cache Bucket ID Variable Name [optional] - The secret vault variable name used for the Bucket ID when configuring the cache bucket setup. (See Setting Up Cache Bucket)
• Send Email API Key Variable Name [optional] - The secret vault variable name used for the API Key for sending emails. (See Setting Up Email API Key)

Usage

When creating an event, you will provide your PowerShell script code inside the Code Block parameter. The job data is made available as a PowerShell object variable called $xyOps. Enabling Output xyOps JSON Data will display the structure of this object and can be used when developing your scripts. It is not recommended to keep this on for production jobs.

Setup

At the end of this document, there are some optional configuration steps that are required to use certain helper functions. Setting Up Cache Bucket | Setting Up Email API Key

---

Helper Functions

This plugin includes the following helper functions:

Logging & Core Output

• Write-xyOpsJobOutput - Write log messages with severity levels
• Send-xyOpsOutput - Low-level structured output to xyOps
• Send-xyOpsProgress - Report job progress percentage
• Set-xyOpsJobResult - Set the final jobs status that is passed to xyOps

File & Data Management

• Send-xyOpsFile - Upload files to job output
• Send-xyOpsPerf - Report performance metrics (pie chart)
• Send-xyOpsLabel - Set custom job label
• Send-xyOpsData - Pass data to next job in workflow
• Get-xyOpsInputFiles - Get input file metadata
• Get-xyOpsBucketFile - Gets file from the specified bucket
• Add-xyOpsBucketFile - Adds file to the specified bucket
• Remove-xyOpsBucketFile - Deletes file from the specified bucket
• Get-xyOpsBucketData - Gets data from the specified bucket
• Set-xyOpsBucketData - Sets data in the cache bucket
• Get-xyOpsCache - Gets data from the cache bucket
• Set-xyOpsCache - Sets data in the cache bucket
• Get-xyOpsParam - Get parameter values (supports listing all params)
• Get-xyOpsTags - Gets available system tags.
• Send-xyOpsTags - Pushes tags to the job output.
• Send-xyOpsEmail - Send an email using the built-in xyOps mechanism.

UI Display Functions

• Send-xyOpsTable - Display data tables
• Send-xyOpsHtml - Display HTML content
• Send-xyOpsText - Display plain text (preserved formatting)
• Send-xyOpsMarkdown - Display Markdown content

Syntax

---

Write-xyOpsJobOutput

Write-xyOpsJobOutput [-Message] <string> [-Level {info | warning | error | critical}] [-Halt]

.SYNOPSIS
	Writes messages to the xyOps job output stream with optional timestamps.

.DESCRIPTION
	This function lets you report text back to the job output which will be displayed in the job details.

.PARAMETER Message
	The message to log.

.PARAMETER Level
	The log level (info, warning, error, critical). Default is 'info'.

.PARAMETER Halt
	Setting this switch will halt the processing of the script completely and jump to the end. This does not cause the script to error by default. If the Level is set to 'info', the script will halt but show as completed successfully.

Examples:

# Reporting text back to the job output.
Write-xyOpsJobOutput "Sample output to be passed to xyOps job output."

# Strings can be piped to the helper function.
"Log this information to the job output, please. Thanks." | Write-xyOpsJobOutput -Level warning

Logging & Core Output

---

Send-xyOpsOutput

Send-xyOpsOutput [-InputObject] <object>

.SYNOPSIS
	Sends structured JSON output back to the xyOps system. This is low-level output to xyOps.

.DESCRIPTION
	This function provides a simple way to report back updates to the job output using a PowerShell object or a hashtable. The input is converted to the proper JSON format that xyOps requires. Keep in mind that xyOps expects a specific structure, depending on what you're reporting back.

.PARAMETER InputObject
	The object to send to xyOps. Can be a hashtable, PSCustomObject, array, or primitive type.

Please refer to the xyOps documentation for more information.

Examples:

# Tell xyOps that the job has completed successfully.
Send-xyOpsOutput @{ xy = 1; code = 0 }

# Bypass the Send-XyOpsProgress function and report the progress data directly using the Send-XyOpsOutput function.
Send-xyOpsOutput ([pscustomobject]@{
	xy       = 1
	progress = 0.75
})

Logging & Core Output

---

Send-xyOpsProgress

Send-xyOpsProgress [-Percent] <decimal> [-Status <string>]

.SYNOPSIS
	Reports job progress percentage to xyOps.

.DESCRIPTION
	Sends a progress update to the xyOps system with a percentage value between 0 and 100. Optionally, you can include a status with the progress update using the -Status parameter.

.PARAMETER Percent
	The progress percentage (0-100).

.PARAMETER Status
	The current status for the job.

Examples:

# Report progress of 25%.
Send-xyOpsProgress -Percent 25

# Report progress with an optional status.
Send-xyOpsProgress -Percent 46 -Status "Processing $($itemNumber) of $($items.Count)..."

# Report progress with an optional status.
Send-xyOpsProgress 75.5 "Almost done!"

# Using Send-xyOpsProgress how you might normally use PowerShell's built-in Write-Progress cmdlet.

function repeatNames {
	param(
		$firstName,
		$lastName
	)

	$items = 1..5
	$current = 0
	foreach ($current in $items) {
		$current++
		Send-xyOpsProgress ($current / $items.Count * 100) "Working on $($current) of $($items.Count)"
		Write-xyOpsJobOutput "Hello, $($firstName) $($lastName)! Welcome!"
		Start-Sleep -Seconds 1
	}
}

repeatNames -firstName Jon -lastName Doe

Logging & Core Output

---

Set-xyOpsJobResult

Set-xyOpsJobResult [-Status] {success | warning | error | critical} [-Description] <string>

.SYNOPSIS
	Set the final job result status and description.

.DESCRIPTION
	This function sets the current job result status and description that will be passed to xyOps at the end of the script processing. It's designed so that the severity of the status can't be downgraded. For example, a warning can't be changed to a success, an error can't be changed to a warning or success, and so on.

.PARAMETER Status
	The status of the job result to be set.

.PARAMETER Description
	The description that will accompany the result.

Examples:

# Set the job result to warning with a custom description.
Set-xyOpsJobResult -Status warning -Description 'A non-breaking issue occurred.'

Logging & Core Output

---

Send-xyOpsStatus

Send-xyOpsStatus [-Status] <string>

.SYNOPSIS
	Reports job status to xyOps.

.DESCRIPTION
	Sends a status for the job that is displayed on the job status page as well as the jobs list.

.PARAMETER Status
	The current status for the job.

Examples:

# Report a status.
Send-xyOpsStatus "Building sites list..."

# Report a status.
Send-xyOpsStatus -Status "Processing $($itemNumber) of $($items.Count)..."

File & Data Management

---

Send-xyOpsFile

Send-xyOpsFile [-Filename] <string>

.SYNOPSIS
	Reports file changes to the xyOps system so that xyOps can upload the file and use it.

.DESCRIPTION
	Uploads a file to the job output. The file is then accessible in the UI to download. It can also be passed to the input of a proceeding event within a workflow to be further processed.

.PARAMETER Filename
	The path to the file to report.

Examples:

# Report a generated file back to the job output.
$outfile = "people_$(New-Guid).csv"
$peopleList | Export-Csv -Path $outfile
Send-xyOpsFile $outfile

# Generate output and report the file in one event, then consume the file in a second event using a workflow.

######
#First Event Code (generate data and output file)
######

$filename = "people_$(New-Guid).csv"

$items = @(
	[pscustomobject]@{
		Name = 'John Doe'
		Age = 40
		Country = 'Canada'
	}
	[pscustomobject]@{
		Name = 'Jane Doe'
		Age = 41
		Country = 'United Kingdom'
	}
	[pscustomobject]@{
		Name = 'Bob Smith'
		Age = 75
		Country = 'United States'
	}
	[pscustomobject]@{
		Name = 'Sally Smith'
		Age = 39
		Country = 'Canada'
	}
)

$items | Export-Csv -Path $filename -NoTypeInformation

Send-xyOpsFile $filename
 
######
# Second Event Code (receiving input from previous event)
######

$files = Get-xyOpsInputFiles
$people = Import-Csv -Path $files[0].filename

foreach ($person in $people) {
	Write-xyOpsJobOutput "$($person.Name), $($person.Age), is from $($person.Country)."
}

File & Data Management

---

Send-xyOpsPerf

Send-xyOpsPerf [-Metrics] <hashtable> [-Scale <int>]

.SYNOPSIS
	Reports performance metrics to xyOps.

.DESCRIPTION
	Sends performance timing data to xyOps for display as a pie chart on the Job Details page. Metrics represent time spent in different categories.

.PARAMETER Metrics
	Hashtable of performance metrics where keys are category names and values are time in seconds.

.PARAMETER Scale
	Optional scale factor if metrics are not in seconds (e.g., 1000 for milliseconds).

Examples:

# Metrics in seconds
Send-xyOpsPerf @{ db = 18.51; http = 3.22; gzip = 0.84 }

# Metrics in milliseconds
Send-xyOpsPerf @{ db = 1851; http = 3220; gzip = 840 } -Scale 1000

File & Data Management

---

Send-xyOpsLabel

Send-xyOpsLabel [-Label] <string>

.SYNOPSIS
	Sets a custom label for the job.

.DESCRIPTION
	Sets a custom label for the job which will be displayed alongside the Job ID in the xyOps UI. Useful for differentiating jobs with different parameters.

.PARAMETER Label
	The label text to display.

Examples:

# Set a label of 'Backup - Production DB'
Send-xyOpsLabel "Backup - Production DB"

# Set a label with a variable that would change depending on the environment it's running on.
Send-xyOpsLabel "Deploy to $env:TARGET_ENV"

File & Data Management

---

Send-xyOpsData

Send-xyOpsData [-Data] <object>

.SYNOPSIS
	Sends arbitrary output data to be passed to the next job.

.DESCRIPTION
	Outputs data that will be automatically passed to the next job in a workflow or via a run event action. Data can be any PowerShell object.

.PARAMETER Data
	The data object to pass to the next job.

Examples:

Send-xyOpsData @{ hostname = "server01"; status = "ok" }

File & Data Management

---

Get-xyOpsInputFiles

Get-xyOpsInputFiles

.SYNOPSIS
	Gets the list of input files passed to the job.

.DESCRIPTION
	Returns an array of input file metadata objects from the xyOps job input. Files are already downloaded to the current working directory.

Examples:

$files = Get-xyOpsInputFiles
foreach ($file in $files) {
	foreach ($file in $files) {
		Write-Host "Processing: $($file.filename)"
	}
}

File & Data Management

---

Get-xyOpsBucketFile

Get-xyOpsBucketFile [-BucketId] <string> [-Filename] <string> [-OutFilename <string>]

.SYNOPSIS
	Gets file from the specified bucket.

.DESCRIPTION
	Uses the get_bucket API to retrieve a file from a specified bucket.

.PARAMETER BucketId
	The ID of the bucket you want to access.

.PARAMETER Filename
	The filename in the bucket you want to retrieve.

.PARAMETER OutFilename
	Optionally, set the output filename to save as. Otherwise, the same filename as the original file is used.

Examples:

Get-xyOpsBucketFile -BucketId 'bml2ut4ys4pt7raf' -Filename 'customers.csv'

API Key Required, see Setting Up Cache Bucket

File & Data Management

---

Add-xyOpsBucketFile

Add-xyOpsBucketFile [-BucketId] <string> [-Filename] <string>

.SYNOPSIS
	Adds file to the specified bucket.

.DESCRIPTION
	Uses the upload_bucket_files API to add a file to a specified bucket.

.PARAMETER BucketId
	The ID of the bucket you want to access.

.PARAMETER Filename
	The local filename you want to upload to the bucket.

Examples:

$newFile = New-FileName -FileType csv
$customers | Export-Csv -FilePath $newFile
Add-xyOpsBucketFile -BucketId 'bml2ut4ys4pt7raf' -Filename $newFile

API Key Required, see Setting Up Cache Bucket

File & Data Management

---

Remove-xyOpsBucketFile

Remove-xyOpsBucketFile [-BucketId] <string> [-Filename] <string>

.SYNOPSIS
	Deletes file from the specified bucket.

.DESCRIPTION
	Uses the delete_bucket_file API to delete a file from a specified bucket.

.PARAMETER BucketId
	The ID of the bucket you want to access.

.PARAMETER Filename
	The filename you want to delete from the bucket.

Examples:

Remove-xyOpsBucketFile -BucketId 'bml2ut4ys4pt7raf' -Filename 'customers.csv'

API Key Required, see Setting Up Cache Bucket

File & Data Management

---

Get-xyOpsBucketData

Get-xyOpsBucketData [-BucketId] <string>

.SYNOPSIS
	Gets data from the specified bucket.

.DESCRIPTION
	Uses the get_bucket API to retrieve JSON data from the specified bucket.

.PARAMETER BucketId
	The ID of the bucket you want to access.

Examples:

$bucketData = Get-xyOpsBucketData -BucketId 'bml2ut4ys4pt7raf'

API Key Required, see Setting Up Cache Bucket

File & Data Management

---

Set-xyOpsBucketData

Set-xyOpsBucketData [-BucketId] <string> [-Key] <string> [-InputObject] <object>

.SYNOPSIS
	Sets data in the cache bucket.

.DESCRIPTION
	Uses the write_bucket API to write a JSON converted object to a specified bucket data.

.PARAMETER BucketId
	The ID of the bucket you want to access.

.PARAMETER Key
	The key of the item you want to add to the bucket data.

.PARAMETER InputObject
	The input object you want to add to the bucket data.

Examples:

Set-xyOpsBucketData -BucketId 'bml2ut4ys4pt7raf' -Key 'Countries' -InputObject @('Canada','United States','United Kingdom')

API Key Required, see Setting Up Cache Bucket

File & Data Management

---

Get-xyOpsCache

Get-xyOpsCache [-Key] <string>

.SYNOPSIS
	Gets data from the cache bucket.

.DESCRIPTION
	Uses the get_bucket API to retrieve JSON data from a bucket configured for cache.

.PARAMETER Key
	The key of the cached item you want to retrieve from the cache bucket.

Examples:

$Countries = Get-xyOpsCache -Key Countries

API Key Required, see Setting Up Cache Bucket

File & Data Management

---

Set-xyOpsCache

Set-xyOpsCache [-Key] <string> [-InputObject] <object>

.SYNOPSIS
	Sets data in the cache bucket.

.DESCRIPTION
	Uses the write_bucket API to write a JSON converted object to a bucket data configured for cache.

.PARAMETER Key
	The key of the cache item you want to set.

.PARAMETER InputObject
	The input object you want to save in the cache bucket data.

Examples:

Set-xyOpsCache -Key Countries -InputObject @('Canada','United States','United Kingdom')

API Key Required, see Setting Up Cache Bucket

File & Data Management

---

Get-xyOpsParam

Get-xyOpsParam [-Name <string>]

.SYNOPSIS
	Gets a parameter value from xyOps or environment variable.

.DESCRIPTION
	Retrieves a parameter value, checking both the params object and environment variables. Environment variables are checked first. When called without a Name parameter, displays all available parameters in a formatted table.

.PARAMETER Name
	The parameter name to retrieve. If omitted, displays all available parameters.

Examples:

# Get specific parameters
$timeout = Get-xyOpsParam -Name "timeout"
$apiKey = Get-xyOpsParam -Name "api_key"

# List all available parameters
Get-xyOpsParam

File & Data Management

---

Get-xyOpsTags

Get-xyOpsTags [-Tags <list>]

.SYNOPSIS
	Gets available system tags.

.DESCRIPTION
	Gets available system tags using the get_tags API. Optionally, you can supply tag titles so that only those are returned.

.PARAMETER Tags
	Optionally supply a list of tag titles as an array or list. If the tags exist, they will be returned.

Examples:

# Get all tags.
Get-xyOpsTags

# Get specific tags.
Get-xyOpsTags -Tags @('Canada','United States','United Kingdom')

# Get specific tags.
Get-xyOpsTags 'John','Joe','Jill','Jane'

API Key Required, see Setting Up Cache Bucket

File & Data Management

---

Send-xyOpsTags

Send-xyOpsTags [-Tags] <list>

.SYNOPSIS
	Pushes tags to the job output.

.DESCRIPTION
	Pushes one or more tags to be appended to the job output. The tags are provided as an array or list of tag names. Available tags are retrieved from the system to get the ID, which is used by xyOps to apply the correct tag.

.PARAMETER Tags
	An array or list of tag titles or IDs to be set on the job. The tags must exist in the xyOps tags configuration, otherwise they will be ignored.

Examples:

# Push tags to job output
Send-xyOpsTags -Tags @('Canada','United States','United Kingdom')

# Push tags to job output
Send-xyOpsTags 'John','Joe','Jill','Jane'

API Key Required, see Setting Up Cache Bucket

File & Data Management

---

Send-xyOpsEmail

Send-xyOpsEmail -To <string> -Subject <string> -Body <string> [-CC <array[string]>] [-BCC <array[string]>] [-Title <string>] [-ButtonLabel <string>] [-ButtonUri <string>] [-Importance {low | normal | high}] [-Attachments <array[string]>]

.SYNOPSIS
	Send an email using the built-in xyOps mechanism.

.DESCRIPTION
	Sends an email using the built-in xyOps mechanism and configuration.

.PARAMETER To
	The email address of the recipient. Multiple recipients should be comma-separated.

.PARAMETER Subject
	The email subject.

.PARAMETER Body
	The email body. This parameter is processed as Markdown so your body text can be formatted using Markdown syntax. This also means
	you can supply pure HTML as Markdown supports HTML directly.

.PARAMETER CC
	The email address(es) of the recipient(s) to CC. Multiple recipients should be comma-separated.
	
.PARAMETER BCC
	The email address(es) of the recipient(s) to CCC. Multiple recipients should be comma-separated.

.PARAMETER Title
	Title text that will be displayed at the top of the email in larger text.

.PARAMETER ButtonLabel
	The label used in the optional button. Include this parameter to include a button in the top-right corner of the email.

.PARAMETER ButtonUri
	The Uri to where the button will link to.

.PARAMETER Importance
	Set the importance of the email. Choose between low, normal and high. This is set to normal by default.

.PARAMETER Attachments
	Provice an array or list of file paths to files that you want to attach to the email.

Examples:

# Send a basic email with high importance
Send-xyOpsEmail -To "user@domain.com" -Subject "Important Email Update" -Body "This is a test!" -Importance high

# Send an email with attachments
Send-xyOpsEmail -To "user@domain.com" -Subject "Reports" -Body "Please see attached." -Attachments './report1.pdf','./report_final.pdf'

API Key Required, see Setting Up Email API Key

File & Data Management

---

Send-xyOpsTable

Send-xyOpsTable -Rows <array> -Header <array> [-Title <string>] [-Caption <string>]

.SYNOPSIS
	Sends tabular data for display in the xyOps UI.

.DESCRIPTION
	Renders a data table on the Job Details page in xyOps.

.PARAMETER Rows
	Array of rows, where each row is an array of column values.

.PARAMETER Title
	Optional title displayed above the table.

.PARAMETER Header
	Optional array of header column names.

.PARAMETER Caption
	Optional caption displayed under the table.

Examples:

# Provide data inline
Send-xyOpsTable -Rows @(@("192.168.1.1", "Server1", 100), @("192.168.1.2", "Server2", 200)) -Header @("IP", "Name", "Count")

# Setup data before sending
$rows = @(
	@("192.168.1.1", "Server1", "Online"),
	@("192.168.1.2", "Server2", "Offline")
)
Send-xyOpsTable -Rows $rows -Header @("IP", "Name", "Status") -Title "Server Status"

UI Display Functions

---

Send-xyOpsHtml

Send-xyOpsHtml -Content <string> [-Title <string>] [-Caption <string>]

.SYNOPSIS
	Sends custom HTML content for display in xyOps.

.DESCRIPTION
	Renders custom HTML on the Job Details page. Only basic HTML elements are allowed.

.PARAMETER Content
	The HTML content to display.

.PARAMETER Title
	Optional title displayed above the content.

.PARAMETER Caption
	Optional caption displayed under the content.

Examples:

$html = "<h3>Summary</h3><ul><li>Total: <b>1000</b></li></ul>"
Send-xyOpsHtml -Content $html -Title "Results"

UI Display Functions

---

Send-xyOpsText

Send-xyOpsText -Content <string> [-Title <string>] [-Caption <string>]

.SYNOPSIS
	Sends plain text content to display in xyOps in a separate textbox.

.DESCRIPTION
	Renders plain text on the Job Details page with formatting preserved.

.PARAMETER Content
	The plain text content to display.

.PARAMETER Title
	Optional title displayed above the content.

.PARAMETER Caption
	Optional caption displayed under the content.

Examples:

$logContent = Get-Content "/var/log/app.log" -Raw
Send-xyOpsText -Content $logContent -Title "Application Log"

UI Display Functions

---

Send-xyOpsMarkdown

Send-xyOpsMarkdown -Content <string> [-Title <string>] [-Caption <string>]

.SYNOPSIS
	Sends Markdown content for display in xyOps.

.DESCRIPTION
	Renders Markdown on the Job Details page (converted to HTML).

.PARAMETER Content
	The Markdown content to display.

.PARAMETER Title
	Optional title displayed above the content.

.PARAMETER Caption
	Optional caption displayed under the content.

Examples:

$md = "## Results`n- **Success**: 98%`n- **Failed**: 2%"
Send-xyOpsMarkdown -Content $md -Title "Summary"

UI Display Functions

---

Setting Up Cache Bucket

In order to to use the cache and bucket management functionality built into this plugin, the following setup steps required.

Create Cache Bucket

1. In the menu pane under the Scheduler section, navigate to Buckets.
2. Click New Bucket...
3. Provide a Bucket Title as something recognizable, such as Cache.
4. Click Create Bucket
5. Take note of the new bucket ID as it will be used in a later step.

Create API Key for managing buckets

* Note that this API Key will also be used for the other API access helper functions.

1. In the menu pane under the Admin section, navigate to API Keys.
2. Click New API Key...
3. Provide an App Title as something recognizable, such as Bucket Management.
4. Modify the Privileges so that it only includes Edit Buckets.
5. Click Create Key
6. At this point, you'll see a pop-up saying NEW API KEY CREATED. This is the ONLY time you will have access to this new API key secret, so click Copy to Clipboard and paste it somewhere as it will be used in a later step.

Create Secret Vault

1. In the menu pane under the Admin section, navigate to Secrets.
2. Click New Vault...
3. Provide a Secret Vault Title as something recognizable, such as Read/Write Buckets.
4. For Plugin Access, select PowerShell from the list.
5. Under Secret Variables, click New Variable...
6. Enter XYOPS_CACHE_BUCKET_ID for the Variable Name for the cache bucket ID.
7. Paste the bucket ID of the bucket created in previous steps into the Variable Value.
8. Click Add Variable
9. Under Secret Variables, click New Variable...
10. Enter XYOPS_BUCKET_API_KEY for the Variable Name for the bucket management API key secret.
11. Paste the API key value copied from the new API key created in previous steps into the Variable Value.
12. Click Add Variable
13. Click Create Vault

NOTE: If you use a different different variable name from the defaults, you'll need to make sure they're set properly every time you use the event plugin.

---

Setting Up Email API Key

In order to to use the Send-xyOpsEmail function built into this plugin, the following setup steps required.

Create API Key for sending emails

1. In the menu pane under the Admin section, navigate to API Keys.
2. Click New API Key...
3. Provide an App Title as something recognizable, such as Send Email.
4. Modify the Privileges so that it only includes Send Emails.
5. Click Create Key
6. At this point, you'll see a pop-up saying NEW API KEY CREATED. This is the ONLY time you will have access to this new API key secret, so click Copy to Clipboard and paste it somewhere as it will be used in a later step.

Create Secret Vault

1. In the menu pane under the Admin section, navigate to Secrets.
2. Click New Vault...
3. Provide a Secret Vault Title as something recognizable, such as Send Email API.
4. For Plugin Access, select PowerShell from the list.
5. Under Secret Variables, click New Variable...
6. Enter XYOPS_SENDEMAIL_API_KEY for the Variable Name for the Send Email API key secret.
7. Paste the API key created in previous step into the Variable Value.
8. Click Add Variable
9. Click Create Vault

NOTE: If you use a different different variable name from the defaults, you'll need to make sure they're set properly every time you use the event plugin.

---

Data Collection

This plugin DOES NOT collect any data or user information.

---

Author: Nick Dollimount

Contributors: Tim Alderweireldt