Connect Azure DevOps and New Relic to unlock the power of automation
- No credit card required
- Free forever for core features
- 14-day trial for premium features and apps
How Zapier works
Zapier makes it easy to integrate Azure DevOps with New Relic - no code necessary. See how you can get setup in minutes.
Choose a trigger
A trigger is the event that starts your Zap—like a "Completed Build" from Azure DevOps.
Add your action
An action happens after the trigger—such as "New Deployment" in New Relic.
You’re connected!
Zapier seamlessly connects Azure DevOps and New Relic, automating your workflow.
Supported triggers and actions
Zapier helps you create workflows that connect your apps to automate repetitive tasks. A trigger is an event that starts a workflow, and an action is an event a Zap performs.
- Build DefinitionRequired
- Build Status
- ProjectRequired
Try ItTriggerInstant- ProjectRequired
- Repository
- Branch
Try ItTriggerInstant- ProjectRequired
- Area Path
- Work Item Type
Try ItTriggerInstant- ProjectRequired
- Build DefinitionRequired
ActionWrite
- ProjectRequired
- PathRequired
Try ItTriggerInstant- ProjectRequired
- Area Path
- Work Item Type
- Contains StringRequired
Try ItTriggerInstant- ProjectRequired
- Area Path
- Work Item Type
- Changed Field
Try ItTriggerInstant- ProjectRequired
- TypeRequired
- TitleRequired
- Area
- Iteration
- Assigned To
- Description
ActionWrite
Zapier is the automation platform of choice for 87% of Forbes Cloud 100 companies in 2023
93%
Customers who say using Zapier has made them better at their job
25m
Customers have created over 25 million Zaps on the platform
6 mins
The average user takes less than 6 minutes to set up a Zap
Connect Azure DevOps and New Relic to integrate crucial parts of your business
With Zapier, you can integrate everything from basic data entry to end-to-end processes. Here are some of the business-critical workflows that people automate with Zapier.
Automate your lead management and improve conversions
Create more impactful campaigns with automation
Provide world-class support with a little help from automation
Automate your way to actionable, up-to-date data
Resolve incidents faster with automation
Frequently Asked Questions about Azure DevOps + New Relic integrations
New to automation with Zapier? You're not alone. Here are some answers to common questions about how Zapier works with Azure DevOps and New Relic
How can I set up a trigger in Azure DevOps to alert New Relic of a deployment?
To set up a trigger in Azure DevOps that alerts New Relic of a deployment, you'll need to create a service hook. First, go to the Azure DevOps project settings and choose 'Service hooks.' Add a subscription and select the event type related to deployments (e.g., 'Release deployed'). Configure the action to send the necessary data to New Relic's webhook URL.
What actions can be triggered in New Relic from an Azure DevOps event?
Azure DevOps events such as completed builds or releases can trigger actions in New Relic such as creating incidents, sending deployment change notes, or updating dashboards. You can set these up through webhooks or third-party connectors that are configured in both platforms.
Is it possible to automatically update New Relic dashboards based on Azure DevOps activities?
Yes, you can configure webhooks in Azure DevOps that update specific components of your New Relic dashboards. When certain build or release events occur in Azure DevOps, corresponding updates or metrics can be pushed to New Relic's dashboards using the API.
How do we ensure secure communication between Azure DevOps and New Relic during integration?
To ensure secure communication between Azure DevOps and New Relic during integration, it's crucial to use HTTPS for webhooks and API calls. Additionally, using authentication tokens provided by New Relic and configuring IP whitelisting for further security are recommended best practices.
Can deployment notes from Azure DevOps be sent automatically to New Relic?
Yes, by setting up service hooks in Azure DevOps, you can automatically send deployment notes to New Relic. Choose the appropriate deployment event as your trigger and configure the webhook URL with the necessary payload information required by New Relic.
What should we do if triggers from Azure DevOps aren't activating actions in New Relic?
If triggers from Azure DevOps aren't activating actions in New Relic consistently, check whether the webhook connections are correctly configured. Ensure all URLs are correct and that any required authentication keys are accurately implemented. It might also help to check for any reported downtime on either platform.
Are there limits on the number of interactions between Azure DevOps and New Relic via integrations?
There aren't strict limits on interactions per se; however, both platforms have their rate limitations when it comes to API requests. It's important to review these limits within each platform's documentation page so that your integration remains responsive without disruption.
