mirror of
https://github.com/n8n-io/n8n.git
synced 2024-11-14 00:24:07 -08:00
26 lines
1.2 KiB
Markdown
26 lines
1.2 KiB
Markdown
# Key Components
|
|
|
|
|
|
## Connection
|
|
|
|
A connection establishes a link between nodes to route data through the workflow. Each node can have one or multiple connections.
|
|
|
|
|
|
## Node
|
|
|
|
A node is an entry point for retrieving data, a function to process data or an exit for sending data. The data process includes filtering, recomposing and changing data. There can be one or several nodes for your API, service or app. You can easily connect multiple nodes, which allows you to create simple and complex workflows with them intuitively.
|
|
|
|
For example, consider a Google Sheets node. It can be used to retrieve or write data to a Google Sheet.
|
|
|
|
|
|
## Trigger Node
|
|
|
|
A trigger node is a node that starts a workflow and supplies the initial data. What triggers it, depends on the node. It could be the time, a webhook call or an event from an external service.
|
|
|
|
For example, consider a Trello trigger node. When a Trello Board gets updated, it will trigger a workflow to start using the data from the updated board.
|
|
|
|
|
|
## Workflow
|
|
|
|
A workflow is a canvas on which you can place and connect nodes. A workflow can be started manually or by trigger nodes. A workflow run ends when all active and connected nodes have processed their data.
|