Package source
Begin from the exact npm command shown on this site. Before running it, inspect the resolved package name, published metadata, version, and terminal prompts. Do not rely on a copied screenshot or a similarly named package.
Install and runtime support
Prepare your agent for a controlled first run
This page is an installation reference, not a sales form. Copy the exact command, inspect package behavior, and validate the skill with a narrow research task before granting broader access or connecting external systems.
Contact information
Know where each installation question belongs
Lindy AI is represented here as an agent-native workflow. No physical office, telephone support line, or verified social profile is claimed. Use the package registry and your own runtime administration channels as the authoritative paths for package and environment questions.
Runtime administration
Questions about file access, network policy, Node.js availability, and secret storage belong to the administrator of the AI agent environment where you execute the installer. Runtime compatibility is configuration-dependent.
Working hours
The installed workflow runs according to your agent environment rather than published office hours. Provider APIs, rate limits, maintenance windows, and account permissions can still affect task availability.
Run a preflight before the installer
- Confirm Node.js and npx are available in the intended environment.
- Review package provenance, execution prompts, update path, and uninstall procedure.
- Prepare a runtime secret store; never paste API keys into a prospecting prompt.
- Scope provider credentials to the minimum permissions required by the test.
- Define retention, deletion, and export rules for any prospect data returned.
- Keep enrichment, drafting, and sending behind separate human approval decisions.
For cold outreach, account relevance does not remove legal and operational obligations. Apply suppression lists, clear identification, opt-out handling, consent rules, and regional requirements such as CAN-SPAM, CASL, GDPR, or other laws relevant to the recipient and sender.