SerB2B icon

SerB2B

Interact with SerB2B API

Customer → Update

AI-generated

Overview

This node updates an existing customer in the SerB2B system. It is useful for scenarios where you need to modify customer details such as company name, phone number, address, tax information, and status flags like active or approved. For example, you can update a customer's phone number or mark them as active/inactive.

Use Case Examples

  1. Updating a customer's phone number and address after receiving new contact information.
  2. Changing the status of a customer to 'approved' after verification.

Properties

Name Meaning
Customer ID The unique identifier of the customer to update.
Additional Fields Optional fields to update for the customer, including company, phone, mobile, address, city, country, tax number, tax office, is active status, and is approved status.

Output

JSON

  • id - Unique identifier of the updated customer.
  • mail - Email address of the customer.
  • yetkili - Name of the authorized person or contact for the customer.
  • company - Company name of the customer.
  • phone - Phone number of the customer.
  • mobile - Mobile number of the customer.
  • address - Address of the customer.
  • city - City of the customer.
  • country - Country of the customer.
  • tax_number - Tax number of the customer.
  • tax_office - Tax office of the customer.
  • is_active - Boolean indicating if the customer is active.
  • is_approved - Boolean indicating if the customer is approved.

Dependencies

  • SerB2B API key credential

Troubleshooting

  • Ensure the Customer ID provided exists in the SerB2B system; otherwise, the update will fail with a not found error.
  • Verify that the API key credential is valid and has permissions to update customer data.
  • If the update payload contains invalid or unsupported fields, the API may return an error; ensure fields conform to expected types and values.

Links

  • SerB2B API Documentation - Official API documentation for SerB2B, useful for understanding the customer update endpoint and payload structure.

Discussion