Make call follow-up review a weekly habit
Create one predictable moment to see which conversations need another step.
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
Call follow-ups can become scattered across days, making it hard to see what still needs attention.
- Create a reliable weekly review point for recent calls.
- Use Groqcloud-powered analysis to help identify follow-up needs.
- Reduce the need to remember every call as it happens.
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 ask Notis to set up the outcome in plain language.
- 3In one instruction, ask Notis to retrieve recent Retellai call details and use your Groqcloud workflow to identify outstanding follow-ups.
- 4Choose a weekly Notis schedule and a reporting channel, then review one real weekly run.
Questions about this workflow
What does the scheduled action retrieve?
Retellai's call-list action retrieves call records with filters, sorting, and pagination. The prompt can ask Groqcloud to help interpret the results.
Does Groqcloud trigger this workflow?
No. Notis starts it on a recurring schedule; Groqcloud can support the analysis in the instruction.
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.