Scheduled Workflow Activity Manager - n8n Workflow

• Users needing strict operational hours for specific n8n workflow automation.
• n8n administrators or DevOps specialists managing internal n8n instance resource usage.
• Technical users looking for advanced n8n templates utilizing the internal API to control system operations.

Many crucial automations only need to run during standard business hours to efficiently handle incoming requests or monitor systems. Running them 24/7 can unnecessarily consume resources or clutter logs outside peak utilization times. This expert n8n workflow provides a robust solution for managing those operational windows. By leveraging the dedicated n8n node and the internal n8n API, this n8n template ensures that your critical business logic is only active when necessary. This precise, programmatic control over any target n8n workflow activity simplifies compliance requirements and optimizes the utilization of your self-hosted or cloud n8n instance. This n8n workflow utilizes two key Schedule n8n trigger points to manage the target lifecycle.

This automation utilizes two distinct, scheduled paths to control the target n8n workflow status:

1. Activation Path (Morning): The Activate at 08:00 daily Schedule n8n trigger fires every morning at the designated time (08:00). It sends its data stream to a Merge n8n node, which combines the trigger data with the target workflow ID defined in the Workflow ID Set n8n node. This merged data is then passed to the n8n Activate n8n node, which uses your n8n API credentials to call the internal API and set the targeted n8n workflow to active.

1. Deactivation Path (Evening): The Deactivate at 20:00 daily Schedule n8n trigger fires every evening at the designated time (20:00). Similar to the activation path, it merges with the target workflow ID. This stream then instructs the n8n Deactivate n8n node to use the API to set the targeted n8n workflow to inactive.

The use of the n8n node for API interaction ensures native, reliable control over other n8n templates within your instance.

1. Importing the n8n Workflow: Copy the provided JSON data and import it into your n8n instance by creating a new n8n workflow and selecting 'Import from JSON.'


2. API Key Setup: This automation requires access to the n8n API. If you haven't already, generate an API key within your n8n user settings.


3. Credential Configuration: Create a new n8n credential in your instance, providing the generated API key. Ensure this new credential is selected in both the n8n Activate and n8n Deactivate n8n node settings.


4. Target ID Configuration: Navigate to the Workflow ID Set n8n node. Update the default value (cGqPi5Uy2u1ShmoO in the example) with the actual ID of the n8n workflow you intend to control. This ID can be found in the URL when viewing the target workflow.


5. Schedule Adjustment: Review the Activate at 08:00 daily and Deactivate at 20:00 daily Schedule n8n trigger nodes. If your required operational hours are different from 08:00–20:00, adjust the Cron expressions accordingly.


6. Final Step: Activate this entire n8n workflow to begin scheduled management of your target automation.

Activate at 08:00 daily (Schedule Trigger n8n trigger): Initiates the activation sequence. Key configuration: Runs daily at 08:00 (0 8 ).
Deactivate at 20:00 daily (Schedule Trigger n8n trigger): Initiates the deactivation sequence. Key configuration: Runs daily at 20:00 (0 20 ).
Workflow ID (Set n8n node): Stores the critical workflowID of the target n8n workflow. This is where you configure the specific automation being managed.
Merge in Workflow ID for activation/deactivation (Merge n8n node): Combines the data output from the Schedule n8n trigger with the target workflowID defined in the Set n8n node, ensuring the subsequent API call targets the correct automation.
n8n Activate (n8n node): Performs the activation of the target n8n workflow using the configured n8n API credential. The operation is set to activate.
n8n Deactivate (n8n node): Performs the deactivation of the target n8n workflow using the configured n8n API credential. The operation is set to deactivate.