New file in SharePoint or Google Drive should be processed automatically

File triggers are popular but have nasty pitfalls: trigger on all changes (including rename), run per user, sometimes miss files in sub-folders. Pin the trigger context first, then process.

Try this first

1. 1Pick the right trigger: 'When a file is created' (new only) versus 'When a file is created or modified' (updates too). Wrong choice gives double processing.
2. 2Scope to one specific folder, not the whole site or drive. Recursion on or off depends on the tool, test deliberately.
3. 3Prevent self-trigger: if your flow moves or renames the file and the trigger listens on modify, you're in a loop. Move to a folder outside trigger scope.
4. 4Read file content in a separate step, not in the trigger itself. Big files sometimes time out the trigger step.
5. 5Store file id or path as dedup key, otherwise a rename or permission change triggers re-processing.

None of the above fits?

Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.