Skip to content
Notis

Connect Captions to New relic

When something happens in Captions, Notis takes the next step in New relic. Describe what you want in plain English, or start from one of the examples below.

When this happens · Trigger

Do this · Action

Examples

Ways Notis can move work from Captions to New relic

View example

Check the Captions API app inventory

On a scheduled or operational signal, retrieve New Relic applications related to your Captions integration so you can quickly confirm which services are being monitored.

View example

Review Captions alert policies weekly

Have Notis retrieve New Relic alert policies on a weekly cadence, making it easier to spot whether monitoring for Captions-related services is still organized as expected.

View example

Audit notification channels for Captions

When an operations check is requested, retrieve configured New Relic notification channels so the team can verify that alert destinations are current.

View example

Check Captions browser apps monthly

Retrieve New Relic browser applications monthly to keep frontend monitoring for Captions-related experiences visible and easy to review.

View example

Look up conditions for a Captions alert policy

When an alert policy is under review, retrieve its New Relic conditions so the operator has the relevant configuration detail close at hand.

View example

Keep a Captions policy watchlist

Retrieve New Relic alert policies on a recurring schedule, creating a dependable watchlist for whoever owns reliability follow-up on Captions services.

View example

Inventory New Relic apps during Captions service onboarding

When a service onboarding checklist reaches its monitoring step, retrieve New Relic applications to help the owner confirm what is already registered.

View example

Review Captions alert channel readiness

On a recurring cadence, retrieve New Relic channels for a human review of whether notification routes still match the team's current operating setup.

View example

Fetch policy context for a Captions incident

When an incident workflow requests context, retrieve New Relic alert policies to help responders orient themselves before deciding what to inspect next.

Supported Triggers and Actions

Notis builds workflows that link Captions to New relic. A trigger fires from one place; an action lands in another.

Captions triggers

New relic actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Create Alert Notification Channel

Tool to create an alert notification channel. use when you need to register a new endpoint (email, webhook, etc.) for alert notifications.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Create Alert Policy

Tool to create an alert policy. use when you need to programmatically set up a new alert policy in new relic.

ActionInstant

Delete alert policy

Tool to delete an existing alert policy via rest api. use when you have the policy id and want to remove it via new relic's rest api. use after confirming the policy id exists.

ActionInstant

Get Alert Channels

Tool to retrieve a list of alert notification channels. use when you need to list all configured channels after verifying your api key.

ActionInstant

Get Alert Conditions

Tool to retrieve alert conditions for a specified policy. use after you have the policy id.

ActionInstant

Get Alert Policies

Tool to retrieve a list of alert policies. use when you need to list existing alert policies with optional filtering and pagination.

ActionInstant

Get Applications

Tool to retrieve a list of new relic applications. use when you need to list all applications or filter by name, host, or ids after authenticating your api key.

ActionInstant

Get Browser Applications

Tool to list new relic browser applications. use when you need to retrieve all browser applications or filter by name after authenticating your api key.

ActionInstant
Trigger Types

Four ways to start an automation.

A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.

Integration triggers

Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.

New Notion pageStripe chargeCalendar event

Webhook triggers

A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.

Any HTTP POSTCustom backendIoT event
Works with
ZapierPipedream
Most used

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only
Coming soon

Database triggers

Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.

Row insertedValue > limitQuery match
Why AI automation

Classic automation breaks. AI adapts.

Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.

Classic automationAI automation
Cost
$ · pay per run
$$ · AI models per run
Reliability
Breaks on schema change
Adapts to format changes
Setup
Click 8 dropdowns
Describe it in English
Handles fuzzy
Hard-coded fields only
Reads intent, summarises
Human in loop
Bolted on
Built in · approval inbox
Maintenance
You own every break
Self-heals · we own it
Ease of use

Describe it. Notis builds it.

Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.

Notis

You · in the Notis Builder

NEW

“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”

Notis built this automation:

TriggerRow added to "Q4 OKRs"
Condition✦Status = "Blocked"
AI step✦Summarise the blocker in plain English
ActionDM the row owner with summary
Timeout✦No reply in 24h → ping you
Observability

Watch every run.

Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.

  • Full run history with inputs, outputs and traces
  • Replay any run with edited inputs
  • Approval inbox, confirm via chat in one tap
  • Audit logs for compliance teams

Automations

Inbox

All12Manager5Telegram1Messages0Whatsapp2Email4Slack8

Migrate background jobs to a durable queue You can cancel it through Stripe

3 days

Notis v3 release update This one’s v3: Notis Manager (desktop app with …

8 days

Add multi-tenant RBAC User initiates a voice call

13 days

Draft pricing v (tiers, limits, overages) and sanity-check margins

2 weeks

Verify analytics events for new features That’s a really interesting automat…

1 month

Everything in the box.

Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.

AI in the middle

Every step can include an LLM call: summarise, classify, extract, rewrite.

Full observability

Every run, every step, every input, all replay-able from Mission Control.

Human in the loop

Pause for approval. Notis pings you in chat with one-tap approve.

Self-healing

When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.

Related pairs

More ways to connect Captions and New relic

Connect any two apps with Notis in the middle.

Captions and New relic, or any other combination from 1,000+ integrations.

When this happens · Trigger

Do this · Action

Save your first hour today.

7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business New relic.