Overview

This node integrates with the iBill.io API to update customer information. It allows users to specify a customer by their ID and update various fields such as name, email, tags, phone number, address details, tax information, discount details, GPS coordinates, and notification preferences. This node is useful in scenarios where customer data needs to be programmatically updated in the iBill.io system, such as syncing customer details from another CRM or updating customer preferences based on user interactions.

Use Case Examples

1. Updating a customer's email and phone number after receiving new contact information.
2. Modifying a customer's address and tax ID for billing purposes.
3. Enabling or disabling email notifications for a specific customer.

Properties

Output

JSON

• id - The unique identifier of the updated customer
• name - The updated name of the customer
• email - The updated email address of the customer
• tags - Updated tags associated with the customer
• phone_number - Updated phone number of the customer
• enabled - Updated enabled status of the customer
• address1 - Updated primary address line
• address2 - Updated secondary address line
• city - Updated city
• state - Updated state
• pocode - Updated postal code
• country - Updated country
• tax_id - Updated tax identification number
• ssn - Updated Social Security Number
• tax_rate - Updated tax rate
• discount_pct - Updated discount percentage
• discount_expires - Updated discount expiration date
• discount_description - Updated discount description
• gps_lat - Updated GPS latitude coordinate
• gps_long - Updated GPS longitude coordinate
• do_not_suspend - Updated suspension flag
• reseller_id - Updated reseller identifier
• email_notifications - Updated email notification preference

Dependencies

• Requires iBill.io API credentials for authentication and access.

Troubleshooting

• Common issues include invalid or missing customer ID, which will cause the update operation to fail.
• Incorrect or incomplete API credentials can lead to authentication errors.
• If no fields to update are provided, the operation may return an error or no changes will be made.
• Error messages typically indicate missing required parameters or API connectivity issues; ensure all required fields are correctly set and the API is reachable.