Nazar P.

Leads, invoices, call recordings, and product copy still wait on someone to copy them from chats and spreadsheets. I design the workflow that runs after the trigger: Make, n8n or ConnectiveOne (n8n analog) moves the data; OpenAI or Google Gemini writes or scores it; Google Sheets, CRM, OpenCart, or Telegram is the output. What I build: • Document extraction: Google Cloud Vision (OCR) plus 19 OpenAI Assistants parse invoices into JSON. Make files them in Drive, skips duplicates, and alerts in Telegram. • Call quality: When a Ringostat call ends, Apps Script logs it to Google Sheets. Make sends the transcript to Gemini. A score below 3.5 fires Telegram; a second red alert is blocked. • Catalog sync: KeyCRM products land in Sheets. OpenAI writes Ukrainian and English name, HTML, and SEO. Confirmed rows go to OpenCart as unpublished drafts; stock fields are not overwritten. • Telegram content: a Gemini reels studio with in-chat approve or regenerate. • Win-back in Telegram: a Gemini agent with a pay-link funnel and stage logging. • Clinic inbox: Telegram, Instagram Direct, Facebook Direct, and Gmail in one operator panel. The operator AI suggests replies from a services knowledge base; it never writes to the patient. • Sales commissions: Apps Script matrix on KeyCRM orders — tiered bonuses, aging rules, one-click manager reports, Telegram on script errors. Reliability: error handlers, retries, send/response logs, and duplicate-alert blocks so a failed push is visible, not silent. Tools on live work: Make, n8n, ConnectiveOne (n8n analog), OpenAI, Gemini, Telegram. If a new row, a finished call, or an inbound chat still needs someone to copy-paste, write me with that workflow.