Exa Websets icon

Exa Websets

Create, manage, and query structured datasets from web sources using Exa Websets API

Actions28

Overview

The node "Exa Websets" provides functionality to create, manage, and query structured datasets from web sources using the Exa Websets API. Specifically, the Monitor - Create operation allows users to set up a content monitor that automatically searches for new web content matching specified criteria and updates websets accordingly.

This is useful in scenarios such as:

  • Tracking news articles or blog posts about a specific topic (e.g., "artificial intelligence breakthroughs").
  • Monitoring social media or forums for mentions of a company or product.
  • Automatically collecting research papers or financial reports related to a field.
  • Keeping an updated dataset of relevant web content without manual searching.

Practical example: A user wants to create a monitor named "AI News Monitor" that runs daily, searching for new English-language news articles about AI breakthroughs, excluding certain domains, and optionally sending notifications when new content is found.

Properties

Name Meaning
Monitor Name Name for the monitor (e.g., "AI News Monitor"). Required string input.
Search Query The search query string to monitor for new content (e.g., "artificial intelligence breakthroughs"). Required string input.
Frequency How often to run the monitor. Options: Daily, Hourly, Monthly, Weekly. Default is Daily.
Target Webset ID Optional ID of an existing webset to which monitored content will be added. Leave empty to create a new webset.
Monitor Configuration Collection of additional configuration options:
  Category Content category to monitor. Options include Any Category, Blog Post, Company, Financial Report, Forum Discussion, GitHub, LinkedIn, News Article, PDF, Research Paper, Tweet, Wikipedia. Default is Any Category.
  Duplicate Detection Boolean flag to skip content already collected. Default true.
  Exclude Domains Comma-separated list of domains to exclude from monitoring (e.g., "reddit.com, twitter.com").
  Include Content Whether to extract full content from monitored pages. Boolean, default true.
  Include Domains Comma-separated list of domains to monitor specifically (e.g., "techcrunch.com, wired.com").
  Include Summary Whether to generate AI summaries of new content. Boolean, default false.
  Language Language filter for content. Options: Any Language, Chinese, English, French, German, Italian, Japanese, Korean, Portuguese, Russian, Spanish. Default is Any Language.
  Max Results Per Run Maximum number of new results to collect per monitoring run. Number between 1 and 1000. Default 50.
  Search Type Type of search to perform. Options: Auto, Keyword, Neural. Default Auto.
  Time Range Time range to look for new content relative to last run. Options: All Time, Past Day, Past Hour, Past Month, Past Week, Past Year. Default Past Day.
  Use Autoprompt Whether to use Exa's autoprompt feature for better search results. Boolean, default true.
Notification Settings Collection of notification-related settings:
  Enable Email Notifications Boolean to enable email notifications when new content is found. Default false.
  Email Address Email address to send notifications to. Only used if email notifications are enabled.
  Enable Webhook Boolean to enable webhook notifications when new content is found. Default false.
  Webhook URL URL to send webhook notifications to. Only used if webhook notifications are enabled.
  Notification Threshold Minimum number of new items needed to trigger notification. Number, minimum 1. Default 1.

Output

The node outputs JSON data representing the result of the monitor creation operation. This typically includes details about the newly created monitor such as its ID, name, configuration, and status.

If the monitor successfully creates or updates a webset with new content, the output may also contain information about the collected items.

No binary data output is indicated by the source code or properties.

Dependencies

  • Requires an API key credential for authenticating with the Exa Websets API.
  • The node makes HTTP requests to https://api.exa.ai.
  • Proper network connectivity to the Exa Websets service is necessary.
  • For email notifications, valid email addresses and possibly configured SMTP/email services outside n8n are required.
  • For webhook notifications, accessible webhook URLs must be provided.

Troubleshooting

  • Common issues:

    • Invalid or missing API authentication token will cause authorization errors.
    • Providing invalid domain names or malformed URLs in include/exclude domain lists may cause request failures.
    • Setting notification options without providing corresponding email addresses or webhook URLs will prevent notifications from being sent.
    • Exceeding maxResults limits or setting frequency too low might lead to rate limiting or API throttling.

  • Error messages:

    • "Unknown resource" error indicates the resource parameter is incorrect or unsupported.
    • Validation errors on required fields like Monitor Name or Search Query will prompt user to provide these inputs.
    • Network or API errors will return messages from the Exa Websets API, which should be checked for details.

  • Resolutions:

    • Ensure all required parameters are filled correctly.
    • Verify API credentials and permissions.
    • Check domain lists for correct formatting.
    • Confirm notification settings are complete if enabled.

Links and References

Discussion