HDW Instagram icon

HDW Instagram

Integrate with Horizon Data Wave Instagram API
Join our community

Actions8

Overview

The node integrates with the Horizon Data Wave Instagram API to retrieve detailed information about Instagram posts. Specifically, the "Get Post" operation fetches comprehensive data for a given Instagram post ID. This is useful for scenarios where users want to analyze or display detailed post metadata such as captions, media, engagement metrics, and other post attributes.

Practical examples include:

  • Marketing teams extracting post details for performance analysis.
  • Social media dashboards displaying enriched Instagram post content.
  • Automated workflows that trigger actions based on specific post data.

Properties

Name Meaning
Post ID The unique identifier of the Instagram post to retrieve (e.g., 3676612811870810696_1777543238).
Timeout Maximum time in seconds to wait for the API response; valid range is 20 to 1500 seconds.

Output

The node outputs JSON data representing the detailed information of the specified Instagram post. The structure typically includes fields such as post metadata, media URLs, captions, timestamps, and engagement statistics (likes, comments, etc.). If multiple items are returned (though usually one for this operation), each is output as a separate JSON object.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Horizon Data Wave Instagram API.
  • The base URL for API requests is https://api.horizondatawave.ai.
  • The node uses HTTP POST requests with JSON payloads.
  • Proper configuration of the API authentication credential within n8n is necessary.

Troubleshooting

  • Timeout Issues: Setting the timeout too low may cause requests to fail if the API response is slow. Increase the timeout property if you encounter timeouts.
  • Invalid Post ID: Providing an incorrect or malformed Instagram post ID will result in API errors. Verify the post ID format before use.
  • API Errors: The node surfaces detailed error messages including HTTP status codes and API error headers. Common errors might include rate limiting or authentication failures.
  • Authentication Failures: Ensure the API key credential is correctly configured and has sufficient permissions.
  • Rate Limits: If many requests are made in quick succession, the API may throttle requests. The node includes a small delay between requests to mitigate this.

If the node encounters an error and "Continue On Fail" is enabled, it returns an error object with details such as HTTP status, API error message, request ID, execution time, and token points used.

Links and References

Discussion