Actions5
Overview
The node interacts with the SCH API, specifically providing functionality to convert a lead into a customer. This operation is useful in scenarios where you manage sales or CRM workflows and want to automate the transition of a lead record into a customer record within the SCH system. For example, after qualifying a lead through marketing efforts, this node can be used to programmatically update the lead status and create a corresponding customer entry.
Properties
| Name | Meaning |
|---|---|
| Customer Details | JSON object containing details about the customer to be created when converting a lead. |
The "Customer Details" property expects a JSON object that includes all necessary information required by the SCH API to create or update the customer record during the conversion process.
Output
The node outputs data in JSON format representing the response from the SCH API after attempting to convert the lead to a customer. This typically includes confirmation of the conversion, details of the newly created customer, or error messages if the operation failed.
If the node supports binary data output (not indicated in the provided code), it would represent any files or attachments returned by the API, but based on the static analysis, only JSON output is expected.
Dependencies
- Requires an active connection to the SCH API.
- Needs an API authentication token or key configured in the node's credentials to authorize requests.
- The base URL for the SCH API must be set in the credentials configuration.
Troubleshooting
Common Issues:
- Invalid or incomplete customer details JSON may cause the API to reject the request.
- Missing or incorrect API credentials will result in authentication errors.
- Network connectivity issues can prevent the node from reaching the SCH API.
Error Messages:
- Authentication failures usually indicate invalid or missing API keys; verify credential setup.
- Validation errors from the API often point to malformed or incomplete customer details; ensure the JSON structure matches the API requirements.
- Timeout or network errors suggest connectivity problems; check internet access and API endpoint availability.
Links and References
- Refer to the official SCH API documentation for detailed information on the required customer details JSON structure and other available operations.
- Consult n8n documentation on how to configure API credentials and use JSON input properties effectively.