Connect Agile CRM to Castingwords

When something happens in Agile CRM, 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 Agile CRM to Castingwords

View example

Transcribe an Agile CRM call recording

Send a call recording URL from an Agile CRM workflow or request to Castingwords for transcription, then keep the result tied to the relevant sales conversation.

View example

Check Castingwords balance before a CRM call order

Before ordering a transcript for an Agile CRM call, check the account's current Castingwords prepay balance and report whether funds are available.

View example

Review Castingwords prepay balance each morning

Run a scheduled balance check and send the current Castingwords prepay balance in a Notis run report for planning upcoming Agile CRM call transcriptions.

View example

Review transcription services before ordering a CRM call

When a CRM recording is ready for transcription, retrieve Castingwords' available SKUs so you can review service options and pricing before ordering.

View example

Transcribe a recording when a deal is ready

Start a Castingwords order when a deal is marked ready in a Notis webhook request that includes an accessible recording URL and deal context.

View example

Fetch a completed transcript for a CRM conversation

When a transcription is complete, retrieve the transcript in the requested format and report it with the Agile CRM contact or deal context supplied in the request.

View example

Add timestamps to a completed deal transcript

Order a timestamp upgrade for a completed Castingwords audio file when a webhook request identifies the file and its Agile CRM deal context.

View example

Register a webhook for transcript completion

Register a service endpoint to receive Castingwords transcript-complete notifications, so completed recordings connected to Agile CRM can prompt follow-up.

View example

Verify the transcript notification endpoint weekly

Retrieve the registered Castingwords webhook URL on a schedule and report it so you can confirm the endpoint used for transcript notifications.

Supported Triggers and Actions

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

Agile CRM 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

Retrieves a completed audio transcription in the requested format.

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.