n8n and activate n8n
Configured with N8N. Review the connections and setup before adapting this template.
Node categories in this workflow
- Integration
- Routing
- Trigger
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| n8n | Integration | N8N | See node parameters |
| TAG? Auto start | Routing | If | See node parameters |
| n8n1 | Integration | N8N | activate |
| When clicking ‘Test workflow’ | Trigger | Manual Trigger | See node parameters |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
n8nApi
Workflow notes
Auto Starter
Auto Starter
On importing workflows these will not be auto started, even if the old version was running. To fix this we created this workflow that can be run after n8n starts. It fits in our auto deploy pipeline and modified n8n container that will import workflows, start n8n and start the tagged workflows.
- Start this workflow after n8n starts.
- It will get all workflows in the running n8n instance.
- If the files have a tag 'Auto start' the workflow will be started.
Configuration
- You need a a n8n api key configured.
n8n and activate n8n
n8n and activate n8n
Purpose and structure
This folder contains the n8n and activate n8n workflow. Its executable nodes use if, manualTrigger, n8n. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
When clicking ‘Test workflow’
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Manual/0928_Manual_N8N_Automate_Triggered.json MIT; preserve source notices.