Close is a CRM platform designed to help businesses manage and streamline their sales processes, including calling, email automation, and predictive dialers.
Close is a CRM platform designed to help businesses manage and streamline their sales processes, including calling, email automation, and predictive dialers. On Nagent, Close is exposed as a fully-configurable crm integration that any agent can call — 6 actions, and API key authentication. No code is required to wire Close into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Close to automate the kinds of tasks crm 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 Close 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 Close, with input parameters and output schema. Drop these into any step of an agent built in Helix.
CLOSE_CREATE_CALLCreates a new call record in Close.com. This tool allows you to log both inbound and outbound calls associated with a lead, supporting parameters such as lead_id, direction, and optional support for contact_id, phone, duration, note, recording_url, and user_id.
Input parameters
A text note about the call
The phone number associated with the call
The ID of the lead associated with the call Must reference an existing lead; an incorrect ID silently attaches the call to the wrong lead.
The ID of the user who made/received the call
Duration of the call in seconds
The direction of the call (outbound or inbound)
The ID of the contact associated with the call
The outcome of the call (answered, no-answer, vm-answer, vm-left, busy, blocked, error, abandoned)
HTTPS URL pointing to the MP3 recording of the call
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
CLOSE_CREATE_LEADCreates a new lead in Close CRM. A lead represents a company or organization in your sales pipeline. This tool allows you to create leads with company information (name, description, website), associate contacts with emails/phones/URLs, add addresses, and set the lead status. Contacts and addresses can be nested in the lead creation request. The tool returns comprehensive lead information including the lead ID, direct URL to view in Close CRM, associated contacts with their IDs, addresses, status information, and creation/update timestamps. Note: Activities, tasks, and opportunities must be created separately after lead creation.
Input parameters
Website URL of the company
Name of the company/lead
List of contacts associated with the lead
List of addresses associated with the lead
ID of the lead status. If not provided, organization's default status will be used
Description of the lead
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
CLOSE_CREATE_SMSThis tool creates a new SMS activity in Close CRM. It is primarily used to log SMS communications, including sent messages, received messages, and draft messages. The tool requires an internal phone number (local_phone) which must be an SMS-enabled phone number owned by your Close organization. Note: Actually sending SMS messages (status 'outbox' or 'scheduled') requires A2P 10DLC compliance.
Input parameters
The content of the SMS message
The status of the SMS. Must be one of: inbox, draft, scheduled, outbox, sent
The ID of the lead associated with the SMS Verify the lead_id before submission — an incorrect ID causes silent misassociation with no error returned.
Number of seconds to delay sending the SMS when status is outbox. Must be less than 60
The direction of the SMS. Defaults to 'inbound' if status is inbox, otherwise 'outbound'
The ID of the contact associated with the SMS
The internal phone number used to send the SMS. Must be associated with a Phone Number of type 'internal'
The ID of an SMS Template to render and use as the message content
The recipient's phone number
The date and time when the SMS should be sent (required if status is 'scheduled')
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
CLOSE_CREATE_TASKThis tool creates a new task in Close.com. Tasks are used to track to-do items and can be associated with leads. The tool will create a task with the specified parameters using the provided text, due_date, and is_complete flags.
Input parameters
The date when the task is actionable. Can be date-only (YYYY-MM-DD) or date-time (YYYY-MM-DDThh:mm:ss+00:00)
Description of the task
Type of task to create. Must be either 'lead' (a to-do item for a sales rep) or 'outgoing_call' (a call task). Defaults to 'lead'
The ID of the lead the task is associated with An incorrect but valid lead_id silently associates the task with the wrong lead.
User ID of the person the task is assigned to. If omitted, assigns to the API caller
Whether the task is complete
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
CLOSE_DELETE_CALLThis tool allows you to delete a specific call activity in Close.com. It is useful for removing incorrectly logged calls or cleaning up call records. The action deletes a call activity using its unique call ID and cannot be undone.
Input parameters
The unique identifier of the call activity 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
CLOSE_GET_NOTEThis tool retrieves a list of note activities from Close. It allows users to fetch notes with optional filtering parameters, including filtering by lead_id, user_id, and date ranges. The tool returns details such as note content, creation and update dates, and any associated attachments.
Input parameters
Number of results to skip for pagination (maps to _skip API parameter). Use together with limit to page through results.
Maximum number of results to return per page (maps to _limit API parameter). Use together with skip to page through results.
Filter notes by a specific lead ID An incorrect lead_id silently returns notes for the wrong lead rather than raising an error; verify the lead_id before filtering.
Filter notes by a specific user ID
Filter notes created after this date (ISO 8601 format)
Filter notes created before this date (ISO 8601 format)
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 34 agents privately built on Nagent that already use Close.
Build on Nagent
Connect Close 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 Close, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Close is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Close is connected, you configure its 6 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Close 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 Close event fires, the agent kicks off automatically.
Every Close 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 Close ships with 6 pre-built crm actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Close together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Close-based workflows tailored to your business.