Chat bots and workflow automation

TypeScript bots for Telegram, WhatsApp, Discord, Slack, and other messengers—commands, alerts, and glue between chat and your stack.

Messengers are a practical surface for alerts, lightweight admin flows, and user assistants. I build bots and sidecar services in TypeScript on Node.js.

Typical patterns span news bots, payment flows, Home Assistant bridges, and developer notifications. A bot + small API often ships faster than a heavyweight app.

Representative work

Recent deliveries include cursor-telegram-integration and thinklens-bot—systems where chat bots and workflow automation skills (Telegram, WhatsApp Business API, Discord, Slack, TypeScript, Node.js, webhooks, commands, scheduling, CRM/payment hooks, Docker) were applied end to end.

Those projects combined product UI, APIs, and operational concerns: roles, exports, integrations, and observability. The goal is always software your team can extend—not a one-off demo that collapses under real users.

Typical collaboration starts with a written brief: constraints, integrations, compliance, and what “done” means for the first release. We slice work into vertical milestones so you see progress every one to two weeks and can reprioritize without losing the thread.

After go-live we offer a short hypercare window: fix edge cases, tune performance, and transfer knowledge. Long-term support can stay with your in-house team or continue as a retainer—your choice.

We document decisions in plain language, keep staging environments aligned with production, and leave runbooks so your team is not blocked after handoff. If you already have designers or backend engineers, we plug into your rituals instead of inventing a parallel process.

We document decisions in plain language, keep staging environments aligned with production, and leave runbooks so your team is not blocked after handoff. If you already have designers or backend engineers, we plug into your rituals instead of inventing a parallel process.

We document decisions in plain language, keep staging environments aligned with production, and leave runbooks so your team is not blocked after handoff. If you already have designers or backend engineers, we plug into your rituals instead of inventing a parallel process.

We document decisions in plain language, keep staging environments aligned with production, and leave runbooks so your team is not blocked after handoff. If you already have designers or backend engineers, we plug into your rituals instead of inventing a parallel process.

We document decisions in plain language, keep staging environments aligned with production, and leave runbooks so your team is not blocked after handoff. If you already have designers or backend engineers, we plug into your rituals instead of inventing a parallel process.

We document decisions in plain language, keep staging environments aligned with production, and leave runbooks so your team is not blocked after handoff. If you already have designers or backend engineers, we plug into your rituals instead of inventing a parallel process.

FAQ

Tap a question to expand the answer.

Which messengers do you support?

Telegram, WhatsApp Business API, Discord, Slack on the international side; for RU audiences also VK and MAX with shared business logic.

Webhook or long polling?

Webhooks in production when HTTPS is available; polling only for local dev or constrained hosting.

Where does the bot run?

Usually Docker on your VPS or cloud VM; I help with env secrets, restarts, and log-friendly deployments.

How do you handle API tokens safely?

Secrets in environment variables, least-privilege bot scopes, no tokens in git, and rotation guidance when platforms allow it.

Can the bot talk to our CRM or site?

Yes—typical pattern is bot + small REST API to your backend, payment provider, or Home Assistant.