MonOrdo TriggerInstall

Overview

The MonOrdo Trigger node is designed to start an n8n workflow when specific events occur in the MonOrdo system. It acts as a webhook trigger, listening for selected event types (such as account, profile, order, collect, parcel, prescription, vital, or mutuel events) and initiates the workflow upon receiving relevant notifications from MonOrdo.

Common scenarios:

• Automating downstream processes when a new account, order, or prescription is created in MonOrdo.
• Keeping external systems synchronized with updates or deletions of entities in MonOrdo.
• Notifying users or updating records in other applications when certain MonOrdo events happen.

Practical examples:

• When a new order is created (order.created), automatically send a notification email.
• When a prescription is updated (prescription.updated), update a connected CRM system.
• When a collect is confirmed (collect.confirmed), trigger a shipment process.

Properties

Available options include:

• account.created, account.updated, account.deleted
• profile.created, profile.updated, profile.deleted
• order.created, order.updated, order.deleted
• collect.created, collect.updated, collect.deleted, collect.confirmed, collect.rebuilt, collect.synchronized, collect.cancelled
• parcel.created, parceld.with_auto_collect, parcel.updated, parcel.deleted, parcel.cancelled
• prescription.created, prescription.updated, prescription.deleted
• vital.created, vital.updated, vital.deleted
• mutuel.created, mutuel.updated, mutuel.deleted

Output

The node outputs the JSON payload received from the MonOrdo webhook. The structure of this output depends on the event type and the data sent by MonOrdo, but it will always be a direct pass-through of the webhook's body.

Example output:

[
  {
    "json": {
      // All fields as received from MonOrdo webhook
      "event": "order.created",
      "data": {
        "orderId": "12345",
        "status": "created",
        // ...other fields
      }
    }
  }
]

• The json field contains all properties sent by MonOrdo for the triggered event.
• No binary data is produced by this node.

Dependencies

• External Service: Requires access to the MonOrdo API/webhook system.
• Credentials: Needs monOrdoCredentialsApi credentials configured in n8n, including:
  • API URL (url)
  • API Key (apiKey)
• n8n Configuration: The node must be accessible via a public URL if running outside of n8n Cloud, so MonOrdo can reach the webhook endpoint.

Troubleshooting

Common issues:

• Webhook not triggering: Ensure that your n8n instance is publicly accessible and the webhook URL is correctly registered with MonOrdo.
• Invalid credentials: If the API key or URL is incorrect, webhook creation or deletion may fail.
• Missing expected data: If the webhook creation response does not contain an ID, the node will throw an error indicating missing expected data.

Error messages and resolutions:

• "MonOrdo webhook creation response did not contain the expected data."
  • Check MonOrdo API response and ensure your credentials are correct.
• Errors during webhook creation/deletion (e.g., network errors, authentication failures)
  • Verify connectivity between n8n and MonOrdo, and double-check credentials.

Links and References

• n8n Documentation: Webhook Triggers
• [MonOrdo (if available): API/Webhook documentation] (Contact MonOrdo support or refer to their developer resources.)