Why is my n8n workflow not triggering automatically?

Dev

If your n8n workflow is not triggering automatically, there are a few common causes to investigate depending on the type of trigger and how your instance is set up (self-hosted vs cloud).

✅ Common Reasons Why Your n8n Workflow Isn't Triggering Automatically

1. Workflow Is Not Active

Problem: The workflow is saved but not activated.
Fix: Open the workflow and click "Activate" (top right corner).

2. Trigger Node Misconfigured

Problem: The trigger node (like Webhook, Cron, or App-based trigger) might be set up incorrectly.
Fix:
- For Webhook: Make sure you're calling the correct URL (use the production one when activated).
- For Cron: Double-check the schedule and whether the server time matches your expectation.
- For third-party triggers (like Gmail, Trello): Ensure proper credentials and permissions are set.

3. n8n Instance Not Running in Background (Self-Hosted)

Problem: If you’re using self-hosted n8n, it might only be running in manual mode or temporarily via CLI.
Fix: Ensure you’ve launched n8n as a background service (e.g., with Docker, PM2, systemd, etc.).

4. Workflow Set to Manual Execution Mode

Problem: The workflow was triggered manually in development and wasn’t switched to production mode.
Fix: Make sure the workflow is activated and triggered from the proper entry point (especially for webhooks).

5. Missing or Invalid Credentials

Problem: If your trigger relies on APIs (e.g., Google, Slack), outdated or invalid credentials can silently fail.
Fix: Go to Credentials > verify or refresh tokens, API keys, etc.

6. No Incoming Data or Events

Problem: The service (e.g., Stripe, GitHub, Airtable) is not actually sending the trigger data.
Fix: Confirm from the source app that it is configured to call the webhook or send events.

7. Webhook URL Mismatch

Problem: Webhook URLs differ between test (manual execution) and production (active workflow).
Fix: Use the production webhook URL when the workflow is active.

8. n8n Queue Mode Not Processing

Problem: If you're running in queue mode, but workers aren't running, triggers might fail.
Fix: Ensure both main instance and workers are up and properly connected to Redis.

🧪 How to Debug

Open the workflow and check the Execution Log for any runs or errors.
Use manual execution to test and inspect inputs/outputs.
Check the n8n logs (console, Docker, or PM2 logs).
Use external tools like Webhook.site to check if your app is sending requests.