New Relic Insights Zapier integrationAutomate New Relic Insights with Zapier.
New Relic Insights Zapier integration: 0 triggers, 1 action, no search step. Zapier can send a custom event into New Relic Insights each time something happens in another app, so business moments sit next to the metrics you already track there.
Verified Trustpilot reviews · AI, automation & growth agency
What the New Relic Insights Zapier integration actually does
New Relic Insights is an analytics platform that gathers metrics from your live production software and turns them into readings on your business, customers and applications. On Zapier it works in one direction: a Zap (an automation you set up once: one trigger, then one or more actions) takes an event from another app and records it in Insights as a custom event.
Three results worth building with New Custom Event. Sign-ups on the chart: each new form submission becomes an event, so you can line up interest in your offer with what your software was doing that day. Sales activity in one place: a new contact in your CRM is recorded too, next to the technical metrics. A log of anything that lives in a spreadsheet: a new row becomes an event you can query later.
What Zapier does not do for this app. New Relic Insights has no trigger on Zapier, so a Zap can never start from something that happens inside Insights. The Zap always begins in another app, with one of that app's triggers. There is no search step either, so a Zap cannot read back a value stored in Insights. One action, one direction: into New Relic Insights.
Because the trigger belongs to another app, how fast an event arrives depends on that app's trigger, not on New Relic Insights. Check its type on that app's Zapier page before you count on speed.
If you are weighing automation platforms more broadly, see our Zapier alternatives roundup.
Zapier vocabulary in one minute
The Zapier words on this page, each one explained once in plain English.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run every time that trigger event happens.
- Trigger
- The event in an app that starts the Zap. With New Relic Insights, the trigger always comes from another app.
- Action
- What the Zap does once it has started: the step that writes, sends or moves something, here a custom event into Insights.
- Task
- The unit Zapier bills: one action your Zap completes successfully. The count on your plan is a count of those.
- Polling trigger
- A trigger Zapier checks on a timer: it asks the app for new items at a fixed interval and keeps only the ones it has not seen.
- Instant trigger
- A trigger the app reports itself: it calls Zapier the moment the event happens, so nothing waits for the next check.
- Filter
- A step that lets the Zap carry on only when what arrived meets the condition you set, and stops it otherwise.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A second action, a filter or a search makes it one, and it then needs a paid plan.
What a New Relic Insights Zap really costs
New Relic Insights is not a premium app, so it works from the free plan. Each event you send is one task.
- Free plan100 tasks a month, unlimited two-step Zaps
- Per event sentOne task
- Failed actionNot counted against the plan
- Premium appNo, it works on the free plan
Zapier counts a task each time an action completes, so every custom event recorded in Insights costs one. The trigger in the other app costs nothing, and neither do Zapier's checks for new items. An action that fails is not counted. The free plan gives 100 tasks a month and unlimited Zaps, each limited to two steps: one trigger, one action. That fits a Zap that sends one event per new item. A filter in front of it, or a second action, needs a paid plan. The grid below only matters if the trigger you pick in the other app is a polling trigger.
Connect your New Relic Insights account to Zapier
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. A connection is your New Relic Insights account linked to Zapier once, then reused by every step that uses it.
- 02
Pick New Relic Insights
Search New Relic Insights in the dialog, select it and click Add connection. You need an account on the app, plus read or write access on anything you do not own yourself and want the Zap to touch.
- 03
Sign in and grant access
Sign in to New Relic Insights in the tab that opens and grant Zapier access to the account. The connection is then ready for the New Custom Event step of every Zap you build, and you will still need a connection to the app whose trigger starts the Zap.
Your first Zap: selected form submissions as events
GoalEvery form submission that meets a condition you set is recorded in New Relic Insights as a custom event of the type you choose.
- 01
Build: pick the trigger
Create a Zap and choose your form tool as the starting app, with its event for a new submission. New Relic Insights has no trigger, so the Zap starts here.
- 02
Test the trigger
Run the test: Zapier brings back the three most recent submissions of the connected account. Read the fields you get before setting up the action that follows.
- 03
Add the filter
From the plus icon, add Filter and set the field to look at, the rule and the value to compare with. A filter makes the Zap multi-step, so it needs a paid plan.
- 04
Add New Custom Event
Add the New Relic Insights action New Custom Event, select your connection, type the Event Type you chose and set Copy Trigger Fields.
- 05
Test, then publish
Test the action once and check the event in Insights. Then click Publish to switch the Zap on. Submissions made before that moment are not sent.
The New Relic Insights action on Zapier
New Relic Insights gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.
New Custom Event
ActionIn Zapier“Create a new custom event inside New Relic Insights for tracking.”
Records a new custom event in New Relic Insights from whatever started the Zap, so you can track it alongside your other data there.
When a New Relic Insights Zap breaks
Zapier attaches no help article to New Relic Insights and lists no limit of its own for it. The cases below come from how Zapier works in general.
Four situations to know before switching a Zap on. For other problems, see our Zapier troubleshooting guide.
Past items are not sent
A Zap only reacts to what happens after it is switched on. Items created before that in the other app never become events; moving that history is a separate job.A Zap that keeps setting itself off
As a general precaution: a Zap that writes into the very place its own trigger watches can start itself again and again, and burn through your tasks fast.A big batch held back
When the trigger suddenly returns a huge batch, after a bulk import or a migration for example, Zapier's flood protection can hold it back.The same item, one event
On a polling trigger, Zapier keeps track of what it has already seen, so the same item does not start the Zap twice and does not send two events.
Need help automating New Relic Insights with Zapier?
A person reads every message.
