I just finished making a site, it has multiple ways emails are stored, I made a n8n workflow that gets the stored emails, checks if it has not been added onto a spreadsheet before, deduplicates it, then adds it to a spreadsheet. This workflow runs anytime a new email is submitted. This is my first time using n8n, is this dangerous? in the sense that having a n8n workflow that can be triggered directly by users, can it cause massive usage spikes in memory, etc very easily when its dependent on what a user can do? even if i ratelimit it, because I dont know the overhead n8n has, it takes a minute for the workload to finish also.

  • frongt@lemmy.zip
    link
    fedilink
    English
    arrow-up
    5
    ·
    8 hours ago

    I’m not familiar with n8n, but any time you accept user input, it’s dangerous. What happens if a user submits 10,000 emails per second? What if they submit user@example.com'; DROP TABLE emails; --, or whatever the n8n equivalent of SQL injection is? What if they submit ,,,,,,,,,,,,,,,,? What if they submit a blank field? What if they submit completely invalid random binary data? What if they submit a very, very, very long email address?