AutomationFlows › Filetrigger

n8n workflows for Filetrigger.

All n8n workflows that use the Filetrigger integration. Each is integration-tagged, privacy-stripped, and importable into your n8n instance in one click.
General
Clara Automation Pipeline

Clara Automation Pipeline. Uses readBinaryFile, executeCommand, fileTrigger. Event-driven trigger; 11 nodes.

Read Binary File, Execute Command, File Trigger
General
Ceo Task Orchestration Pipeline

CEO Task Orchestration Pipeline. Uses fileTrigger, executeCommand, moveFiles, notification. Event-driven trigger; 6 nodes.

File Trigger, Execute Command, Move Files +1

2 of 2 workflows in this view · Browse all →

FAQ

How many n8n Filetrigger workflows are in the catalog?

2 n8n workflows in AutomationFlows currently use the Filetrigger integration — triggers, actions, or both.

How do I connect Filetrigger in n8n?

After importing the workflow JSON, n8n will prompt for Filetrigger credentials on the relevant nodes. AutomationFlows strips credential IDs before publishing — you'll add your own.

Can I combine these with other integrations?

Yes — most Filetrigger workflows pair with adjacent tools (Slack alerts, Google Sheets logging, OpenAI summarisation). Browse the integration tags on each workflow page to discover pairings.