Connect Fireflies to Cloudinary
When something happens in Fireflies, Notis takes the next step in Cloudinary. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Do this · Action
Ways Notis can move work from Fireflies to Cloudinary
Create a client folder for every completed meeting
After a Fireflies transcript completes, create a Cloudinary folder named for the client and meeting series when it does not already exist.
Find the right Cloudinary root folder for each meeting series
Use transcript details to look up the matching Cloudinary root folder and report the correct destination for meeting media.
Find Cloudinary assets mentioned in a completed call
Search Cloudinary by contextual metadata named in a Fireflies transcript and return the relevant assets for follow-up.
List assets in the folder tied to a completed meeting
After transcription, identify the relevant Cloudinary folder and list the assets stored directly inside it for review.
Inspect a Cloudinary asset referenced in a call
Extract a public ID mentioned in a Fireflies transcript and retrieve the asset's full Cloudinary details.
Verify a Cloudinary asset ID mentioned in meeting notes
Use a completed transcript to locate an asset ID and retrieve the corresponding Cloudinary resource for confirmation.
Summarize Cloudinary tags related to a completed call
Extract the project context from a Fireflies transcript and retrieve the tags used for the relevant Cloudinary resources.
Check Cloudinary transformations discussed in a call
Extract requested image or video treatment terms from a Fireflies transcript and retrieve matching Cloudinary transformations.
Find the streaming profile needed for a video request
Use video requirements from a completed Fireflies transcript to retrieve relevant Cloudinary adaptive streaming profiles.
Supported Triggers and Actions
Notis builds workflows that link Fireflies to Cloudinary. A trigger fires from one place; an action lands in another.
Fireflies triggers
Cloudinary actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Folder
Tool to create a new asset folder. use when you need to organize assets into nested directories. use after confirming the folder path does not already exist.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Metadata Field
Tool to create a new metadata field definition. use when extending your metadata schema with new fields.
Transcription Complete Trigger
Triggers when a transcription is complete. Polls Fireflies API for transcripts created or updated since the last poll time. Handles rate limiting gracefully.
Create Trigger
Tool to create a new webhook trigger for a specified event type. use after configuring your webhook endpoint and choosing the event type. example: "create a trigger for uploads to https://example.com/hooks/cloudinary"
Create Upload Mapping
Tool to create a new upload mapping folder and url template. use when you need to dynamically map external url prefixes to a cloudinary asset folder before uploading files.
Create Upload Preset
Tool to create a new upload preset. use when defining centralized upload options (tags, formats, transformations, etc.) before asset uploads.
Delete Derived Resources
Tool to delete derived assets. use when you need to remove specific derived assets by their ids. example: "delete derived assets with ids [id1, id2]".
Delete Metadata Field Datasource Entries
Tool to delete datasource entries for a specified metadata field. use when you need to soft-delete (inactivate) specific entries in a field's datasource. example prompt: "delete entries ['color1','color2'] from metadata field 'color id'"
Delete Folder
Tool to delete an empty asset folder. use when the folder is confirmed empty and you need to remove it.
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.
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.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
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.
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.
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:
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
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything 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.
More ways to connect Fireflies and Cloudinary
Connect any two apps with Notis in the middle.
Fireflies and Cloudinary, 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 Cloudinary.