Expert Make.com Engineer Needed for AI Document Processing Pipeline & Client Portal Integration

PLEASE READ: This project operates on a Capped Revenue-Share Partnership Model (15% of monthly Stripe revenue up to a $5,000 total payout cap). Do not apply if you only accept standard cash upfront. Hi, I am launching ForgeOps, an AI-automated invoicing platform built for heavy industries. The app takes unstructured data from PDF field tickets and converts it into clean, structured line items inside a client dashboard ledger. I have already mapped out our workflow roadmap, configured our primary Stripe payment gateways, and built a baseline automation engine on Make.com. However, the Make scenario currently triggers data-type formatting and bundle validation errors during the AI extraction phase. I am looking to hand off 100% of the technical development to an Expert backend automation architect or agency. YOUR DELIVERABLES: 1. Audit and refactor my existing Make.com scenario permanently. 2. Build advanced JSON schema validation and robust error handling (Resume/Break directives) so the system handles non-standard PDF formats without crashing. 3. Fully integrate the Make data flow into a white-label client frontend wrapper (like Copilot), creating a secure dashboard login for file uploads. 4. Link the portal natively to our existing Stripe setup for recurring subscription gates. COMPENSATION MODEL: You will receive 15% of all gross monthly revenue processed natively through our Stripe account. This contract features a strict payout cap of $5,000. Once your 15% payouts reach a total of $5,000, your contract naturally expires and ownership reverts fully to the company. SCREENING QUESTIONS (You must answer these briefly to be considered): 1. When extracting text from an invoice PDF via AI in Make.com, what specific validation step do you implement to prevent downstream database validation errors if an entry field is missing? 2. What exact error-handling directives will you embed inside the scenario to ensure corrupt or non-standard file uploads are routed safely without breaking the runtime loop? 3. Have you successfully integrated Make.com webhooks with all-in-one client portal frameworks like Copilot or SuiteDash?