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 resource and the Update Content operation, it allows users to update the custom HTML content of a form by specifying the form ID and new content. This is useful when you want to dynamically change the appearance or information presented in a form without manually editing it on the BCL platform.
Practical examples include:
- Updating promotional messages or banners within a form.
- Changing form instructions or descriptions based on campaign needs.
- Embedding custom HTML elements like videos or images into the form content.
Properties
| Name | Meaning |
|---|---|
| Form ID | The unique numeric identifier of the form to update. Required to specify which form's content will be changed. |
| Content | Custom HTML content to set for the form. This is the actual markup that will replace the existing form content. |
Output
The node outputs JSON data representing the response from the BCL API after updating the form content. This typically includes confirmation details about the updated form, such as its ID and the new content state.
No binary data output is produced by this operation.
Dependencies
- Requires an API token credential for authenticating requests to the BCL Payment API.
- The node makes HTTP requests to the base URL
https://bcl.my/api. - Proper configuration of the API token credential in n8n is necessary for successful execution.
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 configured and active.
- Validation error: Occurs if required parameters are missing or malformed (e.g., empty content or invalid form ID). Verify all required fields are provided and valid.
- Not found: If the specified form ID does not exist, the node will report a "not found" error. Confirm the form ID is correct.
- Bad request: Improperly formatted requests or invalid parameter values can cause this error. Double-check the input data format.
- Server error: Temporary issues on the BCL server side may result in 5xx errors. Retry later or contact BCL support if persistent.
If the node is set to continue on fail, errors will be returned as JSON objects containing error details instead of stopping execution.
Links and References
- BCL Payment API Documentation (official API docs for reference)
- n8n HTTP Request Node documentation (for understanding underlying HTTP calls)