Automation builder · Philippines UTC+8

Useful automations for small teams

I build forms, chatbots, AI agents, and workflows with Zapier, Make, n8n, and the tools you already use. Based in the Philippines, working with small teams worldwide.

Good automation usually starts with one annoying task: a form, a follow-up, a report, or a record someone updates by hand. We map the smallest useful version first.

Services

Useful workflows. Built around your tools.

Forms, chatbots, AI agents, Zapier, Make, n8n, CRM automation, email workflows, reporting, and tool integrations for small teams.

Smart forms and lead capture

Useful forms for leads, bookings, requests, and internal intake. The goal is clean data and fast follow-up.

AI chatbots

Simple website or internal bots that answer common questions, collect details, and know when to hand off.

AI agents for repetitive tasks

Small helpers for summaries, tagging, drafting, routing, research, and other repeatable admin work.

Zapier / Make / n8n workflows

Workflows that connect the apps you already use. Zapier for speed, Make for visual logic, n8n for control.

CRM, email, spreadsheet automation

Keep contacts, notes, reminders, and status fields in sync across the tools your team opens daily.

Reports and notifications

Daily summaries, alerts, and exception reports that show what changed and what needs attention.

Process

A simple build process. No mystery in the middle.

We start with one annoying task, build a working version, test it, and leave you with a setup you can understand.

01 Map the task

We write down the trigger, the tools involved, the data needed, and the result you want.

02 Choose the right tool

Zapier, Make, n8n, forms, chatbots, or custom code. The tool should fit the job, not the other way around.

03 Build a first version

I build the smallest working version first, then test it with sample data and real-looking edge cases.

04 Go live carefully

We connect the real accounts, watch the first runs, and make sure failures are visible instead of silent.

05 Handoff or support

You get short notes you can understand. If you want support, we keep it running and adjust it as your process changes.

Pricing

Start with one useful workflow. Grow only if it works.

Pricing depends on complexity, tool limits, and support. A small local workflow should not be priced like a big agency build.

Workflow audit — from PHP 1,000

One manual process reviewed. Tool, cost, and limit notes. Simple next-step recommendation. Good fit / not worth it call.

Simple automation — from PHP 2,500

Forms, lead trackers, alerts, simple reports. Basic Zapier, Make, n8n, or chatbot setup. Short handoff notes included.

Workflow buildout — from PHP 8,000

Multiple tools or handoff points. AI drafts, agents, or review steps if useful. Testing, failure notes, and screenshots.

About FloxoLab

Practical automation help. Directly from the builder.

FloxoLab is run by Stepan Nikonov, an automation builder based in the Philippines (UTC+8). I work directly with small teams using Zapier, Make, n8n, forms, chatbots, AI agents, Google Sheets, Airtable, Notion, Gmail, and Slack.

We start with one task, choose the tool that fits, and keep the setup understandable after handoff. No large agency rebuilds, no vague AI strategy decks.

Contact: [email protected] · LinkedIn

FAQ

Questions small teams ask. Plain answers.

Do you only work with n8n?

No. I use Zapier, Make, n8n, forms, chatbots, AI tools, and simple custom code when needed. The best tool depends on the workflow, budget, and how much control you want.

What should I automate first?

Start with a task that has a clear trigger and a clear result: a new lead, a paid invoice, a support request, a weekly report, or a repeated follow-up.

Can you help me choose between Zapier, Make, and n8n?

Yes. Zapier is usually fastest for simple automations, Make is strong for visual branching, and n8n is useful when you need more control or self-hosting.

Can you work with my existing tools?

Usually yes. If your team already uses Google Sheets, Gmail, HubSpot, Airtable, Slack, Telegram, Notion, or similar tools, I build around that instead of forcing a new stack.

What happens if something breaks?

A good workflow should make failures visible. I include simple notes about where it runs, what can fail, and what to check first.

How do we work across time zones?

I am based in the Philippines, UTC+8. I work async-first with written updates, screenshots, and short walkthroughs.

Can I maintain it myself later?

That is the goal. I keep the setup understandable and include handoff notes.