Actions108
- AI Actions
- Transcribe
- Detect Brand
- Extract Contact Information
- Mood Detection
- Detect Adult Content
- Enitity Detection
- Language Detection
- Too Long To Read
- Check Content Policy
- Detect Faces
- Generate Python Code
- Picture Text Recognition
- Detect Color
- Generate Image
- PDF OCR
- Translation
- Detect Email Type
- Generate Javascript Code
- Picture Object Recognition
- Business Actions
- Calculate Actions
- Code Actions
- Convert Actions
- Crypto Actions
- Date & Time Actions
- Generate Actions
- Image Actions
- Operator Actions
- PDF Actions
- Storage Actions
- Text Actions
- User Actions
Overview
The node provides a variety of no-code utility functions grouped by resource and operation categories. Specifically, for the Operator resource with the Split Name operation, it takes a full name string as input and splits it into components such as first name, last name, etc. This is useful in scenarios where you need to parse and extract parts of a person's name from a single string for further processing or data normalization.
Practical examples include:
- Splitting a full name field from a form submission into first and last names.
- Preparing user data for personalized communications by extracting name components.
- Data cleaning workflows where names need to be standardized.
Properties
| Name | Meaning |
|---|---|
| Code Variables | A collection of code variables defined in the code editor for the selected function. Each variable has: - Variable Name or ID: Selectable from a list or specified via expression. - Value: The value assigned to the variable. |
| Name to Split | The full name string that you want to split into components (e.g., "John Doe"). This is a required string input for the Split Name operation under the Operator resource. |
Output
The output is a JSON array where each item corresponds to an input item processed. For the Split Name operation, the output JSON will contain the parsed components of the input name string, typically including fields like first name, last name, middle name, etc., depending on the splitting logic implemented by the underlying service.
If the node supports binary data output for other operations, it would represent files or images accordingly, but for Split Name, the output is purely JSON text data representing the name parts.
Dependencies
- Requires an API key credential for authentication to the external "0CodeKit" service.
- The node makes HTTP POST requests to the endpoint corresponding to
operator/splitnamewith the input parameters. - No additional environment variables are explicitly required beyond the API key credential.
Troubleshooting
Common Issues:
- Invalid or empty "Name to Split" input may cause errors or empty outputs.
- Missing or invalid API key credential will result in authentication failures.
- Network connectivity issues can prevent the node from reaching the external service.
Error Messages:
- Authentication errors indicate problems with the provided API key; verify and update credentials.
- Input validation errors suggest required properties are missing or malformed; ensure "Name to Split" is provided as a non-empty string.
- JSON parsing errors in advanced switch operations (not relevant here) indicate malformed JSON inputs.
Resolution Tips:
- Double-check all required inputs before execution.
- Ensure the API key credential is correctly configured and active.
- Use expressions carefully when specifying variable names or IDs to avoid syntax errors.
Links and References
- n8n Expressions Documentation
- Official documentation or API reference for the external "0CodeKit" service (not publicly linked here).