Mpro5 Trigger icon

Mpro5 Trigger

Starts the workflow when mpro5 events occur
Join our community

Overview

The Mpro5 Trigger node is designed to start an n8n workflow when specific events occur in the Mpro5 platform. It acts as a polling trigger, periodically checking for new events such as completed flows, created follow-up actions, IoT sensor alerts, or completed jobs. This node is useful for automating processes that need to react to changes or updates within the Mpro5 system.

Common scenarios:

  • Automatically process data when a flow or job is completed in Mpro5.
  • Initiate follow-up tasks when a new action is created.
  • Respond to IoT sensor alerts in real time by triggering workflows.

Practical examples:

  • When a "Job Being Completed" event occurs, automatically send a notification or update another system.
  • On receiving an "Iot Sensor Alert Being Raised," log the alert details and notify relevant personnel.

Properties

Name Meaning
Event The type of Mpro5 event to trigger the workflow on. Options:
- Flow Being Completed
- Follow Up Action Being Created
- Iot Sensor Alert Being Raised
- Job Being Completed

Output

The output is a JSON array where each item represents a detected event since the last poll. The structure of each item depends on the selected event:

  • For Flow Being Completed: Each object contains at least AuditID.
  • For Job Being Completed: Each object contains at least JobID.
  • For Iot Sensor Alert Being Raised: Each object contains at least AlertID.
  • For Follow Up Action Being Created: Each object contains at least FollowUpActionID.

Example output (for "Job Being Completed"):

[
  {
    "JobID": "12345"
  }
]

No binary data is output by this node.

Dependencies

  • External Service: Requires access to the Mpro5 API.
  • Credentials: Needs valid mpro5CredentialsApi credentials configured in n8n.
  • Dependencies: Uses the moment library for date handling.

Troubleshooting

Common issues:

  • Invalid Credentials: If the provided Mpro5 credentials are incorrect or missing, the node will fail to connect to the API.
  • Unsupported Event: If an unsupported event is selected, the node throws an error:
    The defined event "<event>" is not supported
    • Resolution: Ensure you select one of the supported events from the dropdown.
  • API Errors: Any errors returned by the Mpro5 API will cause the node to throw an error with details from the API response.

Tips:

  • Make sure your n8n instance has network access to the Mpro5 API.
  • Check that the system clock is accurate, as the node uses timestamps to filter new events.

Links and References

Discussion