Callingly is a lead response management software that automates immediate call and text follow-ups to new leads, integrating seamlessly with various CRMs and lead sources to enhance sales team responsiveness and conversion rates.
Callingly is a lead response management software that automates immediate call and text follow-ups to new leads, integrating seamlessly with various CRMs and lead sources to enhance sales team responsiveness and conversion rates. On Nagent, Callingly is exposed as a fully-configurable phone & sms integration that any agent can call — 29 actions, and API key authentication. No code is required to wire Callingly into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Callingly to automate the kinds of tasks phone & sms teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Callingly into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Callingly, with input parameters and output schema. Drop these into any step of an agent built in Helix.
CALLINGLY_ACTIVATE_DEACTIVATE_CLIENTTool to activate or deactivate a client account. Use when you need to toggle client access after onboarding or offboarding. Example: "Activate client 123" or "Deactivate client 456".
Input parameters
Unique identifier of the client account to modify.
Set to 1 to activate the client account or 0 to deactivate it.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CALLINGLY_CREATE_AGENTTool to create a new agent. Use when you need to register an agent in Callingly after gathering their account ID and contact details.
Input parameters
Agent's phone extension if applicable
Agent's email address
Agent's first name
Agent's last name
Agent's timezone, IANA format (e.g., 'America/Phoenix')
Client's account ID under which the agent will be created
Agent's phone number in E.164 format (must include country code with '+' prefix, e.g., '+14155551234')
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CALLINGLY_CREATE_CALLCreates a new outbound call record and initiates a real outbound call, which incurs cost — ensure explicit user authorization and compliance with applicable consent and telemarketing regulations before use. The call will be routed to available agents on the specified team based on account-level routing configuration. Use List Teams first to get valid account_id and team_id values. Returns a call_id that can be used with Get Call to retrieve call status, recordings, and other details.
Input parameters
Lead's email address
External CRM identifier for the lead, used for syncing with your CRM system
Source where the lead originated from (e.g., 'HubSpot', 'Website', 'Referral')
Lead's company name
ID of the team that will handle the call. Retrieve available team IDs using the List Teams endpoint. Must belong to the specified account_id — a mismatch will prevent proper call routing.
Category to classify the call (e.g., 'Sales', 'Support', 'Pools')
Lead's last name
Your Callingly account ID. Retrieve this using the List Teams endpoint (account_id is returned in each team object).
Lead's first name
Lead's phone number in E.164 format (e.g., +15555555555 for US, +442071234567 for UK)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CALLINGLY_CREATE_CLIENTCreates a new client account in Callingly. Clients are sub-accounts under your agency account that can have their own teams, agents, and billing. Use this when onboarding a new business customer to your Callingly agency.
Input parameters
Client's email address.
Client's first name.
Client's last name.
Client's company name.
Password for the client's account.
Client's phone number in E.164 format (e.g., +14155551234). Must be a valid phone number with a real area code.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CALLINGLY_CREATE_TEAMTool to create a new team. Use when setting up a team configuration before adding agents.
Input parameters
Name of the team.
Delay in seconds before dialing team members.
Number of retry attempts per agent.
Enable per-agent retries: 1 to enable, 0 to disable.
Language code for team messages (e.g., 'en').
Call distribution mode. Only 'simultaneous' supported currently.
Whether calls should be recorded: 1 to record, 0 otherwise.
Account ID under which to create the team.
Pre-call whisper message template.
Number of retries at the lead level.
Enable rescheduling on no-answer: 1 to enable, 0 to disable.
Enable lead-level retries: 1 to enable, 0 to disable.
Schedule for per-agent retries in minutes.
Schedule for lead-level retries in minutes.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CALLINGLY_CREATE_WEBHOOKTool to create a new webhook for call or lead events. Use when you need to receive real-time notifications on specific events. Example: "Create a webhook for call_completed events to http://example.com/callback".
Input parameters
A descriptive name for the webhook.
Event that triggers this webhook.
For lead_created or lead_updated events only: field to watch for changes.
For lead_created or lead_updated events only: value the watched field must match.
For call_completed events only when direction is outbound: the team ID to filter on.
For call_completed events only: whether to trigger on outbound or inbound calls.
For call_completed events only when direction is inbound: the number ID to filter on.
The callback URL to receive the webhook.
For call_completed events only: status filter.
For call_completed events only: lead outcome filter.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CALLINGLY_DELETE_AGENTPermanently delete an agent from a Callingly account. Use when removing an agent who should no longer receive calls. Requires both the agent ID and the account ID the agent belongs to.
Input parameters
Unique identifier of the agent to delete.
The client account ID that the agent belongs to. Required to identify which account's agent to delete.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CALLINGLY_DELETE_CLIENTTool to delete a client. Use when you need to remove an existing client from your account after confirming its ID.
Input parameters
Positive integer ID of the client to delete
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CALLINGLY_DELETE_LEADTool to delete a lead by ID. Use when you need to permanently remove a lead from your account after confirming its ID. Returns a success confirmation.
Input parameters
Positive integer ID of the lead to delete.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CALLINGLY_DELETE_WEBHOOKTool to delete a webhook. Use when permanently removing a webhook by its ID.
Input parameters
Unique identifier of the webhook to delete.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CALLINGLY_GET_AGENT_SCHEDULETool to retrieve the availability schedule for a specific agent. Use when you need to know which days and times the agent is available.
Input parameters
Unique identifier of the agent. Obtain this from the List Users action.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CALLINGLY_GET_CALLRetrieves detailed information about a specific call by its unique ID. Returns comprehensive call metadata including status, duration, lead information, agent details, recording URLs, transcripts, and AI-generated insights. Use the LIST_CALLS action first to obtain valid call IDs.
Input parameters
The unique numeric identifier of the call to retrieve. Obtain this from the LIST_CALLS action response.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CALLINGLY_GET_LEADTool to retrieve details of a specific lead by its ID. Use when you need full lead details before follow-up actions.
Input parameters
Positive integer ID of the lead to retrieve.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CALLINGLY_GET_TEAMTool to retrieve details of a specific team. Use after obtaining the team ID to fetch its configuration details.
Input parameters
Unique identifier of the team to retrieve
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CALLINGLY_GET_WEBHOOKTool to retrieve details of a specific webhook by its ID. Use when you need to inspect a webhook's configuration before modifying or deleting it.
Input parameters
Unique identifier of the webhook to retrieve.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CALLINGLY_LIST_CALLSTool to list calls. Use when you need to retrieve multiple call records with optional filters such as date range, team, and pagination after identifying the need for a collection of calls.
Input parameters
End date for filtering calls (YYYY-MM-DD).
Page number for pagination.
Number of records per page.
Start date for filtering calls (YYYY-MM-DD).
Filter calls by team ID.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CALLINGLY_LIST_CLIENTSTool to list clients. Use when you need to retrieve all clients associated with your account.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CALLINGLY_LIST_LEADSTool to list leads based on provided filters like date range or phone number. Use after confirming filter criteria when bulk lead retrieval is needed.
Input parameters
Date (YYYY-MM-DD) to filter leads created on or before this date
Page number for pagination.
Number of records per page.
Date (YYYY-MM-DD) to filter leads created on or after this date
Account ID for agency partner context
Phone number to filter leads by, e.g., '+14801234567'
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CALLINGLY_LIST_TEAMSTool to list teams. Use when you need to retrieve all teams associated with your account.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CALLINGLY_LIST_TEAM_USERSRetrieve all agents assigned to a specific team in Callingly. Returns each agent's ID, name, priority, call cap, and any custom/integration identifiers. Use this to audit team composition or before performing agent management operations like updates or removals.
Input parameters
The unique numeric ID of the team. Use the List Teams action to retrieve available team IDs.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CALLINGLY_LIST_USERSTool to retrieve a list of agents. Use when you need to see all agents available under the authenticated account, optionally filtering by a specific client account.
Input parameters
Filter users by client account ID (required for agency partners)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CALLINGLY_LIST_WEBHOOKSTool to list configured webhooks. Use when you need to retrieve all webhooks configured in your account to review or manage them.
Input parameters
Filter webhooks by client account ID (required for agency partners)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CALLINGLY_REMOVE_TEAM_AGENTTool to remove a specific agent from a team. Use when you need to disassociate an agent from a team after confirming both team and agent IDs.
Input parameters
Unique identifier of the team to remove the agent from.
Unique identifier of the agent to remove from the team.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CALLINGLY_UPDATE_AGENTTool to update an existing agent's details. Use when you need to modify agent information post-creation.
Input parameters
Unique identifier of the agent to update
Agent's phone extension if applicable
Agent's first name
Agent's last name
Agent's timezone, IANA format (e.g., 'America/Phoenix')
Client's account ID under which the agent exists
Do-not-disturb flag: 1 to enable, 0 to disable
Agent's phone number, in E.164 or local format
Datetime until which do-not-disturb is active, required if donotdisturb=1
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CALLINGLY_UPDATE_LEADTool to update an existing lead's information. Use when you need to modify lead contact details, status, or blocking settings.
Input parameters
Unique identifier of the lead to update
Email address of the lead
First name of the lead
Last name of the lead
Current stage in the pipeline
Outcome/result after call or follow-up
Origin/source of the lead (e.g., 'HubSpot', 'Web Form')
Current status of the lead (e.g., 'new', 'contacted', 'qualified')
Company name associated with the lead
Flag to block the lead: 1 to block, 0 to unblock
Flag to stop automated calls: 1 to enable, 0 to disable
Phone number of the lead in E.164 format (e.g., '+14155551234')
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CALLINGLY_UPDATE_SCHEDULETool to update an agent's availability schedule. Use when you need to set or override an agent's daily availability times.
Input parameters
Unique identifier of the agent whose schedule is being updated. Get agent IDs from the List Users action.
Array of DaySchedule objects defining the agent's weekly availability. Can include all 7 days (Sunday=0 through Saturday=6) or just specific days to update. Each day requires label, day number, is_available flag, and times array.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CALLINGLY_UPDATE_TEAM_AGENT_SETTINGSTool to update settings (priority, capacity) for a specific team agent. Use when adjusting an agent's priority or call capacity after team configuration.
Input parameters
Maximum number of calls the agent can receive. Use null or omit for unlimited capacity.
Unique identifier of the team containing the agent.
Unique identifier of the agent whose settings to update.
Calling priority of the agent within the team (1 = highest priority, called first).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CALLINGLY_UPDATE_TEAM_USERSUpdates the list of agents assigned to a team. This operation replaces all existing agent assignments - any agents not included in the list will be removed from the team. Use CALLINGLY_LIST_TEAM_USERS to check current assignments before updating.
Input parameters
The unique identifier of the team to update. Use CALLINGLY_LIST_TEAMS to find team IDs.
List of agent IDs to assign to the team. This replaces all current agents. Use CALLINGLY_LIST_USERS to find agent IDs. Pass an empty list to remove all agents.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CALLINGLY_UPDATE_WEBHOOKUpdates an existing webhook's configuration by ID. Supports partial updates - only provide fields you want to change. Note: When updating event-specific fields (call_status, call_lead_status, field, filter), you must also include the event field in your request.
Input parameters
The unique identifier of the webhook to update. Required.
New descriptive name for the webhook.
Event type that triggers the webhook. Must be included when updating event-specific fields like call_status or field/filter.
For lead_created/lead_updated events: the lead field to watch for changes. Requires event='lead_created' or 'lead_updated'.
For lead_created/lead_updated events: the value the watched field must match. Requires event='lead_created' or 'lead_updated'.
For outbound call_completed events: filter by team ID. Requires call_direction='outbound'.
For inbound call_completed events: filter by number ID. Requires call_direction='inbound'.
New callback URL to receive webhook payloads.
For call_completed events: filter by call status. Requires event='call_completed'.
For call_completed events: filter by call direction. Requires event='call_completed'.
For call_completed events: filter by lead outcome. Requires event='call_completed'.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 55 agents privately built on Nagent that already use Callingly.
Build on Nagent
Connect Callingly to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Callingly, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Callingly is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Callingly is connected, you configure its 29 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Callingly steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Callingly event fires, the agent kicks off automatically.
Every Callingly action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Callingly ships with 29 pre-built phone & sms actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Callingly together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Callingly-based workflows tailored to your business.