Control when a chosen n8n workflow runs. It turns that workflow on at 08:00 and off at 20:00 every day so work happens in business hours. Ideal for teams that want daytime processing and quiet nights.

Two schedule triggers fire at set times. A Set node stores the target workflow ID, and Merge nodes attach this ID to each run. The n8n API nodes then activate or deactivate the target workflow using your API key. You keep the logic of the target workflow unchanged while managing its uptime window. This design focuses on orchestration rather than data, which keeps the setup small and reliable. Benefits include fewer after hours actions, less noise, and tighter control of when tasks run.

Setup needs your n8n API key and the workflow ID from its URL. Testing is simple by changing the cron to run in the next minute and watching the status flip. Expect fewer after hours sends and fewer surprises at night, plus no daily clicks to toggle status. Use it to pause marketing sends overnight, stop dev jobs outside support hours, or limit data syncs to office time. Note that trial plans do not support the n8n API, so this method will not work there.

• Daily 08:00 schedule trigger turns the target workflow on
• Daily 20:00 schedule trigger turns the target workflow off
• Set node stores the workflow ID in one place
• Merge nodes pass the ID into both activate and deactivate paths
• n8n API nodes call activate and deactivate using your credentials
• Custom cron expressions let you adjust hours and days

• Reduce manual work from 2 daily toggles to 0
• Eliminate 100% of after hours runs for the selected workflow
• Lower nightly server load for that workflow to near zero
• Cut status errors by removing manual steps
• Standardize business hours across teams without changing workflow logic

1. Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
2. You'll need accounts with n8n. See the Tools Required section above for links to create accounts with these services.
3. Create an n8n API key in your n8n instance. Open User Settings and go to the API section, then generate a key and copy it.
4. In the n8n credentials manager, create a new credential for the n8n API. Enter your n8n base URL and paste the API key, then save.
5. Open the Set node labeled Workflow ID and replace the value with the ID of the workflow you want to control. You can find it in the workflow URL.
6. Open both Schedule Trigger nodes. Keep 0 8 * * * and 0 20 * * * or change the cron expressions to match your business hours.
7. Open the n8n Activate and n8n Deactivate nodes and select the n8n API credential you just created. Confirm the base URL matches the instance that hosts the target workflow.
8. Run a quick test. Temporarily change one cron to run in the next minute, wait for execution, and confirm the target workflow status flips in the workflow list.
9. Switch the cron settings back to your desired times and save the workflow. Make sure the scheduler workflow is active.
10. Troubleshooting: 401 errors mean the API key or base URL is wrong. 404 means the workflow ID is not correct. Trial plans do not include API access, so calls will fail.
11. Check your server time zone so cron runs when you expect. Align the schedule with your business time zone.