actions-marketplace-validations/New Relic Application Deployment Marker
Apply a New Relic application change event marker to an application that is monitored by New Relic. **Important Note:** Input requirements for this action vary depending on the `commandType` chosen. Please refer to the detailed documentation in the README for specific mandatory fields for each scenario.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Maintainedlast commit Oct 7, 2025
- License
- Apache 2.0
Pinned Snippet
uses: actions-marketplace-validations/newrelic_deployment-marker-action@d88a59ea8f713ad6935e60de27273157790b1e3b # no releases — HEAD as of 2026-07-10tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| apiKey | Your New Relic User API Key. | yes | — |
| guid | Your New Relic entity GUID. This entity GUID should be for the entity you are tracking. | no | — |
| version | Custom version information to add to the deployment marker - e.g. the latest tag. | no | — |
| region | The geographical region for your New Relic account - US or EU. Default: US | no | US |
| description | Description stored with the deployment. Default: <none> | no | — |
| changelog | Change log string stored with the deployment. Default: <none> | no | — |
| commit | Commit for the deployment. | no | — |
| deeplink | Deep link referencing the deployment. | no | — |
| deploymenttype | The type of deployment this is conducting. | no | BASIC |
| user | The user creating the deployment. Default: `github.actor` | no | ${{ github.actor }} |
| groupid | Group Id used to link deployments together. | no | — |
| commandType | This field lets you track any change event. To use this new API mutation, you must set it to "changeTrackingCreateEvent". | no | changeTrackingCreateDeployment |
| category | The category of the change event. For a list of supported categories, [view our docs](https://docs.newrelic.com/docs/change-tracking/change-tracking-events/#supported-types) | no | — |
| type | The type of the change event. For a list of supported types, [view our docs](https://docs.newrelic.com/docs/change-tracking/change-tracking-events/#supported-types) | no | — |
| featureFlagId | The ID of the feature flag associated with the change event. This is required if the commandType is "changeTrackingCreateEvent" and the category is "Feature Flag". | no | — |
| customAttributes | Represents key-value pairs of custom attributes in JavaScript object format. Attribute values can be of type string, boolean, or number. We store JavaScript number values to either Java long or double values. The main difference between JavaScript object format vs. JSON is that keys are not enclosed in quotes. For more information on limitations, [see our docs](https://docs.newrelic.com/docs/change-tracking/change-tracking-graphql/). | no | — |
| entitySearch | Specify the entity to associate with the change tracking event via query. | no | — |
| shortDescription | This field allows you to add your own context to help you quickly identify the change events sent to our system. This field should contain a concise description of the change suitable for showing in various parts of New Relic One. In the marker flag, shown when hovering over the pinhead of a "Changes" marker on a chart. In the "Activity stream" panels. If this field is left blank sensible defaults will be shown instead. | no | — |
| timestamp | The start time of the change tracking event as the number of milliseconds since the Unix epoch. Defaults to now. | no | — |
| validationFlags | Validation flags for the change event (e.g., "[ALLOW_CUSTOM_CATEGORY_OR_TYPE], [FAIL_ON_FIELD_LENGTH], [FAIL_ON_REST_API_FAILURES]"). Only applicable if commandType is "changeTrackingCreateEvent". | no | — |
Outputs
| name | description |
|---|---|
| deploymentId | The id of the deployment |