B2B contact enrichment and prospecting platform providing verified email addresses, phone numbers, and company information
B2B contact enrichment and prospecting platform providing verified email addresses, phone numbers, and company information On Nagent, Lusha is exposed as a fully-configurable sales & crm integration that any agent can call — 7 actions, and API key authentication. No code is required to wire Lusha into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Lusha to automate the kinds of tasks sales & 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 Lusha 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 Lusha, with input parameters and output schema. Drop these into any step of an agent built in Helix.
LUSHA_CREATE_SUBSCRIPTIONTool to create one or more webhook subscriptions for real-time signal notifications. Use when you want to subscribe to Lusha signals (job changes, company updates, etc.) and receive real-time webhook notifications. Maximum 25 subscriptions per request. Example use case: Set up a webhook to notify your system whenever a contact gets a job title promotion or a company has a funding event.
Input parameters
Default subscription name prefix.
Default values applied to all subscriptions. Required fields: url. Optional fields: entityType, signalTypes.
Array of subscriptions to create (max 25 in production).
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
LUSHA_DELETE_SUBSCRIPTIONSDelete one or more webhook subscriptions by their IDs. Use this action to remove webhook subscriptions from your Lusha account. The action supports batch deletion of up to 25 subscriptions per request. Returns a summary with success and failure counts for each subscription.
Input parameters
Array of subscription IDs to delete. Maximum 25 IDs per request.
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
LUSHA_GET_AUDIT_LOGSRetrieve audit logs for your account including API calls and webhook deliveries. Use when you need to review delivery status, errors, and performance metrics for webhooks and API requests in your Lusha account.
Input parameters
Maximum number of results (1-100)
Number of results to skip
Status of audit log delivery.
Filter by subscription 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
LUSHA_GET_AUDIT_LOG_STATSRetrieve aggregated statistics for audit logs. Returns total count, successful count, failed count, and success rate percentage. Use this to monitor audit log activity and delivery success rates.
Input parameters
Filter statistics by subscription 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
LUSHA_GET_SUBSCRIPTIONTool to get details of a specific webhook subscription by ID. Use when you need to retrieve information about an existing webhook subscription including its status, configuration, and entity details.
Input parameters
The unique identifier of the subscription 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
LUSHA_LIST_SUBSCRIPTIONSList all webhook subscriptions for your account with pagination support. Use when you want to retrieve all configured webhook subscriptions to review their settings, check active status, or manage your webhook integrations. Example use case: Get a paginated list of all your webhook subscriptions to review which contacts or companies you're tracking.
Input parameters
Maximum number of results (1-100)
Number of results to skip
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
LUSHA_UPDATE_SUBSCRIPTIONUpdate an existing webhook subscription configuration. Use this action to modify an existing webhook subscription's settings such as name, webhook URL, active status, and signal types. Optionally, you can regenerate the webhook secret for enhanced security.
Input parameters
The unique identifier of the subscription to update.
New webhook URL.
New subscription name.
Enable or disable subscription.
New signal types to subscribe to.
Generate new webhook secret (secret will be returned in 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
No publicly available marketplace agent is found using this tool yet. There are 81 agents privately built on Nagent that already use Lusha.
Build on Nagent
Connect Lusha 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 Lusha, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Lusha is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Lusha is connected, you configure its 7 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Lusha 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 Lusha event fires, the agent kicks off automatically.
Every Lusha 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 Lusha ships with 7 pre-built sales & crm actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Lusha together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Lusha-based workflows tailored to your business.