
Security News
PEP 810 Proposes Explicit Lazy Imports for Python 3.15
An opt-in lazy import keyword aims to speed up Python startups, especially CLIs, without the ecosystem-wide risks that sank PEP 690.
n8n-nodes-instagram-private-api-wrapped
Advanced tools
n8n community node for Instagram automation using private API capabilities
This is an n8n community node for Instagram automation using the instagram-private-api library. It provides comprehensive access to Instagram's private API capabilities for workflow automation.
n8n is a fair-code licensed workflow automation platform.
Installation
Operations
Credentials
Compatibility
Usage
Resources
Version History
Development
Follow the installation guide in the n8n community nodes documentation.
# Latest version (recommended)
npm install n8n-nodes-instagram-private-api-wrapped@latest
# Specific version 0.0.6 (with credential fixes)
npm install n8n-nodes-instagram-private-api-wrapped@0.0.6
If upgrading from v0.0.5 or earlier:
# Uninstall old version
npm uninstall n8n-nodes-instagram-private-api-wrapped
# Install latest version
npm install n8n-nodes-instagram-private-api-wrapped@latest
# Restart n8n
npm run start
Note: You may need to recreate your credentials after updating to v0.0.6 due to credential name changes.
This node provides the following operations organized by resource type:
This node requires Instagram login credentials configured through n8n's credential system:
🚨 Important: Starting from v0.0.6, credentials are named "Instagram API" (previously "Instagram Credentials"). You may need to recreate your credentials after updating.
This node leverages the powerful instagram-private-api
library to provide access to Instagram's internal APIs, enabling comprehensive automation capabilities.
// Get detailed user profile
{
"pk": "123456789",
"username": "example_user",
"full_name": "Example User",
"follower_count": 1500,
"following_count": 300,
"media_count": 85,
"is_verified": false,
"is_private": false,
"biography": "Content creator and photographer"
}
If you see "Node does not have any credentials set":
// Credential Configuration
{
"username": "your_instagram_username",
"password": "your_secure_password",
"proxyUrl": "http://proxy.example.com:8080" // Optional
}
0.0.6 (Current):
instagramCredentials
→ instagramApi
)proxyUrl
field to credentials for proxy support0.0.5:
0.0.4: Core functionality implementation and bug fixes
0.0.3: Initial TypeScript structure and basic operations
0.0.2: Template refinement and dependency management
0.0.1: Initial template implementation
To work with this node locally:
# Install dependencies
npm install
# Build the node
npm run build
# Run in development mode with file watching
npm run dev
# Run linting
npm run lint
# Run linting with auto-fix
npm run lint:fix
# Run tests
npm test
# Format code
npm run format
The build process includes:
The project includes:
Made with ❤️ for the n8n community
FAQs
n8n community node for Instagram automation using private API capabilities
The npm package n8n-nodes-instagram-private-api-wrapped receives a total of 45 weekly downloads. As such, n8n-nodes-instagram-private-api-wrapped popularity was classified as not popular.
We found that n8n-nodes-instagram-private-api-wrapped demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
An opt-in lazy import keyword aims to speed up Python startups, especially CLIs, without the ecosystem-wide risks that sank PEP 690.
Security News
Socket CEO Feross Aboukhadijeh discusses the recent npm supply chain attacks on PodRocket, covering novel attack vectors and how developers can protect themselves.
Security News
Maintainers back GitHub’s npm security overhaul but raise concerns about CI/CD workflows, enterprise support, and token management.