What is the primary function of the Cockpit node in n8n?
The Cockpit node is essential for starting workflows, acting primarily as a trigger based on specific external events or actions within the connected application. This facilitates seamless Integrations.
How does the Cockpit component initiate an n8n workflow?
It functions as a dedicated trigger, constantly monitoring the external application for defined events. Once the event occurs, the node captures the data and starts the subsequent chain of Integrations.
Can the Cockpit node be used in the middle of a workflow?
No, due to its nature as an event listener, the Cockpit node is specifically designed to be the initial trigger point, defining the start of complex Integrations, rather than an intermediate processing node.
What kind of data does the Cockpit node receive upon activation?
When activated by an external event, the trigger node captures the structured payload (data) related to that event, which is then passed as input to the next processing node.
Is configuration required before using the Cockpit trigger?
Yes, you must configure the specific event or webhook endpoint that the node should listen to, ensuring the workflow is correctly triggered for the desired Integrations.