About NexFlow
A visual automation platform for connecting events, data, external services, and AI.
Why NexFlow exists
Many useful processes cross service boundaries: receive a message, transform its content, call an API, and deliver a response. NexFlow turns that process into a canvas that a team can inspect, save, and troubleshoot without hiding the sequence in an ad-hoc script.
Events start work
Manual clicks, webhooks, messages, and form submissions can act as triggers.
Actions transform or deliver
Gemini can generate text, HTTP Request can call a public API, and messaging actions can deliver results.
Runs are durable
Workflow and node states are persisted and processed asynchronously through the execution system.
Telegram assistant example
The Telegram trigger exposes the incoming message as telegram. Gemini reads {{telegram.message.text}}. The send action returns the generated {{aiText.text}} to {{telegram.message.chat.id}}.
Discord command example
/askDiscord sends an HTTP Interaction. NexFlow verifies the request, acknowledges it, queues the workflow, and the reply action replaces the deferred response with {{aiText.text}}.
Current Discord setup limitation
The server implementation supports HTTP Interactions, but the current Discord Trigger panel does not display its generated endpoint URL and says endpoint connection is a later phase. See the Discord guide before planning a self-service production setup.