How to activate a workflow on n8n
Quick Answer
Activate n8n workflows by toggling the Active switch or clicking Publish in the Editor UI top-right; workflows run automatically on triggers once active. Verify triggers, credentials, and logs first; toggle OFF/ON to re-register webhooks. CLI and API methods available for advanced users.
Prerequisites
- n8n instance running continuously (self-hosted, Cloud, or desktop app)
- At least one valid trigger node (Webhook, Cron, Schedule - not Manual Trigger)
- Valid credentials for all nodes
- Workflow ID from URL (alphanumeric string at end)
- For n8n Cloud: Available active workflow slots
Step-by-Step Instructions
1
Open Workflow in Editor UI
Navigate to your n8n Editor and open the target workflow. The workflow ID is the alphanumeric string at the end of its URL, e.g., in
http://localhost:5678/workflow/109, ID is 109. Ensure it has at least one valid trigger node like Webhook or Schedule.2
Toggle Active Switch
In the top-right corner, find the Active/Inactive toggle (grey for inactive, green for active). Slide or click it to ON. For trigger changes like Webhooks, toggle OFF then ON to re-register production URLs.
New workflows are inactive by default; activation enables automatic execution on triggers.
3
Click Publish Button
Alternatively, click the Publish button in the top navigation bar. This transitions the workflow from draft to active status, making it run whenever triggers receive input or meet conditions.
4
Configure Workflow Settings
Click the Options menu, then Settings. Set Timezone for Schedule triggers, Error Workflow for failures, and toggle Save failed production executions. Use production Webhook URLs (not test).
HTTPS/SSL required for production Webhooks.
5
Verify Trigger Nodes
Confirm at least one trigger node exists (e.g., Webhook, Cron, Schedule). Workflows with only Manual Trigger cannot activate for production. Test manually first via Execute Workflow button.
6
Check Credentials
Validate all nodes have valid, non-expired credentials. Reconnect any invalid/revoked tokens. Check logs for errors like
Workflow is inactive or Webhook not registered. Cloud users: Ensure under active workflow limits.
7
Activate via CLI (Advanced)
n8n execute --id <ID> Find ID from URL; operates on database.
8
Activate via n8n API (Advanced)
Generate API key in Settings > n8n API. Use n8n node or HTTP Request to PATCH
/workflows/<ID> with { "active": true } and API key header. Test after upgrades as API may change. Not for trial users; check <code>/api/v1/docs</code>.
9
Test and Monitor Executions
After activation, switch to Executions tab to view runs. Test production Webhook URLs in browser. Ensure n8n runs continuously (Docker/PM2).
10
Restart if Needed
For persistent issues, restart n8n instance. Most problems resolve in under 10 minutes with this checklist.
Check server timezone for Cron/Schedule.
Common Issues & Troubleshooting
Workflow inactive by default or toggle stuck grey
Toggle Active switch top-right to ON (green). For Webhook changes, toggle OFF/ON to re-register. Check logs for <code>Workflow is inactive</code>.
Missing trigger nodes (only Manual Trigger)
Add valid trigger like Webhook, Cron, or Schedule. Manual Trigger blocks production activation.
Invalid/expired credentials or Webhook errors
Reconnect credentials; use production Webhook URL (not test). Ensure HTTPS/SSL and correct timezone.
n8n Cloud active workflow limit hit
Check plan slots; deactivate others or upgrade.
CLI/API changes not applying
Restart n8n instance after commands. Verify Workflow ID from URL.