Expert Integration Engineer: Make.com, Stripe Metered Billing, & API Webhooks

Title: Expert Integration Engineer: Make.com, Stripe Metered Billing, & API Webhooks Category: Web, Mobile & Software Development - Automation & Integration Job Type: Fixed-Price / Project-Based Budget: $550 Project Duration: Less than 1 week (3-4 Days Sprint) Experience Level: Expert (Make.com Certified Preferred) PROJECT OVERVIEW We are launching a highly secure, automated SaaS document-ingestion and forensic-assembly platform. CRITICAL SCOPE DETAIL: All front-end user interfaces, graphic layouts, form field configurations, and copy vectors are 100% COMPLETED and live via Fillout. Your technical scope is strictly restricted to backend data routing, webhook architecture, and multi-system API mapping. The prioritized middleware automation engine for this build is Make.com. CORE WORKFLOW DELIVERABLES 1. Dynamic Authentication & Inbound Routing: Configure a master webhook listener in Make.com to parse an inbound portal metadata parameter. If populated, authenticate the user as a B2B Partner and bypass the billing wall. If blank, route the user to a public Stripe credit card checkout page. 2. Multi-State Lookup Matrix & Triage Flags: Create a multi-variable lookup table inside Make.com. Read an inbound string field (State) and cross-reference it against an internal dynamic threshold matrix to evaluate a user-selected numerical value bracket. Depending on the Boolean result and user preference data flags, conditionally execute a real-time background webhook POST request to route the payload to either an external priority partner API endpoint or a local Twilio SMS alert node. 3. Stripe Metered Billing & Subscription Tracking: Build the usage-reporting API node inside Make.com. Every time a validated portal account completes an intake form, your pipeline must automatically report 1 unit of usage to the Stripe Metered Billing API under a pre-configured Price ID. Ensure the loop seamlessly interacts with and respects native Stripe subscription trial windows. 4. B2C Pay-On-Use Shipping & Mailroom API: Connect a commercial shipping API (Shippo) and a third-party commercial digital mailroom API into the pipeline. If a specific upgrade SKU is present on the successful Stripe invoice payload, trigger a POST request to generate a scan-based (pay-on-use) return label, appending a transaction string suffix to the recipient line. Set a separate webhook listener to catch when a physical document package is digitized at the mailroom, extract the clean multi-page PDF link, and push it straight into the primary parsing engine. 5. Bank-Grade Security & Immediate Zero-Retention Scrubbing: To pass continuous automated penetration testing, all handle parameters must utilize HTTPS/TLS protocols. Enable the "Data is Confidential" / No-Logging features natively across all Make.com scenarios handling PDF arrays. The final generated files must NEVER be sent as raw email attachments. Upload the completed multi-page Master PDF straight into an encrypted cloud storage bucket (AES-256) and write the private link variable directly to the user's specific database row. You must establish an automated post-execution script node: the exact second the file download is successfully executed by the user from the portal interface, the raw uploaded documents and output PDFs must be permanently purged, scrubbed, and deleted from our cloud servers and web cache completely. 6. Staging Environment & QA Health Boto: Build and wire all initial scenarios inside an isolated Staging Environment. Attach active Break/Ignore Error Handler Directives to our PDF parsing and external API modules to prevent session crashes. Construct an independent, scheduled synthetic health-check bot that pulls a static dummy file once a week, processes it, and freezes the loop with a high-priority alert webhook if the mathematical output deviates by even $0.01 from a known baseline. PRE-SCREENING APPLICATION QUESTIONS 1. Explain how you would structure a background lookup table inside Make.com to dynamically cross-reference 50 different state financial limits without changing front-end form fields. 2. What specific structural workflows do you implement within Make.com to ensure sensitive user file payloads remain secure and are completely purged immediately following a successful download step? 3. This is an urgent, highly structured 3-4 day sprint. Are you fully available to initiate backend connections immediately upon contract signature?