Automations that solve real business problems.
I'm Sadia Khanam Prity, an automation developer who designs the workflow around the problem — AI chatbots, API integrations, and data sync — not the other way around.
Featured automations
Built to solve a specific problem, not to show off a tool
Each one started as a business complaint — replies took too long, a lead went missing, a photo needed matching by eye. Click through to see the actual node graph.
Services
What I take on
Scoped around the outcome, built with whichever automation platform fits the job.
Automation workflow development
End-to-end design and build of automations that model your actual process, not a generic template.
AI-powered chatbots and agents
Agents that answer, act on tools, and know when to hand off to a person instead of guessing.
API integrations
Connecting the tools you already use so data moves between them without manual re-entry.
Webhook automation
Event-driven flows that react the moment something happens, instead of on a delay.
Data synchronisation
Keeping records consistent across sheets, calendars and inboxes without a manual reconciliation pass.
Scheduled and recurring jobs
Reports, digests and housekeeping tasks that run on their own schedule, reliably.
Automation consulting
An outside read on where manual work is costing the most time, and what's actually worth automating first.
Tech stack
Only what's actually shipped
No inflated list — everything here has been used in a live workflow.
Automation Platform
- n8nCurrently primary — workflow orchestration
- WebhooksEvent triggers
- REST APIsService integration
- OAuth2Authenticated access
AI
- Google GeminiText and vision
- Groq API — Llama 3.1Fast structured generation
Integrations
- Meta Graph APIMessenger
- Google SheetsData store
- Google CalendarScheduling
- Gmail APIEmail
- Telegram Bot APIAlerts
- TwilioWhatsApp / SMS
- OCR.spaceText extraction
Frontend
- Next.jsFramework
- TypeScriptLanguage
- Tailwind CSSStyling
Case studies
What changed after the automation shipped
The long-form version — the situation before, what was built, and why it holds up.
About
Sadia Khanam Prity
I design against the business problem first — the tool it ends up running on is whichever one fits fastest and hands over cleanest, not the point in itself.
A workflow I hand over should be readable by whoever inherits it: clearly named nodes, sensible error handling, no cleverness for its own sake.
Contact
Tell me what's manual today
A couple of sentences about the problem is enough to start. I reply within 24 hours.
This form runs on the same kind of automation stack described above — it classifies, routes and lets me know the moment it lands.