Actions20
- Payment Link Actions
- Form Actions
- Coupon Actions
Overview
This node integrates with the BCL Payment API to manage various resources such as payment links, forms, and coupons. Specifically for the Form - Get operation, it retrieves detailed information about a specific form by its ID. This is useful when you want to fetch the current configuration or details of a form within your workflow, for example, to display form data, verify settings, or use form metadata in subsequent automation steps.
Practical examples:
- Fetching a form's details to display or log them.
- Using form data to conditionally trigger other actions based on form properties.
- Integrating form information into reports or dashboards.
Properties
| Name | Meaning |
|---|---|
| Form ID | The unique numeric identifier of the form to retrieve. This is required to specify which form to get. |
Output
The node outputs the JSON response from the BCL API representing the requested form's details. The structure typically includes all form attributes such as title, slug, status, content, stock items, affiliate settings, redirect URLs, webhook settings, pixel tracking configurations, and more depending on the form's setup.
The output is an array of JSON objects (one per input item), each containing the full form data as returned by the API.
No binary data output is involved in this operation.
Dependencies
- Requires an API token credential for authenticating with the BCL Payment API.
- The node makes HTTP requests to
https://bcl.my/api. - Proper configuration of the API token credential in n8n is necessary.
Troubleshooting
- Authentication failed: If the API token is invalid or expired, the node will return an authentication error. Ensure the API token credential is correctly set and active.
- Not found error: If the specified Form ID does not exist, the node will report a "Not found" error. Verify that the Form ID is correct.
- Validation errors: Improper or missing parameters may cause validation errors. Make sure the Form ID is provided and valid.
- Server errors: Temporary issues on the BCL server side may result in 5xx errors. Retry after some time or check BCL service status.
If the node is configured to continue on failure, errors will be returned as JSON objects with error details instead of stopping execution.
Links and References
- BCL Payment API Documentation (official API docs, if publicly available)
- n8n documentation on HTTP Request node for understanding underlying request mechanics (conceptual)