Keep transcript commitments moving into Supabase
Send a new transcript to Notis and let it turn explicit follow-ups into rows in your Supabase task table.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Execute project database query
Executes a given sql query against the project's database; use for advanced data operations or when standard api endpoints are insufficient, ensuring queries are valid postgresql and sanitized. use the get table schemas or generate type script types tool to retrieve the table schema, then base your query on it.
Why this helps
Meeting commitments get buried in long transcripts and are easy to forget when switching to the next task.
- Capture explicit next steps while the conversation is still fresh.
- Preserve owners and dates only when the transcript states them.
- Reduce manual copying between transcription and task tracking.
Setup
Build it in a few focused steps.
- 1Connect GetTranscribe and Supabase to Notis once through the portal.
- 2Create a new automation in the portal, or ask Notis to create one in plain language.
- 3Tell Notis to extract explicit commitments from each incoming transcript and insert them into your Supabase task table, preserving only details the transcript provides.
- 4Choose an incoming webhook trigger and a channel for run reports.
- 5Send one real transcript and check that the resulting rows reflect its actual commitments.
Questions about this workflow
Does this workflow invent an owner or due date?
The instruction can tell Notis to include those details only when they are stated in the transcript.
What starts the automation?
A webhook request sent when your transcript is ready.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GetTranscribe to Supabase. A trigger fires from one place; an action lands in another.
GetTranscribe triggers
Supabase actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create project api key
Creates a 'publishable' or 'secret' api key for an existing supabase project, optionally with a description; 'secret' keys can have customized jwt templates.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete an API key from the project
Permanently deletes a specific api key (identified by `id`) from a supabase project (identified by `ref`), revoking its access.
Get a third-party integration
Retrieves the detailed configuration for a specific third-party authentication (tpa) provider, identified by `tpa id`, within an existing supabase project specified by `ref`.
List third-party auth integrations for project
Lists all configured third-party authentication provider integrations for an existing supabase project (using its `ref`), suitable for read-only auditing or verifying current authentication settings.
Delete third party auth config
Removes a third-party authentication provider (e.g., google, github) from a supabase project's configuration; this immediately prevents users from logging in via that method.
Update an API key for the project
Updates an existing supabase project api key's `description` and/or `secret jwt template` (which defines its `role`); does not regenerate the key string.
Beta activate custom hostname for project
Activates a previously configured custom hostname for a supabase project, assuming dns settings are verified externally.
Activate vanity subdomain for project
Activates a vanity subdomain for the specified supabase project, requiring subsequent dns configuration for the subdomain to become operational.
Connect any two apps with Notis in the middle.
GetTranscribe and Supabase, 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 Supabase.