Connect Abstract to Castingwords

When something happens in Abstract, Notis takes the next step in Castingwords. 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 Abstract to Castingwords

View example

Validate a Media Link and Order Its Transcript

Check an incoming media URL with Abstract, then start a CastingWords transcription order when the link is accessible.

View example

Order Transcripts for Approved Interview Recordings

Accept a webhook request for an approved interview recording and send its accessible media URL to CastingWords.

View example

Order Transcription After a Consent Check

Use a webhook request that includes a consent decision and media URL to submit only approved recordings for transcription.

View example

Add Timestamps to a Completed Transcript

Submit an upgrade request for a completed CastingWords file when a webhook supplies its file identifier and requests timestamps.

View example

Request an Editing Upgrade for a Finished File

Place a user-requested upgrade for a completed CastingWords file, using the file identifier and requested upgrade supplied by the webhook.

View example

Check Your CastingWords Prepay Balance on a Schedule

Run a scheduled balance check so the current CastingWords prepay funds are easy to review before new orders.

View example

Review Available Transcription Services on a Schedule

Retrieve the current CastingWords SKU list periodically so service options and pricing are available before planning orders.

View example

Check the Registered CastingWords Webhook URL

Retrieve the currently registered webhook URL on a schedule and report it for a quick configuration review.

View example

Register a Transcript Notification Endpoint

Register the endpoint supplied in a webhook request so CastingWords can post transcript completion notifications to your service.

Supported Triggers and Actions

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

Abstract triggers

Castingwords actions

Recurring trigger

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

TriggerScheduled

Cancel and Refund Audio File

Cancels an audio file order and issues a refund if eligible.

ActionInstant

Webhook trigger

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

TriggerInstant

Get Prepay Balance

Retrieves the current account prepay balance.

ActionInstant

Get registered webhook URL

Retrieves the webhook URL registered for account notifications.

ActionInstant

Get Transcript

ActionInstant

Order Transcript

Creates a transcription order for audio or video files.

ActionInstant

Order Upgrades

Orders an upgrade for a completed audio transcription.

ActionInstant

Register Webhook

Registers a webhook to receive event notifications.

ActionInstant

List Available SKUs

Lists available transcription services and their prices.

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.