SocialHub icon

SocialHub

SocialHub System API Integration Node

Overview

This node integrates with the SocialHub system API to manage customer information, specifically allowing the creation of new customer records. It is useful in scenarios where businesses need to programmatically add customer details such as name, gender, contact information, source, and organizational affiliation into their customer management system. For example, it can be used to automate customer onboarding from e-commerce platforms like Shopify.

Use Case Examples

  1. Automatically create a new customer record when a user registers on an online store.
  2. Batch import customer data from a CRM system into the SocialHub customer management system.

Properties

Name Meaning
Customer Name The full name of the customer to be created.
Gender The gender of the customer, with options Unknown, Male, or Female.
Mobile Phone The customer's mobile phone number, required for contact.
Phone Prefix Code The international prefix code for the customer's phone number.
Email The customer's email address, optional.
Customer Source The source code indicating where the customer originated from, e.g., Shopify.
Birthday The customer's birthday in yyyy-MM-dd format, optional.
Customer Identity Type The type of customer identity, such as Member, Registered User, Guest, or Employee.
Organization Code The code of the organization the customer belongs to.

Output

JSON

  • data - The response data from the SocialHub API after creating the customer, typically including the created customer details or confirmation.

Dependencies

  • Requires an API key credential for SocialHub API authentication.

Troubleshooting

  • Ensure all required fields (Customer Name, Mobile Phone, Phone Prefix Code, Customer Source, Organization Code) are provided to avoid validation errors.
  • Check that the API credentials for SocialHub are correctly configured and have the necessary permissions.
  • If the API returns errors related to data format, verify that the birthday is in the correct yyyy-MM-dd format and other fields conform to expected types.

Links

Discussion