Senior Make.com Expert Needed: Fix ShipStation Webhook & Logic Mapping Project Overview I have an automation scenario in Make.com that is 90% built but is currently failing due to a specific "mapping ghost" in the logic and a webhook connectivity issue. The goal is to trigger a billing attempt in a subscription app via API the moment a return package is scanned "In Transit" by the carrier. The Technical Challenge The scenario is currently "stuck" at the filter immediately following the Webhook. The Glitch: A recent audit from Make Support confirmed the filter is incorrectly referencing a collection that doesn't exist in the Webhook's flat data output. Webhook Issue: The ShipStation (V2) Track Event Webhook is not reliably triggering the scenario. Broken Mappings: Because modules were deleted and re-added during troubleshooting, several "pills" (variables) in the Shopify and HTTP billing modules are broken and need to be re-mapped to the correct outputs. Workflow Steps Trigger: ShipStation Webhook. Filter: Must identify a specific status code (e.g., IT for In Transit). API Call: HTTP module fetches shipment details from ShipStation. Data Store: Deduplication check to prevent double-billing. Shopify Search: Locate customer order based on payload. Billing: Final API call to process a billing attempt. Freelancer Requirements Expert level in Make.com (specifically handling JSON payloads and HTTP requests). Experience with ShipStation API and Shopify API. Ability to troubleshoot and fix Filter Logic errors and Variable Mapping issues. Capability to implement robust Error Handling to ensure the scenario doesn't shut down on minor API timeouts. Deliverables A fully functional, glitch-free scenario tested across multiple tracking statuses. Final audit of all module mappings to ensure they are pointing to the correct data sources.