Chatbot with acceptance of telegram payments

Technical specification for a Telegram bot Goal: Create a Telegram bot that will: 1. Take posts from one channel (source). 2. Repost them to one or several other channels (receivers) on behalf of the Telegram account. 3. Support: • Text. • Up to 10 photos. • Premium emojis. 4. Replace links in posts according to specified rules. 5. Add inline buttons according to special scripts in the text. 6. Support link and button binding for each receiver separately. Working with links: • There may be links in the post text that need to be replaced. • For each receiver channel, the bot should use its own link. • Example: if the post contains the link https://site.com, then: • For Channel A replace with https://site.com/a • For Channel B replace with https://site.com/b Working with buttons: • The text may contain scripts like: [contact], [website], [order]. • The bot should: • Remove the script from the text. • Add a button with the required text and the required link. • Buttons are configured separately for each receiver channel.

We have a chatbot on SendPulse and need to set it up so that it allows subscription to a closed club via Stripe, which should automatically renew every month, and provide subscription management, as well as automatically open and close access in case of its start or end. What is already ready A product with monthly billing has been created in Stripe, along with a payment link for it. The bot in SendPulse exists, guides the user to payment, and can set tags and work with contact fields. There is a lack of integration between the two systems: currently, if a person pays through Stripe, SendPulse does not get notified about it. What needs to be done Set up a webhook in Stripe for the events checkout.session.completed, invoice.paid, and customer.subscription.deleted. Write a handler (serverless function or a ready-made no-code tool like Albato, n8n) that receives the webhook, extracts the client's email and the type of event. Use the SendPulse API to update the contact field or tag (for example, club_active = yes/no) depending on the event. Set up automation in SendPulse that opens access to the closed channel based on this field upon successful payment and closes it upon cancellation or failed billing. Connect the Stripe Customer Portal so that the participant can cancel the subscription or change the card themselves, and this should also be sent to SendPulse via the same webhook. If you have an easier way to integrate without third-party webhooks, we will consider that too! What should be the outcome A working chain: a person pays in Stripe, receives access to the channel within a couple of minutes, and upon cancellation or failed billing, access is automatically closed without administrator involvement. Plus, a short documentation: where everything is set up, how to restart the handler if it fails, and where to look in case a participant complains about closed access. Who we are looking for Experience with Stripe API and webhooks, experience with SendPulse API (or readiness to quickly understand it, documentation is open), ability to set up a simple serverless handler or configure integration in Albato/n8n. Willingness to show a similar case from the portfolio will be a plus.

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.

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.