BCL icon

BCL

Consume BCL Payment API

Overview

This node integrates with the BCL Payment API to manage forms, payment links, and coupons. Specifically for the Form resource and the Update Homepage Display operation, it allows users to update whether a particular form is shown on the homepage of the associated platform.

Typical use cases include:

  • Dynamically controlling the visibility of forms on a website's homepage without manual intervention.
  • Automating marketing or promotional campaigns by toggling featured forms.
  • Managing multiple forms and selectively displaying them based on business logic or user interaction.

For example, a user can set a form to be visible on the homepage during a special promotion period and hide it afterward using this node in an automated workflow.

Properties

Name Meaning
Form ID The unique identifier of the form to update. Must be provided.
Show On Homepage Boolean flag indicating whether the form should be displayed on the homepage (true to show, false to hide).

Output

The node outputs JSON data representing the response from the BCL API after updating the form's homepage display setting. This typically includes confirmation of the update and the current state of the form's homepage visibility.

The output structure is an array of JSON objects corresponding to each input item processed, containing the updated form data as returned by the API.

No binary data output is involved in this operation.

Dependencies

  • Requires an active connection to the BCL Payment API.
  • Needs an API authentication token credential configured in n8n to authorize requests.
  • The base URL for API requests is https://bcl.my/api.

Troubleshooting

Common Issues

  • Authentication failures: If the API token is invalid or expired, the node will return an authentication error.
  • Invalid Form ID: Providing a non-existent or incorrect form ID will result in a "Not found" error.
  • Missing required parameters: Omitting the Form ID or the Show On Homepage flag will cause validation errors.
  • API rate limits or server errors: Temporary issues with the BCL API may cause 5xx errors.

Error Messages and Resolutions

  • Authentication failed: Check that the API token credential is correctly configured and has not expired.
  • Validation error: Ensure all required fields are provided and formatted correctly.
  • Bad request: Verify that the parameters sent match expected types and constraints.
  • Forbidden: Confirm that the API token has sufficient permissions to update forms.
  • Not found: Double-check the Form ID exists in the BCL system.
  • Server error: Retry after some time; if persistent, contact BCL support.

Links and References

Discussion