Billing Booth One icon

Billing Booth One

Interact with Billing Booth One API

Actions476

Overview

This node interacts with the Billing Booth One API to update email settings for an organization. It supports updating various email configuration methods such as SMTP, Mailgun, and Microsoft 365 by sending the appropriate settings to the API. This node is useful for automating the management of email server configurations within an organization's billing system, enabling seamless updates to email delivery methods and credentials.

Use Case Examples

  1. Updating SMTP settings for an organization's email server by providing server address, port, username, and password.
  2. Switching the email sending method to Mailgun by updating the API keys and endpoint details.
  3. Configuring Microsoft 365 email settings with access and refresh tokens for secure authentication.

Properties

Name Meaning
Organisation Id Unique identifier of the organization whose email settings are being updated.
Method The email sending method to configure, such as SMTP, Mailgun, or Microsoft 365.
Additional Body Fields Optional additional fields for the email settings such as server address, username, password, port, security flag, access token, and refresh token.

Output

JSON

  • json - Response from the Billing Booth One API after updating the email settings, typically containing confirmation or updated configuration details.

Dependencies

  • Billing Booth One API with an API key credential for authentication.

Troubleshooting

  • Ensure the organisationId is valid and exists in the Billing Booth One system to avoid errors related to missing or invalid identifiers.
  • Verify that the selected method (smtp, mailgun, microsoft365) is supported and that all required fields for that method are provided to prevent incomplete configuration errors.
  • Check that the API key credential used for authentication is valid and has sufficient permissions to update email settings.
  • If the node throws errors related to missing binary data, ensure that the binary property name is correctly specified and the binary data exists on the input item.

Discussion