Overview
The node interacts with the Prompticus API to retrieve multiple prompt records based on specified filters. It is designed to fetch a list of prompts, optionally filtered by keyword search. This operation is useful when you want to query and display or process many prompt entries at once, such as listing all prompts containing certain keywords or criteria.
Practical examples:
- Fetching all prompts that include a specific keyword for content generation.
- Retrieving a filtered list of prompts to display in a dashboard or further processing.
Properties
| Name | Meaning |
|---|---|
| Filter | Collection of filter parameters. Currently supports: Keyword - search prompts by a keyword string. |
The "Filter" property contains:
- Keyword (q): A string used to search prompts by keyword. This value is sent as a query parameter named
qin the API request.
Output
The output JSON field contains an array of prompt objects retrieved from the Prompticus API. Each object represents a prompt matching the filter criteria. The exact structure of each prompt object depends on the API response but typically includes prompt details such as ID, text, metadata, etc.
No binary data output is indicated.
Dependencies
- Requires an API access token credential for the Prompticus service.
- The base URL for API requests is
https://api.promptic.us/v1. - The node sends requests with headers specifying JSON content type and acceptance.
Troubleshooting
Common issues:
- Missing or invalid API access token will cause authentication errors.
- Incorrect filter parameters may result in empty results or API errors.
- Network connectivity problems can prevent successful API calls.
Error messages:
- Authentication failures: Ensure the API token is correctly configured and valid.
- Invalid query parameters: Verify the filter values conform to expected formats.
- Timeout or network errors: Check internet connection and API availability.
Links and References
- Prompticus API Documentation (assumed URL for reference)
- n8n documentation on creating HTTP Request nodes and using credentials