Actions20
- Payment Link Actions
- Form Actions
- Coupon Actions
Overview
This node integrates with the BCL Payment API to manage various resources including payment links, forms, and coupons. Specifically for the Form resource and the Update Facebook Pixel operation, it allows users to update the Facebook Pixel tracking settings of a form. This includes enabling or disabling Facebook Pixel tracking, setting the Facebook Pixel ID, enabling the Facebook Conversion API, and providing an API token for authentication.
This node is beneficial in scenarios where you want to programmatically control Facebook Pixel integration on your forms, such as enabling pixel tracking for marketing analytics or conversion tracking without manually updating the form settings in the BCL dashboard.
Practical example:
You have a marketing campaign running and want to enable Facebook Pixel tracking on a specific form to monitor conversions. Using this node, you can update the form’s Facebook Pixel settings dynamically based on campaign needs or automate the setup process for multiple forms.
Properties
| Name | Meaning |
|---|---|
| Form ID | The unique identifier of the form to update. |
| Facebook Pixel Settings | A collection of settings related to Facebook Pixel tracking: |
| - Enable Facebook Pixel | Boolean flag to enable or disable Facebook Pixel tracking. |
| - Facebook Pixel ID | The Facebook Pixel ID string used for tracking. |
| - Enable Facebook API | Boolean flag to enable or disable the Facebook Conversion API. |
| - Facebook API Token | The API token used to authenticate requests to the Facebook Conversion API (password type). |
Output
The node outputs JSON data representing the response from the BCL API after updating the Facebook Pixel settings of the specified form. The output structure corresponds directly to the API's response and typically includes confirmation of the updated settings or error details if the update failed.
No binary data output is produced by this operation.
Dependencies
- Requires an API token credential for authenticating with the BCL Payment API.
- The node makes HTTP requests to the BCL API endpoint at
https://bcl.my/api. - Proper configuration of the API token credential within n8n is necessary for successful execution.
Troubleshooting
- Authentication failed: If the API token is invalid or expired, the node will throw an authentication error. Ensure the API token credential is correct and has not expired.
- Validation errors: If required fields are missing or incorrectly formatted (e.g., invalid Form ID or Facebook Pixel ID), the API may return validation errors. Verify all required properties are correctly set.
- Permission issues: A "Forbidden" error indicates insufficient permissions to update the form. Check that the API token has the necessary rights.
- Not found: If the specified Form ID does not exist, a "Not found" error will be returned. Confirm the Form ID is valid.
- Server errors: Temporary server issues may cause 5xx errors. Retry later or contact BCL support if persistent.
If the node is configured to continue on failure, error details will be included in the output JSON for each failed item.
Links and References
- BCL Payment API Documentation (general reference for API endpoints and parameters)
- Facebook Pixel Setup Guide (for understanding Facebook Pixel usage)
- Facebook Conversion API Documentation