Hi and welcome to the Community @nadavaha!  

Could there be an issue with the API perhaps? I know that New Relic has a number of different API keys available so it may be that the wrong one has been used here. See: https://docs.newrelic.com/docs/apis/intro-apis/new-relic-api-keys/

It looks like it’s the User Key type that you’d need.

Can you try regenerating the key and then reconnect the New Relic app account using that new API key to see if that sorts it? 

Keen to help get to the bottom of this so please keep us updated on how you get on with that!

Hi Sam, 

Thanks for your reply.

I have tried all 3 types and sadly not one of them worked… i really am clueless why none of them worked while I’m the admin.

Can you please try and test it on your end, register a free account in New relic, create an API and try to ZAP from google analytics to new relic. Will be interesting to find out if you managed or not.

Hi there @nadavaha,

I’m jumping in to see if I can help!

I tried connecting New Relic to Zapier and I was able to successfully connect my account using the Rest API key. Here’s how I achieved it:

(view larger)

(view larger)

(view larger)

Hopefully, this helps!

YEP Perfect - i didnt know that the REST API key on the right side brings you o somewhere else.. works !!

I think this solution no longer works. Because Newrelic REST API key was deactivated in March 2024:

So, I keep getting this error when Trying to connect new relic in a recent created zapier account:

I already tried with user key, ingest licence, ingest browser and nothing seems to work.

Error:
 

We hit an error adding your new account

authentication failed: The app returned `{"message":"Could not retrieve a list of accounts."} What happened: Executing authentication.test with bundle {"message":"Could not retrieve a list of accounts."} Console logs: ` as error, which we cannot read.

1. Make sure you click "Allow" or "Accept" on the permission popup
2. Double check your Account has the correct permissions
3. Check out our help docs for more information

Thanks so much for bringing this to our attention @autow! 

With the older REST API Keys now being deprecated and the User API Keys not being accepted this definitely seems like it’s a bug. I’d recommend reaching out to our Support team about this here as they’ll be able to dig into the logs for your Zap and can open up a bug report so that this can be investigated further. 

Sorry to not have a more immediate solution or workaround to suggest. Please do keep us updated on how you get on with them! 

Any news? Workarounds here?

Thanks for reaching out here @tickets. I did some checking and found the bug report that was opened up for these issues with the REST API Keys now being deprecated. So I’ve gone ahead and ensured that everyone here has been added to the list of folks being affected.

I can’t make any promises as to when it will be resolved but we’ll definitely send out an email notification to you all the minute it’s been resolved. There aren’t any workarounds reported at the moment but we’ll follow up here to share details of any we come across in the meantime.

Thanks in advance for everyone’s patience while this is being worked on. We’ll keep you posted on any updates here!