Actions9
- User Actions
- Media Actions
- Feed Actions
Overview
This node integrates with Instagram's private API to perform various actions related to Instagram media. Specifically, the "Like Media" operation allows users to like a specific Instagram media post by providing its media ID. This is useful for automating engagement activities on Instagram posts, such as liking photos or videos programmatically.
Practical examples include:
- Automatically liking posts from certain users or hashtags.
- Integrating Instagram engagement into marketing workflows.
- Building custom social media management tools that interact with Instagram content.
Properties
| Name | Meaning |
|---|---|
| Media ID | Instagram media ID (string). The unique identifier of the media post to like. |
Output
The output JSON contains a simple success confirmation object when the "Like Media" operation completes successfully:
{
"success": true
}
This indicates that the media post was liked without errors.
No binary data is output by this operation.
Dependencies
- Requires an Instagram API authentication credential (an API key or username/password session) configured in n8n.
- Uses a private Instagram API client library bundled with the node.
- The node attempts to reuse saved session data if available; otherwise, it authenticates using provided credentials.
- Network access to Instagram's private API endpoints is necessary.
Troubleshooting
- Authentication failures: If the node throws an error about Instagram authentication failure, verify that the provided credentials are correct and have not expired. Re-authenticate or update credentials as needed.
- Invalid Media ID: Providing an incorrect or non-existent media ID will cause the operation to fail. Ensure the media ID is valid and accessible.
- API rate limits or restrictions: Instagram may limit the number of actions per time period. If you encounter errors related to rate limiting, consider adding delays or reducing request frequency.
- Session issues: If session data is corrupted or invalid, the node falls back to username/password authentication. Make sure credentials allow successful login.