Actions20
- Payment Link Actions
- Form Actions
- Coupon Actions
Overview
This node integrates with the BCL Payment API to manage forms, payment links, and coupons. Specifically for the Form - Update Status operation, it allows users to activate or deactivate a form by updating its status via the API.
Common scenarios where this node is beneficial include:
- Enabling or disabling a form dynamically based on business logic or workflow conditions.
- Automating form lifecycle management in marketing or sales funnels.
- Controlling form availability without manual intervention in the BCL dashboard.
Example use case:
- Automatically deactivate a form after a campaign ends.
- Reactivate a form when a new promotion starts.
Properties
| Name | Meaning |
|---|---|
| Form ID | The unique numeric identifier of the form to update. |
| Is Active | Boolean flag indicating whether the form should be active (true) or inactive (false). |
Output
The node outputs JSON data representing the response from the BCL API after attempting to update the form's status. This typically includes confirmation of the updated status and any relevant metadata about the form.
The output is an array of JSON objects, each corresponding to an input item processed. If an error occurs and "Continue On Fail" is enabled, the output will contain an error object with details such as error message, HTTP status code, timestamp, resource, and operation.
No binary data output is produced by this operation.
Dependencies
- Requires an API token credential for authenticating requests to the BCL Payment API.
- The base URL for API requests is
https://bcl.my/api. - The node uses HTTP PATCH method to update the form status endpoint
/forms/{formId}/status.
Troubleshooting
- Authentication failed: Indicates invalid or expired API token. Verify and update the API key credential.
- Validation error (422): Usually caused by missing or incorrect parameters. Ensure
Form IDis valid andIs Activeis provided. - Bad request (400): Request format or parameters are invalid. Double-check property values.
- Forbidden (403): Insufficient permissions to modify the form. Confirm API token has required access rights.
- Not found (404): The specified form does not exist. Verify the
Form ID. - Server error (5xx): Temporary issues on BCL server side; retry later or contact support.
If "Continue On Fail" is enabled, errors will be returned as part of the output JSON instead of stopping execution.
Links and References
- BCL Payment API Documentation (official API docs)
- n8n documentation on HTTP Request Node (for understanding underlying HTTP calls)