Classify support tickets
Turn sample ticket text into a category, urgency and summary. Review the result before routing a ticket.
Download workflow JSONINTEGRATIONS
Use Flonno from your server or automation tool. Start with a sample, select a model and inspect the response before connecting business systems.
chat:completions and access to your chosen model. Add models:read if your client lists models.https://www.flonno.com/v1.Download a workflow, import it from a file in n8n and open the Call Flonno node. Select a Header Auth credential with name Authorization and value Bearer YOUR_FLONNO_KEY. Replace the sample input, then execute manually.
Turn sample ticket text into a category, urgency and summary. Review the result before routing a ticket.
Download workflow JSONTurn supplied product facts into a short description. Review every claim before publishing.
Download workflow JSONExtract invoice fields from text you supply. This example uses text; it does not upload or read PDFs.
Download workflow JSONRead text from choices[0].message.content. JSON requested in a prompt still needs validation. The files contain no API secrets and start inactive. Your n8n version may require adapting node settings; live execution in n8n has not yet been verified.
Import the OpenAPI specification into your API client to explore the two documented endpoints. Add your own credential after importing.
A small server script using built-in fetch, a request timeout and a 128-token output cap.
Download Node.js example ↓Read the SDK guide →Configure your Flonno key and base URL, then call Chat Completions with a supported model ID.
Download Python example ↓A configuration for an OpenAI-compatible route. The API key comes from your server environment.
Download LiteLLM configuration ↓Read the LiteLLM guide →HTTP 401: check your key. HTTP 403: check permissions, model access and IP restrictions. HTTP 402: check your available prepaid balance. HTTP 400: check the model ID and request fields. Review Activity logs after each test; avoid automatically retrying payments or failed generation.
Flonno receives request content and currently forwards model requests to an external inference service. Self-hosted inference and automatic overflow are target architecture. n8n and client tools may retain execution content according to their settings. Read the privacy notice before sending customer data.