add_agent_phone_number
ChatGPTLinks an organization phone number to an agent for inbound or outbound calls. Takes effect immediately for every version of the agent. Refused when the agent has no published version, already has 3 numbers in that direction, the number is linked to another agent in that direction (unless move is true), or a default number is used for inbound. With move, the number is taken off its current agent in the same step; confirm with the user first, since that agent stops using it, and it is refused while the number has live calls, an unfinished batch, or an active workflow there. Get phone number IDs from list_organization_phone_numbers.
clean_batch_call_names
ChatGPTSuggests a cleaned-up natural first name for each raw name you pass in — same AI suggestion logic the dashboard's batch call upload wizard uses (extracts a first name, e.g. "Rai Rao" -> "Rai", strips titles, fixes casing). The names are processed by an AI model to produce the suggestions; nothing is stored and nothing is changed. Call this on the name column before create_batch_call, show the user original vs. suggested for each, let them accept/reject/edit, then build the final CSV using the confirmed names.
create_agent
ChatGPTCreates a new voice agent for the organization. This is NOT a read-only action — it creates a real, persistent agent. prompt_text, language_id, and voice_id are required; everything else has sensible defaults. Use list_languages/list_voices/list_llms/list_transcribers first to get valid IDs. Only call this after the user has described what they want the agent to do — never as a guess.
create_batch_call
ChatGPTCreates a batch call campaign from a small lead list and starts dialing real phone numbers immediately. This is NOT a read-only action, spends real money, and cannot be undone once calls go out (the campaign itself can be cancelled afterward with update_batch_call_status, but any calls already placed are not). Requires confirm: true — only set this after the user has explicitly approved starting this specific batch, never preemptively. Only suitable for short lists (a few dozen leads at most) — for larger campaigns, tell the user to use the dashboard upload instead. Recommended order: clean_batch_call_names on the name column, then preview_batch_call_leads on the file, resolve any issues with the user, THEN call this. Leads file, in this order of preference: the file argument when the user attached a file in the chat (pass the attachment, never re-encode it); otherwise an upload_id from create_upload_url for any real file; file_text only for a few rows the user typed into the conversation. If the user has not given any leads yet, ask for them and say they can either paste the numbers or attach their CSV/Excel file. Either way the file needs a phone_number column (and optionally name/other columns as dynamic variables). agent_version_number must be a PUBLISHED version; the batch stays on that version even if the agent is published again while it runs. The batch dials from one of the agent's outbound numbers: pass phone_number_id when the agent has more than one (list_agent_phone_numbers). Use get_agent or list_agent_versions first to find the right version_number.
create_call
ChatGPTPlaces a real outbound phone call using one of the organization's agents. This is NOT a read-only action: it dials an actual phone number immediately and deducts from the organization's billing wallet on success. Only call this after the user has explicitly confirmed the phone number and intent — never as a guess or a way to "check" something. Requires the organization's account verification (completed in the dashboard) and sufficient wallet balance; fails with a clear error otherwise. Returns the new call's ID (e.g. call_abc123), which can be passed to get_call to check on its status afterward.
create_knowledge_base
ChatGPTCreates a new, empty named knowledge base container for the organization. This is NOT a read-only action. This only creates the container — add content with upload_knowledge_base_text (text you already have, e.g. from a document the user shared), or from the dashboard for PDF files.
create_organization_folder
ChatGPTCreates a folder for grouping agents. Reversible — folders hold no data of their own, and deleting one does not delete the agents inside it. Use move_agent_to_folder afterwards to file agents into it.
create_upload_url
ChatGPTPrepares a secure, one-time upload slot for a real file that lives on a machine you control, so it never has to be pasted into the conversation: a PDF/text document for a knowledge base (kind kb_document, target_id = kb_id), or a CSV/Excel leads file for a batch call (kind batch_leads, target_id = agent_id). Returns an upload_id valid for 10 minutes. Not needed for a file the user attached in the chat: that attachment goes in the file argument of the target tool (preview_batch_call_leads, create_batch_call, upload_knowledge_base_document). The file bytes are sent with an HTTP PUT by whoever holds the file. Set reveal_url to true only when the caller performs that PUT itself (a command-line agent or script with internet access); the result then includes the URL and headers to use, and names the tool to call once the upload is done. Chat sandboxes without internet access cannot complete the PUT. In hosts that render apps, an upload panel appears in the chat for the user to pick the file; once they confirm, call the finalize tool with the upload_id. Rule of thumb: content under ~50 KB that you already have goes inline as file_text (or file_base64 for a small .xlsx on disk); anything larger on your own disk comes through here. Nothing is stored until the file is actually uploaded.
delete_agent
ChatGPTPermanently deletes an agent and detaches every phone number assigned to it, so inbound calls to those numbers are no longer answered by it. It is refused while an active workflow uses the agent, or while one of its numbers has an unfinished batch or a call in progress. This is NOT reversible. Only call this after the user has explicitly confirmed they want THIS specific agent deleted — never as a guess, and never in response to an ambiguous request. Use get_agent first to confirm you have the right one. Requires confirm: true — only set this after the user has given explicit approval in this conversation, never preemptively.
delete_campaign
ChatGPTDeletes a campaign from the organization's list — the same delete the dashboard offers on a draft campaign. Removes the campaign only; calls it already placed keep their own records. Allowed for campaigns that are not live: draft, completed, or cancelled. A campaign that is still going (running, paused, scheduled, waiting) CANNOT be deleted — cancel it first with update_batch_call_status, then delete. Requires confirm: true, and this cannot be undone.
delete_knowledge_base
ChatGPTPermanently deletes a knowledge base and its documents. This is NOT reversible, and fails if the knowledge base is still attached to any agent. Requires confirm: true — only set this after the user has explicitly approved deleting this specific knowledge base, never preemptively.
delete_organization_folder
ChatGPTDeletes a folder. The agents inside it are not deleted; they become unfiled. Requires confirm: true.
delete_phone_number
ChatGPTReleases/deletes one of the organization's phone numbers. This is NOT reversible. Refused while calls are live on the number, while a batch that is not completed or cancelled dials from it, or while an active workflow uses it. Use get_organization_phone_number first to confirm you have the right one. Requires confirm: true — only set this after the user has explicitly approved removing this specific number, never preemptively.
disconnect_integration
ChatGPTDisconnects an integration. This takes effect immediately — anything currently relying on this connection (agent functions, workflow application nodes) will stop working until it's reconnected. Reversible by reconnecting, but not instantaneous (the user has to go through the connect flow again), so requires confirm: true — only set this after the user has explicitly approved disconnecting this specific integration, never preemptively.
duplicate_agent
ChatGPTClones an existing agent — copies its current version's prompt and every setting into a brand-new agent. Reversible: the copy is an unpublished DRAFT that makes no calls, and the original is untouched. Deliberately does NOT copy the phone-number binding, so the clone never starts answering the original's number. Use it for "make a copy of X so I can tweak it" or "same agent but for the Hindi market". Resolve the source with list_agents first.
get_agent
ChatGPTReturns full configuration for a single agent by ID (e.g. agent_abc123), including all versions with their functions, pronunciations, and post-call analysis config. Use list_agents first if you don't already have the ID.
get_agent_builder_inventory
ChatGPTReturns the catalog of building blocks available to the agent builder — LLMs, transcribers, languages, and other resolver options usable when configuring an agent.
get_agent_phone_number_history
ChatGPTEvery number an agent has been linked to, with when it was linked and unlinked and why (manual, agent_deleted, number_deleted, number_released). Newest first. unlinked_at null means the link is current.
get_agent_version
ChatGPTReturns full configuration for a single version of an agent, given its agent_id and version_number, including functions, voice, LLM, and transcriber config.
get_billing_alert_emails
ChatGPTReturns the email addresses that receive this organization's balance and spend alerts. An empty list means alerts fall back to the organization owner.
get_call
ChatGPTReturns full details for a single call by its ID (e.g. call_abc123). Use list_calls first if you don't already have the ID.
get_call_details
ChatGPTReturns what actually HAPPENED on one call: its transcript, the post-call summary, notes, the recording link, warm-transfer details and audio-cache use. This is the only way to read a SINGLE call's transcript — get_call returns metadata (status, duration, cost) but never the conversation. Use it for "what did the agent say on that call?", "why did this one go wrong?", or to quote a caller's own words. Transcripts can be long; ask only for the fields you need. The recording link is returned only with include_recording: true, which you set only when the user explicitly asks for the audio.
get_call_retries
ChatGPTReturns the retry attempts made for a call, given the ORIGINAL (parent) call id. Retries are separate call records with no batch id of their own, so they do not show up in list_calls_in_batch or campaign counts — this is the only way to see them. Use it for "did it try again?", "how many attempts did this lead get?", or when a campaign's numbers do not add up. An empty list means no retries were made.
get_call_transfer
ChatGPTReturns whether a call was handed to a human (warm transfer) and how that went — which sessions were attempted and their status. Answers "did this reach a person?". Calls whose agent has no transfer step report had_call_transfer_node: false.
get_campaign
ChatGPTReturns details for a single campaign by ID (e.g. batch_abc123). Use list_campaigns first if you don't already have the ID.
get_campaign_status
ChatGPTReturns the current control status (running/paused/completed/etc.) and available actions for a campaign, given its batch_id.
get_dashboard_stats
ChatGPTReturns the organization's call/agent/onboarding summary stats — the same numbers shown on the dashboard home page.
get_dashboard_weekly_stats
ChatGPTReturns the organization's call volume for each of the last 7 days.
get_external_webhook
ChatGPTReturns the organization's external webhooks — the endpoints DialNexa posts call results to, and their settings. Answers "where do my call results go?" and "is a webhook set up?". Separate from list_user_webhooks, which covers per-agent webhooks. URLs show only their host; the full URL is in the dashboard.
get_knowledge_base_affected_agents
ChatGPTReturns the agents that currently use this knowledge base. Call it BEFORE proposing delete_knowledge_base or any change to a KB, so the user is told which agents lose that knowledge by name rather than in the abstract. An empty list means nothing is attached and deleting is safe.
get_knowledge_base_document
ChatGPTReturns a single knowledge base document by ID (e.g. kb_abc123). Use list_knowledge_base_documents first if you don't already have the ID.
get_language
ChatGPTReturns details for a single language by ID (e.g. lang_abc123). Use list_languages first if you don't already have the ID.
get_llm
ChatGPTReturns details for a single LLM by ID (e.g. llm_abc123). Use list_llms first if you don't already have the ID.
get_my_organization
ChatGPTReturns basic details (name, plan, settings) about one organization this credential may use. When the token has several organizations, pass organization_id (from list_my_organizations). When it has one, this returns that organization with no arguments.
get_organization_phone_number
ChatGPTReturns details for one of the organization's phone numbers by ID (e.g. phn_abc123).
get_phone_number_active_workflows
ChatGPTReturns the ACTIVE workflows that dial through this phone number. Call it BEFORE proposing delete_phone_number or reassigning a number, so the user knows what stops working — releasing a number that a live workflow calls through breaks that workflow mid-run. An empty list means nothing active depends on it. Paused workflows are deliberately excluded: they are not blocking.
get_prompt_suggestions_for_agent
ChatGPTReturns pending AI-generated prompt improvement suggestions for a specific agent, based on recent call analysis.
get_spend_limits
ChatGPTReturns the organization's monthly spend cap and how much of it is used, how much has been spent so far this month, when the month resets, and its two low-balance email alerts — all in INR. Months are calendar months in IST. Pair this with get_wallet_balance for any "how much can I still spend" question: once this month's spend reaches monthly_spend_cap_inr, new calls, phone number renewals and purchases are refused until reset_date, however large the wallet. A null cap means no cap is set. The two alert fields only send emails and never block spending.
get_template
ChatGPTReturns details for a single agent template by ID. Use list_templates first if you don't already have the ID.
get_transcriber
ChatGPTReturns details for a single transcriber by ID (e.g. trs_abc123). Use list_transcribers first if you don't already have the ID.
get_user_webhook
ChatGPTReturns details for a single webhook by ID (e.g. webhook_abc123). Secret is masked. The URL shows only its host; the full URL is in the dashboard.
get_voice
ChatGPTReturns details for a single voice by ID (e.g. voice_abc123). Use list_voices first if you don't already have the ID.
get_voice_languages
ChatGPTReturns the languages a specific voice supports, given its voice ID.
get_wallet_balance
ChatGPTReturns the organization's current billing wallet balance in INR — the money left to spend on calls. This is the SAME balance the dashboard sidebar shows, and it is the tool to use for any "how many credits / how much balance do I have left" question. The other billing tools return the plan and rate CATALOG, not what is left. If this organization has no billing_wallets row, this reports that explicitly rather than returning zero.
get_workflow
ChatGPTReturns details for a single workflow by ID (e.g. workflow_abc123). Use list_workflows first if you don't already have the ID.
get_workflow_lead_history
ChatGPTReturns the full execution history for one lead within a workflow — every step it passed through, timestamps, and current status. Use list_workflow_leads first to find the lead_id.
get_workflow_lead_variable_keys
ChatGPTReturns the distinct dynamic variable names (from the uploaded lead CSV columns) available for a workflow's leads — e.g. to know what personalization fields exist.
get_workflow_structure
ChatGPTReturns all nodes and edges currently in a workflow's graph — use this to see the workflow's steps and how they connect, and to check it is complete before it is activated in the dashboard (confirm START has one outgoing edge and no incoming edges, every other node is reachable from START, and a CONVERTED and DROPPED node both exist and are connected).
list_active_agents
ChatGPTReturns the organization's currently active agents (status active, with an inbound or outbound number assigned) — a lighter-weight view than list_agents, used on the dashboard home page.
list_agent_functions
ChatGPTReturns the tool/function definitions (e.g. transfer call, book appointment, custom API calls) configured on a specific agent version. Credential-shaped config values (API keys, tokens, auth headers) are redacted. Use get_agent_version first if you don't already have the version_number.
list_agent_phone_numbers
ChatGPTReturns the phone numbers linked to an agent, split into inbound and outbound (up to 3 each). Numbers are linked to the agent, not a version: every version uses them, and inbound calls run on the agent's latest published version.
list_agent_versions
ChatGPTReturns all versions of a given agent, given its agent_id. Use list_agents first if you don't already have the agent_id.
list_agents
ChatGPTReturns every voice agent in the organization as a compact roster — agent_id, name, type, current version number. This is the tool for resolving an agent NAME to an agent_id (names like "Nexa Agent 10" live here); it deliberately omits prompts, settings and version detail so the whole roster always fits in one result. Call get_agent with an id from here when you need full configuration.
list_batch_call_leads
ChatGPTReturns the leads (contacts) the user uploaded to one of their own batch call campaigns, given its batch_id. For each lead: its id (prefixed lead_), the phone number, the notes and the dynamic variables from the uploaded leads file. Nothing else about the lead is returned, and only batches of the authenticated workspace can be read. Use list_batch_calls to find the batch_id.
list_batch_calls
ChatGPTReturns the organization's batch call campaigns (bulk outbound call jobs), each with an id and title. Use this to find a batch_id before listing the calls inside it or its leads.
list_calls
ChatGPTReturns compact call log ROWS for the organization (status, direction, numbers, duration, cost, timestamps, agent, sentiment, a short summary, and has_transcript/has_recording flags), filterable by agent, status, sentiment and date range. Use it to find calls and to count them. It is NOT the source of truth for what happened on a call: sentiment and summary are written by post-call analysis after the call ends, so they are "unknown" or null on any call that has not been analysed yet. Every result carries an analysis_coverage block saying how many of the returned calls have been analysed. Unanalysed calls carry no sentiment or summary, which says nothing about how the call went. For what was actually said or concluded on one call, use get_call_details. For a single known call by ID, use get_call.
list_calls_in_batch
ChatGPTReturns the individual call logs that belong to a specific batch call campaign, given its batch_id. This is NOT a single-batch-details lookup — it's the calls made within that batch. Use list_batch_calls first to find the batch_id.
list_campaigns
ChatGPTReturns the organization's batch call campaigns with pagination, optionally filtered by status. Use this to find a batch_id before looking up its details or status.
list_countries
ChatGPTReturns the global list of countries phone numbers/calls can be configured for, with their country codes. This is reference data, not org-specific — use list_org_phone_country_rules for what the organization has actually enabled.
list_enabled_network_groups
ChatGPTReturns the telephony network groups currently enabled for the organization's outbound calling.
list_fallback_llms
ChatGPTReturns the LLMs eligible to be configured as an agent’s fallback model (used if the primary LLM fails). Use when the user asks what fallback LLM options exist.
list_fallback_transcribers
ChatGPTReturns transcribers with is_fallback=true — use this list to populate the Fallback STT selector when configuring per-agent STT fallback settings.
list_integrations
ChatGPTReturns every integration available to the organization — provider/adapter keys, what each does, and current connection status (connected/disconnected/error). Use this first to find valid provider_key/adapter_key values before calling any other integration tool.
list_knowledge_base_documents
ChatGPTReturns the organization's knowledge base entries used to ground agent responses. Use this to find a kb_id before fetching a specific document.
list_languages
ChatGPTReturns the languages available for agent voices and transcription. Use when the user asks what languages are supported or wants to configure agent language.
list_llms
ChatGPTReturns the LLM providers/models available to use when configuring an agent (e.g. GPT-4, Claude). Use when the user asks what LLMs are available or wants to pick one for an agent.
list_my_organizations
ChatGPTReturns the DialNexa organizations this credential may use, with each org's id, name, and read/write scopes. Use this when the user has not named an organization, or before passing organization_id to any other DialNexa tool. This is the inventory of orgs on the token; get_my_organization returns details for one org after you have picked an id. Takes no arguments.
list_org_phone_country_rules
ChatGPTReturns the organization's configured rules per country (e.g. allowed prefixes, dialing mode) for outbound calling.
list_organization_folders
ChatGPTReturns the folders used to organize the organization's agents, optionally filtered by name. Use this to find a folder id before filtering agents by folder.
list_organization_phone_numbers
ChatGPTReturns phone numbers owned by the organization, including which agent (if any) is assigned inbound/outbound on each.
list_templates
ChatGPTReturns the platform's catalog of pre-built agent templates, optionally filtered by agent type. Use this when the user wants to start from a template rather than build an agent from scratch.
list_transcribers
ChatGPTReturns the speech-to-text transcriber options available for configuring an agent.
list_user_webhooks
ChatGPTReturns the organization's configured outbound webhooks (URLs notified on events like call completion). Secrets are masked. URLs show only their host; the full URL is in the dashboard.
list_voices
ChatGPTReturns available TTS voices for configuring an agent. Supports three modes via the mode param: standard catalog (filterable by provider/accent/gender/name), just the distinct accent values, or speech-to-speech-capable voices only.
list_workflow_leads
ChatGPTReturns the leads enrolled in a workflow along with their current execution status (which step they're on, when they entered, when they completed). Optionally filter to specific lead IDs.
list_workflows
ChatGPTReturns the organization's automation workflows (multi-step call/WhatsApp sequences), each with an id and name. Use this to find a workflow_id before inspecting its leads.
move_agent_to_folder
ChatGPTFiles an agent into a folder, or removes it from one. Purely organisational and reversible: it changes nothing about how the agent behaves, dials or is billed. Resolve the agent with list_agents and the folder with list_organization_folders first.
preview_batch_call_leads
ChatGPTParses a small CSV/Excel leads file WITHOUT creating anything — same preview/validation the dashboard's batch call upload wizard runs before letting a batch start. Returns how many rows are valid vs. invalid, and for each invalid row, which phone number failed and why (bad country code, invalid length, destination not allowed by this org's calling rules, etc.). Use this on the file before create_batch_call: if invalid_row_count > 0, show the user the specific bad rows, get them fixed or dropped, then call create_batch_call with the corrected file. Same file_base64 size limit as create_batch_call (a few dozen rows).
publish_agent
ChatGPTPublishes a DRAFT version of an agent, making it live and immutable. Once published, that version can never be edited again; publishing automatically creates the next draft version of the same agent, which is where further changes go. Inbound calls and workflows switch to the newly published version; a batch that is already running keeps the version it was created with. Phone numbers are attached separately with add_agent_phone_number (the agent needs a published version first). Use get_agent first to find the draft version_number to publish. Refused if the draft's prompt is over the selected model's size ceiling (prompt_health.status over_ceiling from create_agent/update_agent) — shorten the prompt or choose a model with a larger limit first.
redact_call
ChatGPTHides a call's transcript and recording: from then on they are masked wherever the call is returned, while keeping the call record itself (status, duration, cost, outcome) intact. Use it when the user asks to remove what was said or recorded on a call. It cannot be undone through DialNexa, so never use it to tidy up, and never as a side effect of another request. Requires confirm: true. If the user only wants to stop seeing it, say that this is irreversible and ask them to confirm that is what they want.
remove_agent_phone_number
ChatGPTUnlinks a phone number from an agent for one direction. Refused while calls are live on the number, while a batch that is not completed or cancelled dials from it (change that batch's number or cancel it first), or while an active workflow uses it.
request_integration_access
ChatGPTRequests access to an integration that's currently disabled by admin — sends a notification to the DialNexa team to review; nothing is stored and it does not enable the integration itself. Use list_integrations first to check whether the tool is actually disabled (this fails if it's already enabled).
update_agent
ChatGPTUpdates a specific DRAFT version of an existing agent's configuration. This is NOT a read-only action. version_number is required — published versions cannot be updated (only re-published). Only fields you provide are changed — omit anything you don't want to touch. timezone and pipeline_type apply to the whole agent, so they are refused while a batch is running on it (AGENT_HAS_RUNNING_BATCH). Phone numbers are managed with add_agent_phone_number / remove_agent_phone_number, not here. Use get_agent first to see current values and version numbers.
update_batch_call_phone_number
ChatGPTSwitches the number a batch dials from to another of its agent's outbound numbers (list_agent_phone_numbers). Allowed while the batch is draft, scheduled or paused. A running batch must be paused first with update_batch_call_status, and a paused batch must have no call still in progress. Calls not yet dialled move to the new number.
update_batch_call_status
ChatGPTChanges the execution status of a batch call. This is NOT a read-only action. pause halts new outbound calls (in-progress ones continue, can be resumed); resume continues a paused batch; cancel permanently stops it, removes queued calls, and marks call logs cancelled — it cannot be resumed or undone, and requires confirm: true (only set this after the user has explicitly approved cancelling this specific batch, never preemptively). pause/resume do not require confirm.
update_knowledge_base
ChatGPTRenames a knowledge base container. This is NOT a read-only action.
update_organization_folder
ChatGPTRenames a folder. Reversible, and the agents inside it are untouched. Use list_organization_folders first to get the id.
upload_knowledge_base_document
ChatGPTAdds a real PDF or text FILE to a knowledge base and indexes it — the same import the dashboard upload performs. This is NOT a read-only action. Use it after create_upload_url (kind kb_document, target_id = kb_id) once the user has uploaded the file: pass the upload_id. In hosts that attach chat files to tools (ChatGPT), the host fills in file for a document the user attached; leave it alone otherwise. For text you already have in the conversation use upload_knowledge_base_text instead — never base64-encode a PDF yourself. Titles must be unique within the knowledge base.
upload_knowledge_base_text
ChatGPTAdds a text document to a knowledge base and indexes it, so agents that use the knowledge base can draw on it from their next call. This is NOT a read-only action. Pass the document CONTENT as text — when a user shares a PDF or document in the conversation you already have its text, so send that directly; never base64-encode anything for this tool. Give it a short, unique title (the knowledge base rejects duplicate titles). Use list_knowledge_base_documents to find the kb_id. Suited to documents up to roughly a few hundred KB of text; for large PDFs or files that must keep their original layout, tell the user to upload from the dashboard.
validate_integration_connection
ChatGPTRe-checks an existing integration connection against the provider and updates its stored status (connected/error). Use this if a connection looks stale or the user reports it's not working. Fails if there's no connection at all yet for this provider/adapter — the user connects it in the DialNexa dashboard first in that case.