What is the primary function of the One Simple API node?
The primary function of this node is to act as a webhook listener, enabling external systems to start your workflow. It serves as the initial trigger, processing incoming data for subsequent Integrations.
How do I configure this node to receive data?
You configure the One Simple API node by defining a unique endpoint path. When data is sent to this endpoint (usually via POST or GET requests), the node acts as the trigger, passing the payload to the rest of the workflow steps or Integrations.
Is the One Simple API a trigger or an action node?
This component is specifically designed as a trigger node. It waits passively for an incoming API call before activating the workflow and executing defined Integrations.
What kind of Integrations are best suited for the One Simple API node?
This node is ideal for Integrations where you need immediate, event-driven processing, such as receiving alerts from monitoring tools, accepting form submissions, or acting as the trigger for a CI/CD pipeline.
Can I secure the data received by this trigger node?
Yes, n8n allows you to secure the API endpoint defined by this node using various authentication methods, ensuring that only authorized Integrations can trigger the workflow.