Livo Trigger icon

Livo Trigger

Starts the workflow when Livo events occur (webhooks)
Join our community

Overview

This node acts as a webhook trigger for various events occurring in the Livo system. It listens for specific event notifications such as creation, update, payment, or deletion of orders, products, repairs, and customers. When one of these events happens, the node triggers the workflow with the event data.

Common scenarios where this node is useful include:

  • Automating order processing when a new order is created or updated.
  • Syncing product inventory or details when products are added, updated, or deleted.
  • Managing repair workflows by triggering actions on repair creation, updates, payments, or delivery.
  • Keeping customer records up to date by reacting to customer creation, updates, or deletions.

For example, you could use this node to automatically send an email notification when a new order is created or to update your CRM system whenever a customer's information changes.

Properties

Name Meaning
Event The specific Livo event to listen for. Options include:
- Tạo đơn hàng (New order created)
- Cập nhật đơn hàng (Order updated)
- Thanh toán đơn hàng (Order paid)
- Tạo sản phẩm (Product created)
- Cập nhật sản phẩm (Product updated)
- Xoá sản phẩm (Product deleted)
- Tạo phiếu sửa chữa (Repair created)
- Cập nhật phiếu sửa chữa (Repair updated)
- Thanh toán phiếu sửa chữa (Repair paid)
- Giao trả phiếu sửa chữa (Repair delivered)
- Tạo khách hàng (Customer created)
- Cập nhật khách hàng (Customer updated)
- Xoá khách hàng (Customer deleted)
Additional Options Collection of optional settings:
• Include Raw Data: Whether to include the raw webhook payload in the output (boolean).
• Webhook Secret: Optional secret string used to verify webhook authenticity.

Output

The node outputs JSON data representing the event received from Livo. The structure includes:

  • event: The event type string (e.g., "order.created").
  • resource: The resource category ("orders", "products", "repairs", or "customers") inferred from the event.
  • timestamp: Timestamp of the event, either from the payload or current time if missing.
  • event_id: Unique identifier of the event.
  • Other event-specific data fields under data merged into the output.
  • Optionally, if enabled, the full raw webhook data under raw_data.

The output is structured as a single item in the main output stream, suitable for further processing in the workflow.

Dependencies

  • Requires a publicly accessible webhook endpoint configured in n8n to receive POST requests from Livo.
  • If webhook verification is enabled, the user must provide the correct webhook secret matching the signature sent by Livo.
  • No external API calls are made by this node; it purely processes incoming webhook data.

Troubleshooting

  • Invalid webhook data received: This error occurs if the webhook payload is missing or not an object. Ensure that Livo sends valid JSON data.
  • Webhook signature verification failed: Happens when the provided webhook secret does not match the signature header in the request. Verify that the secret configured in the node matches the one set in Livo's webhook settings.
  • No workflow trigger despite events: Check that the selected event in the node matches the actual event type sent by Livo. The node filters events strictly by type.
  • Make sure the webhook URL is correctly registered in Livo and publicly reachable by their servers.

Links and References

Discussion