Overview
The Moleculer Trigger node is designed to listen for and trigger workflows based on Moleculer microservices actions or events. It is useful in scenarios where you want to automate processes in response to specific actions or events occurring within a Moleculer-based system, such as triggering a workflow when a particular service action is called or an event is emitted.
Use Case Examples
- Trigger a workflow when a user registration action is completed in a Moleculer service.
- Start a process when a specific event, like 'order.created', is emitted by a Moleculer service.
Output
JSON
operation- The type of operation triggered (action or event).eventName- The name of the event triggered (if operation is event).actionName- The name of the action triggered (if operation is action).payload- The data payload received from the triggered action or event.
Dependencies
- Requires a Moleculer API credential for authentication to connect to the Moleculer microservices.
Troubleshooting
- Ensure the Moleculer API credential is correctly configured and has the necessary permissions to listen to actions or events.
- Verify that the specified action or event names exist and are correctly spelled in the Moleculer services.
- Check network connectivity to the Moleculer broker or service registry to ensure the trigger can receive events or actions.
Links
- Moleculer Framework Documentation - Official documentation for the Moleculer microservices framework, useful for understanding actions and events.