Actions19
History → Get Many
AI-generatedOverview
This node operation fetches multiple history entries from the ScrapeGraphAI service. It is useful for retrieving a list of past actions or events related to different services such as crawl, extract, monitor, schema, scrape, or search. Users can filter the results by service, paginate through pages, limit the number of results returned, and choose to receive either a simplified or raw response.
Use Case Examples
- Retrieve the last 50 crawl history entries to analyze recent crawling activity.
- Fetch monitor history entries to review monitoring events over a specific period.
- Get a simplified list of search history entries for quick overview and reporting.
Properties
| Name | Meaning |
|---|---|
| Service Filter | Filter to entries for a single service, such as crawl, extract, monitor, schema, scrape, or search. |
| Page | Page number to fetch, starting from 1, for paginated results. |
| Limit | Maximum number of results to return in one request. |
| Simplify | Whether to return a simplified version of the response instead of the raw data. |
Output
JSON
id- Unique identifier of the history entry.service- The service to which the history entry belongs (e.g., crawl, extract).timestamp- The date and time when the history entry was recorded.details- Additional details or metadata about the history entry, which may be simplified or raw based on the 'Simplify' option.
Dependencies
- Requires an API key credential for ScrapeGraphAI service authentication.
Troubleshooting
- Common issues include invalid service filter values or requesting pages beyond available data, which may result in empty responses or errors.
- If the node throws an 'Unsupported combination' error, verify that the resource is set to 'History' and the operation to 'Get Many'.
- Ensure the API key credential is correctly configured to avoid authentication errors.