Exa Websets icon

Exa Websets

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

Actions28

Overview

The node allows updating an existing monitor within the Exa Websets platform. Monitors are used to track new content automatically and update websets accordingly. This operation is useful when you want to modify the behavior or parameters of a monitor, such as changing its name, search query, frequency of checks, configuration details, or status.

Practical examples include:

  • Changing the monitoring frequency from daily to hourly to get more frequent updates.
  • Pausing a monitor temporarily without deleting it.
  • Updating the search query to refine what content the monitor tracks.
  • Modifying the monitor’s configuration JSON to adjust advanced settings.

Properties

Name Meaning
Monitor ID The unique identifier of the monitor to update.
Update Fields A collection of fields that can be updated for the monitor:
- Configuration Updated configuration in JSON format (advanced settings).
- Frequency Updated monitoring frequency; options: Daily, Hourly, Monthly, Weekly.
- Monitor Name Updated name for the monitor.
- Search Query Updated search query string that defines what content the monitor tracks.
- Status Update the status of the monitor; options: Active, Paused, Stopped.

Output

The output is a JSON object representing the updated monitor data returned by the API after the update operation. It typically includes the monitor's current properties reflecting the changes made, such as its ID, name, status, frequency, search query, and configuration.

If the node supports binary data output (not indicated here), it would represent any associated files or attachments related to the monitor update, but this node primarily deals with JSON data.

Dependencies

  • Requires an API key credential for authenticating with the Exa Websets API.
  • The node communicates with the Exa Websets REST API at https://api.exa.ai.
  • Proper network access to the API endpoint is necessary.
  • No additional external dependencies beyond the configured API authentication.

Troubleshooting

  • Common issues:

    • Invalid or missing Monitor ID will cause the update to fail.
    • Incorrect JSON format in the Configuration field may result in parsing errors.
    • Providing unsupported values for Frequency or Status will cause validation errors.
    • Network connectivity issues or invalid API credentials will prevent successful updates.

  • Error messages:

    • "Unknown resource": Occurs if the resource parameter is not set to "monitors".
    • API error responses indicating invalid input or unauthorized access should be checked against the provided Monitor ID and API credentials.

  • Resolutions:

    • Verify the Monitor ID exists and is correct.
    • Ensure JSON in Configuration is valid.
    • Use only allowed options for Frequency and Status.
    • Confirm API credentials are correctly configured and have sufficient permissions.

Links and References

Discussion