What is the primary function of the Beex Trigger node in n8n?
The Beex Trigger node is specifically designed to act as the starting point for a workflow. It listens for defined events or data changes within the Beex platform, effectively initiating the automated Integrations.
How does the Beex Trigger initiate an n8n workflow?
The trigger initiates the workflow by receiving a webhook or by periodically polling the Beex API for updates. This ensures that the workflow starts instantly when the specified event occurs, providing the payload to subsequent nodes.
Is the Beex Trigger considered a standard node or a special type of component?
It is a specialized starting node. While all components are referred to as nodes, the Beex Trigger is unique because it must be the first node in the chain to handle incoming Integrations data.
What types of events can I monitor using this trigger?
You can monitor crucial Beex events such as the creation of new records, status updates, or modifications to existing data. The trigger captures this event and passes the data to the rest of your automation nodes.
Do I need special credentials to use the Beex Trigger for Integrations?
Yes. To enable seamless communication and security, you must configure your Beex API key or appropriate authentication method (like OAuth 2.0) within n8n before deploying the trigger node.