RV Rental Webhook icon

RV Rental Webhook

Webhook trigger for RV rental system events like reservation creation, confirmations, status changes, and customer actions.
Join our community

Overview

This node acts as a webhook trigger for an RV rental system, listening to various events related to reservations, payments, and document signing. It is designed to capture real-time updates such as when a reservation is created, confirmed, cancelled, or its status changes, as well as when payments are completed or rental agreements are signed.

Common scenarios where this node is beneficial include:

  • Automating workflows that respond immediately to new or updated reservations.
  • Sending notifications or updating external systems when payment is completed.
  • Triggering document management processes once rental agreements are signed.
  • Filtering specific event types to reduce unnecessary workflow executions.

For example, a user could set up this node to trigger only on "Reservation Created" events to automatically send a welcome email to customers or update availability calendars.

Properties

Name Meaning
Event Filter Select which RV rental event(s) should trigger the webhook. Options include: All Events, Reservation Created, Reservation Confirmed, Reservation Status Changed, Reservation Cancelled, Payment Completed, Document Signed.
Response Choose when to return the HTTP response to the webhook call: Immediately with received data, or after the last node in the workflow finishes processing.
Options Additional settings:
• Raw Body: Return the raw request body instead of parsed data.
• No Response Body: Send no body in the HTTP response (only status).

Output

The node outputs JSON data structured around the event received:

  • event: The event type string (e.g., "reservation.created").
  • timestamp: Timestamp of the event or current time if not provided.
  • source: Source identifier, defaulting to "rv-rental-system".
  • headers: HTTP headers from the webhook request.
  • query: Query parameters from the webhook URL.
  • data: The main payload associated with the event.

For reservation-related events ("reservation.created", "reservation.confirmed", "reservation.status_changed"), the output includes a detailed reservation object with fields such as:

  • id, reference number, status, source
  • start and end dates
  • total amount
  • customer details
  • listing information
  • delivery info
  • trip notes
  • pricing details
  • selected add-ons
  • external reservation ID
  • links to documents and signwell document IDs
  • creation and update timestamps

For "reservation.status_changed" events, it also includes old_status and new_status.

If the "Raw Body" option is enabled, the raw request body is included under rawBody.

The node can also control the HTTP response sent back to the webhook caller based on the "Response" and "No Response Body" options.

Dependencies

  • Requires an HTTP POST webhook endpoint exposed by n8n.
  • No external API keys or services are required directly by this node.
  • The node depends on receiving properly formatted webhook calls from the RV rental system.

Troubleshooting

  • Event filter mismatch: If the node does not trigger, verify that the incoming event matches the selected "Event Filter". Selecting "All Events" ensures all events trigger the node.
  • Malformed webhook payloads: The node expects certain fields like event and data. Missing or malformed payloads may cause incomplete output.
  • Response timing issues: Choosing "When Last Node Finishes" delays the HTTP response until workflow completion; ensure downstream nodes do not timeout.
  • No response body: Enabling "No Response Body" sends empty responses; some webhook providers may require a response body to confirm receipt.
  • Raw Body option: Use this only if you need the unparsed request body; otherwise, the node returns parsed JSON data.

Links and References

Discussion