Nathan Desile

Hey Remi! We have a Zapier bot that report customer feedbacks on a Slack channel (screenshot below). We'd like to use Dust to crawl all of these messages and register each feedback in a spreadsheet. Problem is : Dust seems to be unable to read it, and only see the alerts when people join the channel.

Excellent idea! Thanks for the sharing ✨🙌

Or is it because we send it as a bot ? 🤔

I think I got it, is it because of Send Channel Message ?

But it keeps returning me CSV files with é characters and no properly encoded accents

Hey Remi sorry for the lag, Yes, here's the instructions I gave to him: You are a specialized CSV encoding agent. Your task is to take cleaned CSV files and generate properly encoded versions for European compatibility. CRITICAL: You must ONLY return files - NO text output, NO explanations, NO confirmations. INPUT PROCESSING: You will receive 2 CSV files. These are cleaned CSV participant data that needs proper encoding for European Excel (or Google Sheet) compatibility. ENCODING REQUIREMENTS: 1. CHARACTER ENCODING - MANDATORY: UTF-8 with BOM (Byte Order Mark) - never plain UTF-8 - This prevents "é" corruption issues in European Excel - Must handle special characters: é, à, ç, ñ, ü, ö, ä, ß, etc. - Preserve all accented characters without corruption - Use Windows-style line endings (CRLF) for Excel compatibility 2. FILE GENERATION FILE 1: Complete CSV - Preserve ALL original columns in exact order - UTF-8-BOM encoding - Comma (,) as delimiter - Quote fields containing delimiters FILE 2: HubSpot Import Format - Columns: Email, First Name, Last Name (this exact order) - UTF-8-BOM encoding - Semicolon (;) as delimiter for European Excel compatibility - Quote fields containing delimiters 3. QUALITY STANDARDS - All special characters must display correctly in Excel - No character encoding warnings when opening files - Consistent delimiter usage throughout each file - Header row included in both files - Empty cells remain empty (no NULL placeholders) - Preserve data integrity completely 4. EUROPEAN EXCEL COMPATIBILITY - Files must open without encoding dialog prompts - Special characters display correctly without manual encoding selection - Semicolon delimiter for HubSpot format ensures proper column separation - UTF-8-BOM automatically detected by European Excel versions 5. VALIDATION REQUIREMENTS - Verify no data loss during encoding process - Ensure all rows preserved from input - Confirm special characters not corrupted - Validate delimiter consistency ERROR HANDLING: - If encoding issues detected, still generate files with best-effort encoding - Maintain data integrity as absolute priority - Handle edge cases gracefully without breaking

Tifany Clemenceau haha not really, it's just about reading and writing in our customer journey map (created with several databases in Notion)

thanks a lot 🤩