Critique API

Interact with Critique AI search and content API

Actions2

Get Content

AI-generated

Overview

This node integrates with the Critique AI API to perform two main operations: AI-powered search and retrieving processed content from a webpage. Specifically, for the "Get Content" operation, it fetches and processes the content of a given URL using Critique AI's content API. This is useful when you want to extract clean, structured, or enhanced content from web pages without manually scraping or parsing HTML.

Practical examples include:

  • Automatically extracting article text or summaries from news websites.
  • Gathering product descriptions from e-commerce pages.
  • Fetching blog post content for further analysis or republishing workflows.

Properties

Name Meaning
URL The web address of the page from which to retrieve processed content. Must be a valid URL starting with http:// or https://.

Output

The node outputs a JSON object containing the response from the Critique AI content API. This typically includes the processed content extracted from the specified URL. The exact structure depends on the API response but generally contains fields such as the cleaned text, metadata, or other enriched content data.

No binary data output is produced by this operation.

Example output JSON (simplified):

{
  "content": "Extracted and processed text from the webpage",
  "metadata": {
    "title": "Page Title",
    "author": "Author Name",
    "datePublished": "2024-01-01"
  }
}

Dependencies

  • Requires an active API key credential for the Critique AI service.
  • The node makes HTTP POST requests to https://api.critique-labs.ai/v1/contents.
  • Ensure that the API key is configured in n8n credentials before using the node.
  • Internet access is required for the node to reach the Critique AI API endpoint.

Troubleshooting

  • Invalid URL: If the provided URL is malformed or unreachable, the API may return an error or empty content. Verify the URL format and accessibility.
  • Authentication errors: Missing or invalid API key will cause authentication failures. Confirm that the API key credential is correctly set up.
  • API rate limits or downtime: If the API service is unavailable or rate limited, the node will throw errors. Check the service status or consider retry mechanisms.
  • Unexpected API response: If the API changes its response format, the node output might not match expectations. Review the API documentation for updates.

Common error message example:

  • "Invalid URL" — indicates the URL parameter is incorrect or the API cannot process it.
  • "Unauthorized" — indicates issues with the API key credential.

Links and References

Discussion