Use a template to create a Workflow automation

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:

• Slack: Bot token with channel post permissions

• New Relic: Account access and valid NRQL query

  How it works:

1. Runs your NRQL query
2. Converts results to CSV
3. Posts to Slack
4. Logs status

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:

1. Fetches deployment history

2. Correlates with current issue

3. Requests Slack approval

4. Executes rollback if approved

5. Notifies team and cleans up

   Importante

   Manual approval required. Won't rollback without team approval via Slack reactions.

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

  Dica

  Use CloudWatch Metric Streams. Provides complete AWS metrics coverage, including custom namespaces.

  How it works:

1. Gets alert and identifies instance
2. Requests Slack approval
3. Creates automation document
4. Stops, modifies, and starts instance
5. Updates progress and cleans up

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:

• API access: Public status endpoint returning JSON

• New Relic: Account for logging

  How it works:

1. Fetches JSON from endpoint

2. Parses component health

3. Categorizes operational status

4. Logs to New Relic with filters

   Dica

   Schedule every 5-15 minutes to build historical view of third-party reliability.

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:

• New Relic: Entity GUID for monitoring

• Notifications (choose one or both): AWS SQS permissions or HTTP webhook endpoint

  How it works:

1. Monitors health every 1-5 minutes

2. Evaluates alert severity

3. Sends notifications (SQS/webhook) when degraded

4. Logs all health checks

5. Continues until stopped or recovered

   Dica

   Use with change tracking to correlate issues with deployments.

What it does:

Runs SQL queries against New Relic's data catalog using NRLens (advanced query tool).

When to use it:

Complex analysis beyond NRQL: multi-table joins, statistical analysis, custom reports combining metrics/events/logs.

What you'll need:

• NRLens: Credentials for SQL Query Gateway

• New Relic: Organization and account IDs

  How it works:

1. Connects to NRLens

2. Executes SQL

3. Retrieves results

4. Logs to New Relic

5. Supports scheduling

   Dica

   NRLens extends NRQL. Use NRQL for real-time queries, NRLens SQL for complex analytical workloads.