Configuring the adding of participants to the dialogue in amocrm

A technical specialist is required to assemble the architecture and logic of an interactive bot. The project is a gamified product with a deep storyline (U.S. market). What needs to be done: Transfer the finished script (dialogue tree) into the working logic of the bot. Set up strict timings, delayed messages, and conditions (if/else) depending on user actions. Implement the ability to integrate audio files and call external APIs. Platform: to be discussed. Suggest the optimal builder (ManyChat, SendPulse, etc.) or a custom solution if it is more feasible. Important: Your task is specifically the engineering assembly of the script into a functioning, fail-proof mechanism. The complete script will be provided to the selected specialist. In your response, please include: 1. Describe your experience in assembling bots with complex branching (autoresponders, gamification). 2. Which platform would you recommend for the bot, where messages must arrive strictly on a timer the next day (considering time zones), and why? 3. Provide your cost for completing the project and estimated timelines.

Technical task for a Telegram bot / mini-platform 1. Project goal Create a Telegram bot and mini-platform for finding specialists and posting requests from users. The user can leave a request, the specialist can respond, the administrator controls publications, moderation, payment, and security. 2. User roles User: can register; confirm phone number and email; create a request; view specialists; receive responses. Specialist: can register; fill out a questionnaire; specify services, prices, city, experience; add photos of completed work; respond to requests. Administrator: can moderate requests; verify specialists; review complaints; manage advertising; control payments; block users. 3. Registration Mandatory: confirmation of phone number via Telegram or code; confirmation of email via link or code; without confirmation of phone and email, the request is not published. 4. Requests The user fills out: service category; task description; city/region; deadline; budget; photo (if necessary); contact details. Limitations: no more than three requests per day from one user. 5. Moderation All requests initially go for moderation. Automatically block or send for manual review: photos of category 18+; spam; offensive statements; suspicious links; duplicate requests; mass requests from one account. 6. Specialists Specialist questionnaire: name; city; services; experience; prices; portfolio; photo; description; link; reviews; verification status. Important: the platform is not responsible for the quality of the specialist's services. This must be stated in the user agreement. 7. Payment Monetization options: paid placement of the specialist's profile; paid boosting of the profile; paid access to requests; advertising after approval by the administrator; subscription for specialists. Integrate payment: Stripe / Przelewy24 / PayU / Fondy — as per the developer's capabilities. 8. Administrative panel It is necessary to create a convenient admin panel: list of users; list of specialists; requests under moderation; complaints; payments; statistics; blocking users; editing categories; managing advertising; manual approval or rejection of publications. 9. Security Mandatory: protection against spam; request limit; message limit; protection against mass registrations; action logging; database backup; file and photo verification; CAPTCHA or other spam protection mechanism; blocking by phone number, IP address, or Telegram ID. 10. Responsibility The user agreement must specify: the platform is not an employer; the platform is not responsible for the actions of specialists; the user independently makes decisions about cooperation; the administration has the right to delete a request or profile without explanation; advertising is published only after approval by the administrator; spam, fraud, 18+ content, and any manifestations of aggression are prohibited.

Need a DevOps / Linux administrator for deploying a Telegram bot on a VPS. Specifically, server setup and production deployment are required. Project stack: Node.js 20+, Telegraf, Express, Prisma, PostgreSQL, Redis, Docker, Docker Compose, Telegram Mini Apps, OCR. What needs to be done: 1. Prepare Ubuntu VPS. 2. Set up SSH access with keys. 3. Configure the firewall. 4. Install Docker and Docker Compose. 5. Set up PostgreSQL. 6. Set up Redis. 7. Configure Nginx. 8. Connect the domain and SSL Let’s Encrypt. 9. Configure production .env. 10. Run Prisma migrations. 11. Launch the Node.js application. 12. Set up Telegram webhook. 13. Check /health and /ready. 14. Set up PostgreSQL backup. 15. Leave instructions on how to update, restart, view logs, and restore backup. Important: - No need to rewrite the code. - The project needs to be deployed on a VPS. - A person with experience in Docker + Node.js + PostgreSQL + Redis + Nginx is required. - It is preferable to show 2–3 similar projects.

Good afternoon. I need a keyword parser that outputs results through a Telegram bot. How it should work: Automatic search on 4 websites for keywords that change from time to time. Search queries are sent every few minutes. The words are uploaded in the form of a .txt file. The Telegram bot should have buttons: start bot, stop bot, download file (downloads a file with active keywords), upload file (uploads an edited file with new words). The bot should ignore previously found results, i.e., it should not indicate the same ad twice. The result comes to the bot in the form of a link with a photo, but just a link is sufficient. P.S. searching websites without API, VPS with 6TB and 50 IPs are already available. For detailed information, please contact me via private message.

Development of a Telegram Mini App (store) with CRM and Nova Poshta integration It is necessary to develop a Telegram Mini App (store inside Telegram).Main functionality A catalog with approximately 20 products is needed. For each product: photo; name; description; price; model selection; color selection; quantity. Order processing The client must have the ability to: view the catalog; add products to the cart; change the quantity; place an order; enter: name; phone; city; Nova Poshta branch number; payment method; order comment. CRM All orders need to be automatically transmitted to the CRM via API. It is preferable that the integration is universal and in the future, the CRM can be changed without a complete redesign of the project.Nova Poshta Integration with the Nova Poshta API is needed or data transfer to the CRM if the creation of the shipping document will be done by the CRM itself.Administrator A simple administrator mode is needed: adding and editing products; changing prices; changing stock levels; adding new colors or models. Important The project must work as a Telegram Mini App (not a regular bot with buttons). The code, database, and all access after the completion of work must belong to me. The architecture must allow for additional features to be connected in the future without a complete redesign. Please inform: Estimated cost. Completion time. What technology stack you plan to use. Do you have experience in developing Telegram Mini Apps and integrating with CRM and Nova Poshta API.