Centralized Automation Manager API - n8n Workflow

• Automation Specialists: Who need programmatic control and orchestration over a large suite of n8n templates.


• Developers: Building external tools (like the referenced Raycast extension) or custom interfaces that interact with the n8n backend.


• DevOps Engineers: Requiring an API endpoint to check the status (active/inactive) of deployed n8n workflow instances.


• System Integrators: Who need a unified n8n trigger point to fire off various specialized n8n workflows dynamically.

Managing multiple complex n8n workflows can be challenging, especially when external systems need to interact with them programmatically. This specialized n8n workflow solves that orchestration challenge by providing a single, highly secure Webhook n8n trigger endpoint. This unique n8n template supports two key functions: 1) Executing any target n8n workflow dynamically via a POST request, and 2) Retrieving comprehensive status details about any workflow in the n8n instance via a GET request. Utilizing the native n8n API node, this n8n workflow ensures efficient and secure backend communication, making it an indispensable tool for anyone scaling their n8n automation infrastructure.

This automation begins with the Webhook n8n trigger, authenticated via header credentials, listening on the path workflow-manager. The subsequent logic branches based on the HTTP method used:

1. Workflow Execution (POST Request)

1. Mapping: The "Map webhook request to fields" n8n node extracts the target workflowId from the URL query parameters and the input body data, which will be passed to the target n8n workflow.


2. Execution: The powerful "Execute Workflow" n8n node is called, using the dynamically provided workflowId. It is configured to wait for the sub-workflow to complete, ensuring synchronous operation.


3. Response: If successful, the "return succes message" node responds with the output of the executed n8n workflow. If the execution fails, the flow handles the error via "return problem executing workflow."

2. Information Retrieval (GET Request)

1. Parameter Mapping: The "map parameters" n8n node extracts the mode, workflowId, and includedWorkflows query parameters.


2. ID Check: The "Does workflowId Exist" n8n node checks if a specific workflow ID was requested.

1. Output Formatting: All fetched data converges on the "full mode" If n8n node, which checks the mode parameter.

To deploy this centralized management n8n workflow, follow these steps:

1. Import: Copy the provided JSON and import it as a new n8n workflow in your instance.


2. Webhook Authentication: The "Webhook" n8n trigger requires Header Authentication. Create a new Header Auth credential in n8n, using Authorization as the Header Name and a strong Bearer YOURSECRETKEY as the Header Value.


3. n8n API Credentials: The API retrieval branches require access to your n8n instance API. Create an "n8n API" credential (usually requiring an API Key or user credentials depending on your instance setup) and attach it to all four n8n API nodes (Get specific workflowid, get all inactive workflows, get all active workflows, get all workflows).


4. Activate: Ensure the workflow is active. Note the Webhook URL (e.g., https://your.n8n.instance/webhook/workflow-manager).


5. Usage Example (POST): To execute a workflow with ID 123, send a POST request to .../workflow-manager?workflowId=123 with a JSON body.


6. Usage Example (GET): To get a summary of all active workflows, send a GET request to .../workflow-manager?includedWorkflows=active.

Webhook (n8n trigger): The entry point of the n8n workflow, configured for Header Authentication and supports both GET and POST requests on the /workflow-manager path.
Map webhook request to fields (Set n8n node): Essential for the execution path. It maps the query workflowId and the POST request body (workflowInputData) into accessible variables for the next n8n node.
Execute Workflow (n8n node): The core of the orchestration logic. Dynamically targets another n8n workflow using an expression and waits for its execution to complete. This is critical for centralized command.
n8n (API n8n node): Used across all GET branches to interact with the n8n instance's internal API. Operations include get specific workflows and filtering lists based on the activeWorkflows status parameter, allowing management of n8n templates.
Does workflowId Exist (If n8n node): Determines whether the incoming GET request is for a single workflow or a filtered list of n8n workflows.
Included Workflows (Switch n8n node): Routes the list-fetching request based on the includedWorkflows query parameter (active, inactive, or all), ensuring the correct n8n API call is made.

• Map key workflow info (Set n8n node): Used in the 'summary' mode to pare down the extensive n8n API response, providing only key metadata (name, ID, status) for a cleaner, faster response.