As a result, all agreed functionality works correctly, and the outcome meets expectations. I am satisfied with the collaboration.
Budget: 27000 UAH Deadline: 14 days
Vadim, I see here not just automation, but a working tool for daily use: rotation, scheduler, monitoring, and Excel synchronization need to work without manual adjustments. I have already done Python automation, parsing, and integrations with databases and external services, so I will quickly dive into your MVP logic, Playwright, and SQLite. I will pay special attention to universal categories and queue stability. I am ready to discuss details and risks.
Budget: 27000 UAH Deadline: 12 days
Good day! I develop in Python, have worked on similar projects with React/Node.js, and am ready for collaboration.
Budget: 27000 UAH Deadline: 14 days
Hello. Basically, everything described will be implemented with the specified technologies, but it is still necessary to familiarize yourself with the code before execution to avoid wasting time if the deadlines are critical.
Budget: 27000 UAH Deadline: 14 days
Look, there's a nuance here - if stage 1 is already working and the code can be expanded without rewriting the foundation, then 27,000 UAH and 12-14 working days seem like a reasonable estimate for stage 2. If after the review it turns out that the working version relies on temporary solutions, I would simplify things - a short technical check of the code within the marketplace, then a final breakdown by modules.
Regarding implementation, I wouldn't complicate it - separate services within the application for rotation, scheduling, URL monitoring, account groups, and Excel synchronization. Playwright works through saved profiles, SQLite stores statuses and history, and PySide6 displays the queue and errors in a way that the manager sees not magic, but a manageable tool. It seems to me that the main risk is not in the buttons, but in the stability of accounts, limits, and the behavior of Bazoš.cz.
From similar experience Ingello
> https://business.ingello.com/forma-bpm - automation of business processes, statuses, queues, rules, and action logs
> https://business.ingello.com/forma-crm - accounting interfaces, roles, filters, working tables
> https://business.ingello.com/vorfahr - indirectly close in automating product scenarios and system logic
The main profile for such systems - https://systems-fl.ingello.com
What I need from you is the code for stage 1, a test Excel file, a set of test accounts, proxies if they are used, Czech PSČ for probing Bazoš.cz, and a list of categories that we consider mandatory for acceptance. Access can be provided within the marketplace rules.
I want to clarify 2 things, so we don't play architectural shamanism =)
> does stage 1 already have stable session storage for accounts or does this need to be strengthened?
> for sold and inactive, do we definitely delete rows from Excel or is it better to mark them with a status by default?
Budget: 27000 UAH Deadline: 7 days
Hello, I worked on a Desktop application for automating ads on OLX using Python + Selenium, where we processed over 500 ads daily with rotation across 15 accounts and an automatic schedule. It is very similar to your Bazoš.sk project with the same challenges of account management!
I am curious if you plan to integrate a proxy system to work with different regions of Slovakia, considering you use postal codes for localizing ads?
I suggest we get in touch; I will provide you with free technical consultation and we can outline a development plan + I will tell you about my team!
Budget: 26999 UAH Deadline: 13 days
Good day.
I have read the specifications in full. We have experience with similar projects.
The stack Python + Playwright + PySide6 + SQLite + Excel is our specialty. We have done automation with anti-bot circumvention and multi-accounting on several projects.
A few points regarding implementation:
Schedule. APScheduler is suitable, but for PySide6, QTimer is better for the main loop plus a separate thread for publications. It does not block the UI during the bot's operation.
URL monitoring. When checking, it is important to distinguish between types of inactivity: removed by moderation, removed due to time, temporary network error. This helps the manager understand the reason.
Universal engine. Mapping category/subcategory through a separate JSON or YAML file, without recompilation. The manager can add new subcategories themselves.
Excel sync. Matching through product_id as the primary key, title as fallback. When writing via openpyxl, preserving the file formatting.
Limit of 50 ads. In addition to the log, it would be good to make push notifications in Telegram or email to the manager, so they don't have to wait until they open the app.
Probe Bazoš.cz is ready to be done in parallel with the main development.
Before starting, I am ready to show a prototype of one block (schedule or URL monitoring) so you can see the approach to the code.
I await your message in private.
Budget: 27000 UAH Deadline: 14 days
The task is clear: to expand the MVP into a full-fledged production tool with rotation, a scheduler, monitoring, and two-way Excel sync using Playwright + PySide6 + SQLite.
The stack is familiar, I will implement all modules from Stage 2: rotation with intervals per account, reserve status, control limit of 50 listings, scheduling in two modes, status monitoring, universal category engine.
12–14 working days, 27,000 UAH.
Is there already a database schema and UI mockups from the first stage, or are we starting from scratch?
Budget: 27000 UAH Deadline: 3 days
Hello! Your project looks very interesting. I am ready to start working immediately and ensure high quality.
Budget: 27000 UAH Deadline: 14 days
WELL, it’s more like this - for the deadline of 12-14 working days and a budget of 27,000 UAH for stage 2, this looks realistic.
I would simplify it - bring the MVP to a working manager tool through separate modules for rotation, scheduling, monitoring, account groups, synchronization with Excel, and a universal engine for simple categories of Bazoš.sk.
An important nuance I see - with a limit of 50 active listings, the bot should not delete old publications by itself, but should stop the queue by account and show a clear log.
From my feelings, the main risk area here is not the interface, but the stable automation of Bazoš forms, the statuses of listings, and the careful matching of Excel by product_id.
> I will clarify 2 points
> Is the Czech PSČ for probe Bazoš.cz already available, or will it need to be obtained before the start of the check?
> In Palets.xlsx, is product_id present for all rows, or do some products still need to be matched by title?
> Similar cases Ingello
> https://business.ingello.com/vorfahr - close in terms of operation automation, queues, and publication logic through external services
> https://business.ingello.com/forma-bpm - close in terms of statuses, workflows, logs, and task management for the manager
> https://business.ingello.com/prime-eva - indirectly close in terms of product data, integrations, and operational automation
Access to test accounts Bazoš.sk, proxies, the original Excel file, and the current MVP version are needed.
The main page of the team - https://systems-fl.ingello.com
Overall, it’s fine, we don’t need to complicate things - first, we close the stable stage 2, and we leave Bazoš.cz as a separate confirmed stage after the probe =)
Proposals are currently absent
Current freelance projects in the category Bot Development
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.