Templates provide pre-configured workflows for common scenarios—sending reports to Slack, rolling back deployments, resizing EC2 instances, and more. Deploy in minutes, then customize to match your team's process.
Why use templates? Get started faster : Deploy working automations in minutesFollow best practices : Use proven patterns and error handlingLearn by example : See how actions connect and data flowsReduce errors : Start with tested configurationsBefore you begin Most templates need credentials and integrations:
AWS templates : AWS credentials with permissions (EC2, API Gateway, Systems Manager, or SQS).Slack notifications : Slack app with bot token and channel access.All templates : New Relic account and entity GUIDs (unique identifiers for monitored resources).Tip Don't have credentials yet? Browse templates first. Set up credentials before deploying.
Deploy a template Find the right template Browse the template library . Each shows what it does, when to use it, requirements, and how it works.
Go to one.newrelic.com > All Capabilities > Workflow Automation
Select Use a Template
Choose your template
Fill in inputs (credentials, entity GUIDs, queries, channels)
Select Deploy
The workflow is now active and ready to use.
Test and verify Test before production use:
Trigger manually (see Start workflows on demand )
Monitor execution in run history
Check outputs (Slack messages, AWS changes, logs)
Review errors, adjust configuration
Important Test in non-production first. Some templates change infrastructure. Validate before production use.
Customize your template Modify workflows after deployment:
Add conditional logic : Skip steps based on conditionsChain templates : Use outputs as inputs for other workflowsAdjust notifications : Change formats, recipients, channelsAdd custom actions : Include HTTP requests or data transformationsSee Create your own workflow for details.
Workflow automation templates Send report to Slack What it does:
Queries New Relic data with NRQL (New Relic Query Language), formats results as CSV, and posts to Slack.
When to use it:
Automate regular reports: daily performance summaries, weekly error rates, hourly transaction volumes, or custom metrics.
What you'll need:
Runs your NRQL query Converts results to CSV Posts to Slack Logs status API gateway rollback What it does:
Detects deployment issues and rolls back AWS API Gateway to the previous configuration—after getting team approval.
When to use it:
Revert bad deployments that spike errors, break integrations, or cause incidents. Safety net for high-risk changes.
What you'll need:
AWS : API Gateway and Systems Manager permissions
Slack : App for notifications and approval
New Relic : API Gateway entity GUID
How it works:
Fetches deployment history
Correlates with current issue
Requests Slack approval
Executes rollback if approved
Notifies team and cleans up
Important Manual approval required. Won't rollback without team approval via Slack reactions.
EC2 instance management What it does:
Automatically resizes EC2 instances when CPU or resources spike.
When to use it:
Handle CPU spikes during traffic surges, scale instances hitting limits, manage unpredictable load patterns.
What you'll need:
AWS : EC2 and Systems Manager permissions
Slack : App for notifications and approval
New Relic : Alert condition monitoring EC2, AWS CloudWatch Metric Streams , EC2 monitoring integration
Tip Use CloudWatch Metric Streams. Provides complete AWS metrics coverage, including custom namespaces.
How it works:
Gets alert and identifies instance Requests Slack approval Creates automation document Stops, modifies, and starts instance Updates progress and cleans up JSON parsing What it does:
Fetches JSON from external status pages, parses component health, logs to New Relic.
When to use it:
Monitor third-party dependencies (payment processors, auth providers, data services), correlate outages with your issues, create unified dashboards.
What you'll need:
Fetches JSON from endpoint
Parses component health
Categorizes operational status
Logs to New Relic with filters
Tip Schedule every 5-15 minutes to build historical view of third-party reliability.
Deployment rollback What it does:
Monitors application health after deployment, sends notifications when issues arise.
When to use it:
Watch new releases post-deployment, detect production-only issues, trigger rollback workflows on health degradation.
What you'll need:
Monitors health every 1-5 minutes
Evaluates alert severity
Sends notifications (SQS/webhook) when degraded
Logs all health checks
Continues until stopped or recovered