Keep customer requests connected to their source
Save clear requests from customer calls so patterns are easier to spot across conversations.
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
Customer feedback sits in recordings, making it difficult to compare requests or follow up consistently.
- Record requests while the conversation is fresh.
- Retain concise supporting context without copying the full transcript.
- Make feedback easier to review alongside other customer requests.
Setup
Build it in a few focused steps.
- 1Connect GetTranscribe and Supabase to Notis once through the portal.
- 2Create an automation in the portal or describe it to Notis conversationally.
- 3Ask Notis to add each distinct, clearly stated customer request from incoming transcripts to your Supabase feedback table with a short source-grounded summary.
- 4Choose an incoming webhook trigger and a reporting channel.
- 5Test with a customer transcript and check that the saved request is accurate and distinct.
Questions about this workflow
Will it treat every complaint as a feature request?
Tell Notis to capture only explicit requests and separately label other feedback if your table supports it.
Does it need the entire transcript in the database?
No. The instruction can ask for a concise summary and relevant context.
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.