Connect ActiveMerge to Deepgram

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

When this happens · Trigger

Do this · Action

Build an automation Browse examples

Examples

Ways Notis can move work from ActiveMerge to Deepgram

View example

Transcribe an audio file linked from an ActiveMerge workflow

Send a publicly accessible audio URL from an ActiveMerge workflow to Deepgram and get a text transcript for review.

View example

Get a concise summary of audio connected to ActiveMerge

Use Deepgram to summarize a publicly accessible audio file referenced by an ActiveMerge workflow.

View example

Find the main topics in audio from an ActiveMerge process

Pass an accessible audio URL from an ActiveMerge workflow to Deepgram to transcribe it and detect discussed topics.

View example

Review Deepgram speech model options on a schedule

Get a scheduled inventory of public Deepgram speech-to-text models to inform an audio workflow that uses ActiveMerge.

View example

Look up a Deepgram model before an audio workflow review

Retrieve detailed metadata for a specified Deepgram model ID when an ActiveMerge-linked process prompts a model review.

View example

Review public Deepgram text-to-speech voices regularly

Schedule a recurring retrieval of Deepgram's public TTS voice model metadata for teams planning spoken outputs from ActiveMerge materials.

View example

Create speech from text prepared in an ActiveMerge workflow

Turn supplied text from an ActiveMerge process into natural-sounding speech with Deepgram Text-to-Speech.

View example

Review Deepgram projects on a recurring schedule

Get a scheduled list of Deepgram projects to keep audio operations visible alongside ActiveMerge document workflows.

Supported Triggers and Actions

Notis builds workflows that link ActiveMerge to Deepgram. A trigger fires from one place; an action lands in another.

ActiveMerge triggers

Deepgram actions

Recurring trigger

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

TriggerScheduled

Get Public Models

Retrieves metadata for public speech-to-text and text-to-speech models.

ActionInstant

Webhook trigger

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

TriggerInstant

Get Model by ID

Retrieves metadata for a speech-to-text or text-to-speech model.

ActionInstant

List Deepgram Projects

Lists all projects.

ActionInstant

Get Project Usage Summary

Retrieves aggregated usage statistics for a project.

ActionInstant

Get Project Balance

Retrieves a project's balance in the provider's native units.

ActionInstant

List Project Scopes

Lists all permission scopes for a project.

ActionInstant

Get Project Billing Breakdown

Returns a project's dated billing entries in USD.

ActionInstant

Transcribe Pre-recorded Audio

Transcribes a pre-recorded audio file into text.

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.

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.