Raheeb Rehman

Raheeb RehmanSep 2, 2026

Excited to share that my open-source contribution to NanoCoder has been merged! I implemented bundled project presets that allow developers to initialize NanoCoder with stack-specific configurations using: nanocoder init --preset <type> The feature currently supports React, Next.js, and Rust, generating: ✅ Stack-aware AGENTS.md instructions ✅ A tailored .nanocoderignore file ✅ A reusable /check command ✅ Safe file handling that preserves existing configurations ✅ Clear validation for unsupported presets I also added automated tests covering preset resolution, file generation, invalid inputs, existing-file preservation, and the default initialization flow, all 16 focused tests passed. Taking this from an open issue to a fully tested and merged feature was incredibly rewarding. It challenged me to think beyond simply making the code work and focus on building something reliable, safe, and genuinely useful for other developers. A big thank you to the Nano Collective maintainers for reviewing and merging my contribution! 🔗 Pull request: https://lnkd.in/de6b_9Ef #OpenSource #TypeScript #SoftwareEngineering #DeveloperTools #AICoding #NextJS #GitHub

Raheeb RehmanApr 11, 2025

I’m happy to share that I’m starting a new position as Software Developer at Synoptix AI!

Raheeb RehmanAug 14, 2026

Most lead follow-ups don’t fail because teams lack leads. They fail because the next action is late, inconsistent, or disconnected from the customer’s reply. I built this n8n workflow for a dealership lead follow-up system, with separate outbound and inbound communication flows. The outbound flow starts when a new lead is submitted. It normalizes and validates the data, checks consent, prevents duplicate events, verifies whether the customer is already on a permanent suppression list, and confirms that contact is allowed during the customer’s local timezone. If the lead is valid, the workflow prepares a personalized SMS and waits for the configured delay before continuing. It also checks suppression again before contact, so a customer who opts out during the waiting period is not contacted afterward. The workflow then monitors for a reply. If there is no response within the follow-up window, it checks whether a voice attempt has already been made and prepares a fallback call path without creating duplicate attempts. The inbound flow receives the customer’s reply, finds the related lead by phone number, combines the lead data with the incoming message, and classifies the response as: • Interested • Not interested • Opt-out • Unclear Each response is logged and routed accordingly to the dealer queue, a closed-follow-up list, a permanent suppression list, or human review. The workflow also maintains an audit trail using n8n Data Tables. It is currently running in preview mode while Twilio credentials and production webhooks are finalized. The core automation logic, safeguards, routing, and logging are already in place. P.s: The lonely node at top is TWILLO as free trial isnt available for some reason so I made the flow work but when it'll go in production that node would be connected in workflow. #n8n #WorkflowAutomation #Automation #CRM #LeadManagement #Integration