How can I authenticate JSON requests to fetch Instantly campaign analytics in n8n?

It looks like your question is related to extracting analytics from Instantly, but our current resources only cover topics such as ActiveCampaign integration, expressions, and common issues for nodes like HTTP Request or Chat Trigger. Could you clarify if your question is about one of those topics? If you need help with Strictly n8n documentation (for example—configuring API credentials or troubleshooting node issues), please let me know; otherwise, you might want to consult Instantly’s documentation or support channels for their API-specific guidance.

Below is a few troubleshooting steps to help narrow down the source of the issue:

1. Check the API Response Format

When you don’t pass a JSON body, the endpoint is returning HTML (often a generic status or login page) whereas when you pass a JSON body, the API tries to authenticate your call and fails. This usually indicates that the endpoint expects a specific format or set of headers.

• HTML Response:
  This typically means that the API call is landing on a fallback page (for example, a login or error page).

• Authentication Error in JSON Mode:
  This points to the API expecting proper credentials or additional headers when you issue a JSON request.

2. Verify Your Credentials and Authentication Settings

According to the common issues in n8n’s HTTP Request node documentation, a 403 (Forbidden) error will be shown if authentication fails. To verify:

• Make sure your API key or token is valid.
• Ensure that the credentials have the correct permissions or scopes needed for accessing campaign analytics on Instantly.
• Double-check that you are using the correct authentication method (e.g. adding credentials in the HTTP Request node under the Authentication tab or manually setting the Authorization header).

3. Set the Appropriate Headers

When switching to JSON, ensure you’re setting the correct headers. For example, you might need to include:

JSONCopied
{
  "Content-Type": "application/json",
  "Accept": "application/json",
  "Authorization": "Bearer YOUR_API_KEY"
}

If you’re not sure if Instantly’s API requires a different header or token format, consult the API documentation provided by Instantly.

4. Validate Your JSON Format

If you’re using an Expression or manually inputting JSON, double-check that the entire JSON is wrapped correctly. As noted in the n8n docs, using the Expression in a JSON parameter should be wrapped in double curly braces:

JSCopied
{{
  {
    "key": "value",
    "anotherKey": ["arrayValue1", "arrayValue2"]
  }
}}

Also, validate your JSON externally to ensure there are no syntax errors like missing commas or brackets.

5. Compare with a Working Example

If another node or integration is working with Instantly (or a similar API), compare the settings, headers, and credentials. Sometimes tweaking the batch options or connection settings (if applicable) might help narrow down the problem.

Final Thoughts

In summary, the behavior indicates that the API endpoint returns a default HTML page when no JSON is provided, but once you switch to JSON, the authentication mechanism kicks in—and this is where the issue lies. Focus on:

• Verifying that your API credentials are correct and properly applied.
• Ensuring the JSON payload is correctly formatted.
• Setting the right headers as expected by the API.

If after these checks the issue persists, it may be useful to review Instantly’s API docs or use the HTTP Request node in “Test” mode to see the detailed error message, which might give more insight into what the API expects.

Let me know if you need additional details on any of these steps!