Actions40
- Bookings Actions
- Customers Actions
- Agents Actions
- Services Actions
- Payments Actions
- Orders Actions
- Coupons Actions
- Locations Actions
- Availability Actions
- System Info Actions
- Test Actions
Overview
This node integrates with the LatePoint REST API to manage payments within a booking system. Specifically, the Payments - Create operation allows users to create new payment records associated with bookings and customers. This is useful in scenarios where you want to record payment transactions such as cash, credit card, PayPal, or bank transfers linked to specific bookings.
Practical examples include:
- Recording a payment made by a customer for a booking.
- Logging different payment methods and statuses (e.g., pending, completed, refunded).
- Adding transaction IDs from external payment processors for reconciliation.
Properties
| Name | Meaning |
|---|---|
| Booking ID | The unique identifier of the booking associated with this payment. |
| Customer ID | The unique identifier of the customer making the payment. |
| Amount | The amount of the payment. |
| Payment Method | The method used for the payment. Options: Cash, Credit Card, PayPal, Stripe, Bank Transfer. |
| Payment Status | The status of the payment. Options: Pending, Completed, Failed, Refunded. |
| Transaction ID | External transaction ID from the payment processor (optional). |
| Notes | Additional notes related to the payment (optional). |
| Description | A description or prompt to provide context/purpose for the API call (optional). |
| Send Body | Whether to send a custom JSON body or form data instead of individual fields (boolean). |
| Body Content Type | Format of the body content when sending a custom body: JSON or Form Data. |
| JSON Body | Custom JSON object to send as the request body if Send Body is true and content type is JSON. |
| Form Data | Custom form data parameters to send if Send Body is true and content type is Form Data. |
| Additional Fields | Additional optional fields to include when creating the payment record. |
Output
The node outputs the response from the LatePoint API after creating the payment. The output is a JSON object representing the newly created payment record, including all relevant details such as payment ID, amount, status, associated booking and customer IDs, transaction ID, and any notes.
If multiple payments are created (not typical for single create), it would output an array of such objects.
No binary data output is involved.
Dependencies
- Requires an API key credential for authenticating with the LatePoint REST API.
- The base URL and API key must be configured in the node credentials.
- The node sends HTTP requests to the LatePoint API endpoints.
Troubleshooting
- Invalid JSON in body: If using the custom JSON body option, ensure the JSON syntax is correct. Errors will indicate invalid JSON.
- Missing credentials: The node throws an error if no API credentials are configured.
- API errors: Any errors returned by the LatePoint API (e.g., invalid booking ID, missing required fields) will be surfaced in the node output.
- Incorrect field values: Ensure that IDs (booking, customer) exist and amounts are valid numbers.
- Unsupported payment method or status: Use only the supported options listed in the properties.