Billing Booth One icon

Billing Booth One

Interact with Billing Booth One API
Join our community

Actions476

Overview

This node interacts with the Billing Booth One API to update an Auto Collection Endpoint. It allows users to modify various properties of an endpoint such as its name, address, authentication mode, credentials, protocol, frequency, and supplier details. Additional optional fields can also be set, including private key, port, scheduling details, and file collection settings. This node is useful for automating the management of remote data collection endpoints in billing or data aggregation workflows.

Use Case Examples

  1. Updating an FTP endpoint's address and authentication details to ensure secure and timely data collection.
  2. Changing the frequency of data collection from hourly to daily and specifying the exact hour for the trigger.
  3. Modifying the supplier information and enabling or disabling the endpoint based on operational requirements.

Properties

Name Meaning
Id Unique identifier of the Auto Collection Endpoint to update.
Name The name of the endpoint.
Address The remote server address or IP of the endpoint.
Authentication Mode The authentication method used for the endpoint, either password or private key.
Username The username for authentication.
Password The password for authentication.
Protocol The protocol used to connect to the endpoint.
Frequency How often the endpoint is triggered to collect data.
Supplier Id Unique identifier of the associated supplier.
Additional Body Fields Optional additional fields to customize the endpoint update, such as enabling/disabling the endpoint, private key content, port, scheduling hour, supplier name, and various file collection settings.

Output

JSON

  • data - The response data from the Billing Booth One API after updating the Auto Collection Endpoint.

Dependencies

  • Billing Booth One API key credential

Troubleshooting

  • Ensure the provided endpoint Id exists and is correct to avoid 'No routing information found' errors.
  • Verify that all required fields (e.g., name, address, authentication details) are provided to prevent validation errors from the API.
  • Check that the API key credential is valid and has the necessary permissions to update endpoints.
  • If using private key authentication, ensure the private key content is correctly formatted and provided if required.
  • Handle network or API errors gracefully; the node supports continue-on-fail to allow workflow continuation despite errors.

Discussion