Find conversations that are waiting on a next step
Give unresolved calls a regular place to resurface, so they do not depend on memory.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Retrieve call details
The /v2/list-calls endpoint retrieves call records with filters (agent id, timestamps), offers sorting, pagination, and handles different responses (success, bad request, unauthorized, server error) in json format.
Why this helps
A call with an unclear next step can remain open-ended and slowly disappear from attention.
- Resurface potentially unresolved conversations on a schedule.
- Use Groqcloud analysis to help find calls worth a closer look.
- Give follow-up a predictable review point without adding constant alerts.
Setup
Build it in a few focused steps.
- 1Connect Groqcloud and Retellai to Notis once through the portal.
- 2Create a recurring automation in the portal or describe it to Notis conversationally.
- 3Ask Notis in one instruction to retrieve recent Retellai calls and have your Groqcloud workflow surface conversations that may need a next-step review.
- 4Choose a weekly schedule and report channel, then review one real run.
Questions about this workflow
Can the workflow tell whether a call is truly unresolved?
Groqcloud can analyze the available call details or transcript context if your workflow provides it; treat the results as items for review.
Does this automatically make follow-up calls?
No. This scheduled workflow surfaces calls for review and does not place outbound calls.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Groqcloud to Retellai. A trigger fires from one place; an action lands in another.
Groqcloud triggers
Retellai actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Buy a new phone number bind agents
This endpoint allows purchasing a new phone number with a specified area code and binding it to designated agents for inbound and outbound calls. it requires json with agent ids and area code. responses indicate the creation status or errors.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create a new outbound phone call
Initiate an outbound call by post to '/v2/create-phone-call'. requires 'from number' and 'to number' in e.164 format. optional overrides and metadata supported. on success, returns call details including type, status, and ids.
Create a new web call
The /v2/create-web-call endpoint creates a web call with a unique agent id, returning call details like type, token, call id, and status in json format, with a 201 response. optional metadata and variables can be included.
Delete phone number
Deletes an existing phone number identified by its e.164 format.
List all phone numbers
Retrieves a list of all phone numbers associated with the account.
Retrieve call details
The /v2/list-calls endpoint retrieves call records with filters (agent id, timestamps), offers sorting, pagination, and handles different responses (success, bad request, unauthorized, server error) in json format.
Retrieve call details by id
Retrieve call details by id for web/phone calls, including type, agent id, status, timestamps, and web access token; covering responses from success to server errors.
Retrieve details of a specific phone number
Fetches the details of a given phone number in e.164 format.
Connect any two apps with Notis in the middle.
Groqcloud and Retellai, 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 Retellai.