Fórum n8n Community

cd C:\n8n-sandbox

Which directory?

Where did you run the command?

is it inside the docker n8n folder that i have posted earlier??

Sonam_Chophel: dont find any api key and URL It is in the .env file

thank you. But dont find any api key and URL

Sonam_Chophel: Is the Service URL and the API key insidde this docker If it is running from the same directory, then yes

Hi Rami, Thanks — happy to clarify. I don’t currently have a finished synthetic RFQ demo that matches your exact workflow, so I don’t want to present something as existing proof when it isn’t. My closest relevant work is around backend automation, structured data workflows, APIs/webhooks, document-driven processing and CRM-style operational systems. For your RFQ flow, the implementation I proposed would be: PDF input → text/table extraction → normalize product code / quantity / unit → exact match against the catalogue → validate price against the approved versioned price list → flag unmatched/ambiguous rows → generate the Excel quote draft. The important part is that the workflow would not guess prices or silently substitute uncertain matches. Anything below the agreed confidence/rule threshold would be surfaced for review. Yes, I would personally review the implementation and handle fixes. I’d include 7 days of post-acceptance bug-fix support for issues within the agreed scope. New features or scope changes would be handled separately. For the quoted Phase 1 scope, I can include: AED as the pricing currency Arabic/English Excel headings a separate, versioned approved price-list source editable source code and workflow files permission for you to modify and deploy the delivered solution for your client projects I would only retain the right to reuse generic/non-client-specific utilities or patterns; your client data, catalogue, price lists and project-specific configuration r

Is the Service URL and the API key insidde this docker after executing the step given earlier

I built this n8n lead-management demo to organize incoming enquiries and make qualified leads easier to follow up on. The business scenario A business receives website enquiries containing a name, email address, requested service and budget. Manually reviewing each enquiry and updating a spreadsheet creates repetitive work. How the workflow works • A webhook receives the enquiry. • An IF node checks the lead against a budget-based qualification rule. • Each branch assigns a lead status. • Google Sheets records the enquiry and its status. • Qualified leads also trigger a Gmail notification. Both branches keep a record of the enquiry, so leads that do not meet the qualification rule remain available for review. Tools used n8n, Webhooks, Google Sheets and Gmail. About this demo This is a demonstration project using sample data. The qualification criteria can be adapted to a business’s requirements. The screenshot shows the workflow structure. I’m happy to discuss the setup, field mapping and routing logic with other builders. How would you extend this for your business—duplicate detection, assigning a lead owner or follow-up reminders?

You can do it yourself. Just run curl -fsSL https://get.n8n.io | sh