Development of the Viber channel, inviting the contact database

У нас есть чат-бот на SendPulse и требуется настройка, чтобы через него была возможность оформления подписки на закрытый клуб с помощью Stripe и она продлевалась автоматически каждый месяц, и вот давал возможность управления подписки, а также автоматически открывал и закрывал доступ в случае начала либо её окончания Что уже готово В Stripe создан продукт с ежемесячным списанием и платежная ссылка на него. Бот в SendPulse существует, ведет пользователя к оплате и умеет ставить теги и работать с полями контакта. Не хватает связки между двумя системами: сейчас, если человек оплачивает через Stripe, SendPulse об этом не узнает Что нужно сделать Настроить в Stripe вебхук на события checkout.session.completed, invoice.paid и customer.subscription.deleted Написать обработчик (serverless-функция или готовый no-code инструмент вроде Albato, n8n) который принимает вебхук, достает email клиента и тип события Через API SendPulse обновлять поле или тег контакта (например, club_active = да/нет) в зависимости от события Настроить в SendPulse автоматизацию, которая по этому полю открывает доступ к закрытому каналу при успешной оплате и закрывает при отмене или неудачном списании Подключить Stripe Customer Portal, чтобы участник мог сам отменить подписку или сменить карту, и это тоже долетало до SendPulse через тот же вебхук если у вас есть способ связки легче без сторонних веб-хуков, тоже такое рассмотрим! Что должно получиться на выходе Рабочая цепочка: человек оплачивает в Stripe, в течение пары минут получает доступ к каналу, при отмене или провале списания доступ закрывается автоматически, без участия администратора. Плюс короткая документация: где что настроено, как перезапустить обработчик, если он упадет, и куда смотреть при жалобе участника на закрытый доступ Кого ищем Опыт работы с Stripe API и вебхуками, опыт с SendPulse API (или готовность быстро в нем разобраться, документация открытая), умение поднять простой serverless-обработчик или настроить связку в Albato/n8n. Готовность показать похожий кейс из портфеля будет плюсом

Development of a Telegram bot in Python that collects data and synchronizes it with Google Sheets in real time. The system must be fault-tolerant, protected against manual input errors, and fully autonomous.

What exactly needs to be done and what goals will the work serve? It is necessary to create and configure a Telegram bot that automates user access to closed content on the topic of healthy eating. The link to this bot will be placed in my social media profiles to attract traffic. Important: The project must be implemented exclusively on a Ukrainian no-code platform (for example, SmartBot Pro, SendPulse, or similar). The work will be conducted within my personal account of the constructor (invite me as a developer) using my API token from BotFather. Access to the channel itself will not be provided to the developer — I will add the bot to the admin myself. Logic and functionality of the bot: Start: The user follows the link from social media, launches the bot, and sees a welcome message with a choice of two options: Option A (Free trial): Get 1 month of free access in exchange for entering their Email. The bot validates the email, stores it in the database, and grants access for 30 days. After 30 days, access is blocked, and the bot offers to switch to a paid subscription. Option B (Paid access): Immediately purchase a subscription for a month for Telegram Stars (the price will be discussed, approximately from 100 to 350 stars). Access issuance (2 in 1): After payment or entering the email, the bot must automatically generate and send the user unique one-time invitation links simultaneously to two places: Closed Channel (exclusively for my original materials, videos, and posts where comments are disabled). Closed Chat/Group (for participant communication, discussing meal plans, and my responses to their questions). Subscription control: The bot must automatically count the days. Two days before the end of the month, it should send a reminder about renewal. If there is no payment (or the free month has ended) — the bot must automatically remove the user from both the channel and the chat.Mandatory condition for the performer: I need a specialist with good communication skills. Before starting work and approving the technical task, we must definitely have a voice call (in Telegram or Zoom) so that I can explain all my wishes in detail, and you can suggest the best technical solutions and help finalize the logic. Please write in the comments if you are ready for a call.Who is your product aimed at? Ordinary people (mostly women and men) who are interested in weight loss, diets, and a healthy lifestyle. The bot's interface should be as simple, friendly, and understandable for the client as possible.What criteria will you use to evaluate a successful result? A live call was conducted, and the logic was agreed upon. The bot correctly collects and stores emails for the free period. The bot accepts test payments in Telegram Stars without errors. After a successful action (email or payment), working links to the channel and chat are issued.

I'm looking for a developer to create a Telegram bot for our clothing store. The essence: the manager sends the bot a regular photo of the product (on a hanger, on a table) — the bot generates a ready gallery of professional shots for the product card on the website/marketplace using AI. What the bot should be able to do Receive 1–4 photos of the product in the Telegram chat. Automatically recognize the product (category, cut, male/female) — without manual description. Generate a gallery of ~6 shots: product on a model: studio front, back, dynamic pose; product shots: flat lay, close-up detail, ghost mannequin; lifestyle shot. Consistent model — the same person in all shots of the gallery and between galleries (brand face). Several shooting styles to choose from (for example: streetwear, casual, sport, old money). Output format: JPG 4:5, files with numbering (-01, -02…) — ready for upload. The ability to regenerate a single shot or change the style without regenerating the entire gallery. Access only for our team (allowlist), daily limits per user. Accounting for AI API costs: show the price before generation, keep statistics. Technical expectations Image generation: Gemini (Nano Banana) / DALL·E / Flux or similar — please suggest an option with justification of quality and cost per shot. The bot must operate 24/7 on VPS (auto-restart, turnkey deployment). Secrets via .env, code delivered to us (repository). What we will provide Product photos for testing, wishes regarding brand styling. What I expect in the response Cost and timeline estimate. Approximate cost of one gallery. From and To

General information: There is a Telegram bot written in Python (aiogram v3, aiohttp, MySQL, Redis). This is a service for interaction between clients and performers (profiles, projects, etc.). Required skills: - Confident experience with aiogram v3 (not v2!), asyncio, aiohttp; - Knowledge of Telegram Bot API (webhooks); - Experience with MySQL, Redis; - Ability to understand someone else's code; - Communication skills, responsibility. I need to fix a bug in the current version of the bot directly on the server. The problem is as follows: The chats (Nooks) are not functioning properly; there should be a cleaner that works according to an algorithm, but right now it is working with bugs and not cleaning on schedule. - A chat between the client is needed for discussing work matters with the performer. - Chats (nooks are already created, they need to be cleaned and queued. - The user bot creates chats (pair nooks, which we already have) and puts them in the queue; if a deal is made in the chat, the interlocutors are present (one chat for the performer, another chat for the client); if the chat is closed or there was no deal made and users did not write there for 7 days, the bot removes clients or performers from there and puts this chat (nook) back in the queue. - The client can switch to a chat with any performer who responded to the order. - The client and performer are in two parallel chats, so there is no possibility to see the direct account of the interlocutor and no possibility to write to them directly. * We do not change the operation of the chats and everything else. The main thing is that the fix does not lead to other problems.