This could have been a dramatic automation story about one workflow saving a business 150,000 hours. It is not. This is a practical demo of a smaller, more common problem: turning a vague website message into something a human can actually act on.
The workflow uses the same intake surfaces FloxoLab already has on the site: a contact form for structured requests and an AI chat for people who start with a messy question.
The useful workflow is not the chatbot by itself. It is the handoff: what gets saved, who gets notified, and what the human can do next.
Real tools, test data - here is why that is the point
This is a demo workflow, not a finished client system. The point is to show the working pattern: intake, validation, AI response, lead record, private alert, and follow-up email.
Production versions usually need more testing, cleaner edge-case handling, more careful copy, and fields that match the team's real sales or support process. A demo proves the path. Production makes it boring enough to trust.
1. Start with the boring form path
The contact form is the clean path. It already has the fields a human needs: name, email, current tools, budget range, and a short message. The workflow checks whether the email already exists, creates a Notion lead if it is new, sends a private alert, and returns a simple OK response.
2. Let the chat handle messy first messages
The AI chat is for the person who does not know what to put in a form yet. It validates the message, keeps a short safe history, sends a compact instruction set to Groq, and expects a JSON response with reply text, email-offer state, and optional plan data.
The AI prompt is not magic. It is a set of instructions that can be rewritten when the first version does not work.
3. Decide when the workflow should act
The decision point is deliberately plain. If the model says the email is ready and the user has provided enough context, the workflow checks for duplicates, creates a lead, builds an email, and sends it. If not, it simply returns the chat reply.
4. Give the human something useful
The useful handoff is not "a lead arrived." It is a lead record with enough context, a private alert that tells the builder what happened, and a first-pass workflow map the user can reply to.
Demo vs production
A demo can prove the path in half a day. A production workflow needs better copy, fallback paths, duplicate handling, error alerts, cleaner logs, and privacy-safe fields.
Sometimes the hardest production bug is remembering to remove "This message was sent automatically with n8n." That sounds small, but it is exactly the kind of polish that separates a working demo from a workflow a business can comfortably use.
Fields are flexible. The Notion database can have five fields or twenty-five: source, budget, tool stack, urgency, owner, status, next action, or whatever the handoff needs.
Alerts are flexible. The notification can go to Slack, email, Telegram privately, a CRM task, or the channel the team actually checks.
The AI behavior is flexible. It can ask one question, collect missing fields, draft the first reply, or stop and ask a human to review. The prompt is editable.
What can be customized
I can spend 30 days trying to design the perfect intake workflow on paper, or build several working versions in half a day and learn from real messages. For small automations, the second path is usually more useful.
The CRM can be Notion, Airtable, HubSpot, Google Sheets, or something else. The email can be plain text or formatted. The AI model can be Groq, OpenAI, Claude, or no AI at all if the form fields are enough.
Bottom line
This is the kind of workflow automation Philippines teams can inspect: visible inputs, validation before action, AI that returns structured data, a human-readable lead record, and a clear next step.
It is not a giant AI sales machine. It is a small intake workflow that makes the first human response easier.