Project Description We are looking for an experienced n8n developer to build an end-to-end automation workflow for AML/KYC compliance checks (LCB-FT) on French companies identified by their SIREN number. The workflow includes a public-facing web form, API integration with Pappers, structured Excel output stored on a server, and automated email delivery of results to the user. Functional Specifications 1. Web Form (n8n Form Trigger) Field 1 : Single SIREN number input (numeric, 9 digits) Field 2 : Excel file upload (.xlsx) containing a column named "SIREN" with multiple entries Field 3 : Email address (mandatory) — used to deliver results The two SIREN input fields are mutually exclusive — the user fills one or the other Form accessible via a stable public URL 2. Input Processing If single SIREN : format as a single-item list and pass to the API call step If Excel file : parse the file, extract the SIREN column, validate format (9 digits), and pass the full list to the API call step Handle errors : missing column, wrong format, empty file 3. API Integration — Pappers Endpoint(s) already identified and tested — Python code provided by client Translate calls to n8n HTTP Request nodes (or execute Python script via Code/Execute Command node if simpler) Process each SIREN individually (Split in Batches) Handle API errors per SIREN (not found, rate limit, timeout) without stopping the full batch 4. Output Formatting & Storage Aggregate each SIREN results into a structured Excel file (.xlsx) One file per SIREN with relevant LCB-FT fields returned by Pappers (beneficial owners, legal status, alerts, etc.) A dedicated column for errors (SIREN not found, API error, invalid format) when applicable Store the output file on a designated server (FTP, SFTP, or S3 — to be confirmed with client) File named with timestamp : lcbft_SIRENnumber_YYYYMMDD_HHMMSS.xlsx 5. Confirmation Page (Success) After successful processing, display a custom n8n confirmation page including : Number of SIREN successfully processed Number of SIREN with errors Message informing the user that the Excel file has been sent by email Content must be dynamically injected from workflow data 6. Error Page (Global Failure) If the workflow fails entirely (e.g. unreadable Excel file, Pappers API unreachable), display a distinct n8n error page with : An explicit error message describing what went wrong An invitation to retry or contact support 7. Email Delivery On success : send an email to the address provided in the form with : The Excel results files as an attachment A summary in the email body (X SIREN processed, X errors) On partial errors : same email with the Excel file attached, including a dedicated column or section listing failed SIREN with error reason On global failure : send an alert email with a description of the error and the original input file attached, to allow the user to resubmit Sender configurable via SMTP node Technical Requirements n8n (cloud) Pappers API (credentials provided by client) Input : n8n native form + Excel file upload Output : .xlsx files written to server + emailed to user Error handling at each step (form validation, API errors, file write failures) Clean, documented workflow (node naming, sticky notes for logic explanation) Deliverables Exported n8n workflow JSON (importable) Brief documentation (1 page) explaining the workflow structure and how to maintain it Test report showing results on a sample SIREN list Questions for Applicants Delivery time : when can you deliver this project once kickoff is confirmed? Price : What is your fixed price for this project? (Fixed price only, no hourly rate) n8n experience : Describe your experience with n8n — number of workflows built, types of integrations, and if possible share examples or screenshots API & file handling experience : Have you previously worked with APIs and Excel file processing (input/output) in n8n workflows? If yes, please describe briefly