Overview
This node integrates with the Genum API to interact with "prompts" — predefined templates or instructions that can be run with user input. Specifically, the Run operation executes a selected prompt by sending a question (input text) to it and receiving a processed response.
Typical use cases include:
- Automating text generation or transformation based on custom prompts.
- Using AI-driven prompts for chatbots, content creation, or data enrichment.
- Running dynamic queries or commands defined as prompts with contextual memory support.
For example, you might select a prompt designed to summarize text, provide a question, and get back a concise summary generated by the Genum service.
Properties
| Name | Meaning |
|---|---|
| Prompt | Select the prompt to run. You can specify by ID (a numeric string) or choose from a searchable list of available prompts fetched from Genum. |
| Question | The input text or question to process using the selected prompt. |
| Memory Key | Optional key to maintain context or memory across prompt runs, enabling stateful interactions. |
| Productive | Boolean flag indicating whether to use the committed (production) version of the prompt. Defaults to true. |
Output
The node outputs the JSON response returned by the Genum API after running the prompt. This typically includes the processed result based on the input question and prompt logic.
- The output is structured as JSON objects representing the API response.
- If multiple items are returned, each is output as a separate item.
- No binary data output is produced by this node.
Dependencies
- Requires an API authentication token credential for the Genum API.
- The node makes HTTP requests to
https://api.genum.ai/api/v1/endpoints. - Network access to the Genum API must be available.
- Proper configuration of the API key credential in n8n is necessary.
Troubleshooting
- Invalid Prompt ID: If the prompt ID is not a number or does not exist, the API will return an error. Ensure the prompt ID is numeric and valid.
- Authentication Errors: Missing or invalid API token will cause authorization failures. Verify the API key credential is correctly set up.
- Network Issues: Connectivity problems to the Genum API endpoint will cause request failures.
- Empty or Invalid Input: Providing an empty question may lead to unexpected results or errors. Always supply meaningful input text.
- Memory Key Misuse: Using an incorrect or inconsistent memory key may disrupt context continuity.
If the node is set to continue on failure, errors will be included in the output JSON for troubleshooting.
Links and References
- Genum API Documentation (assumed official docs URL)
- n8n Documentation on Creating Custom Nodes
- General info on HTTP Request Node (for understanding underlying requests)