Actions20
- Call Actions
- Contact Actions
- Agent Actions
- Phone Number Actions
Overview
This node integrates with the ContactShip API to manage contacts and related entities. Specifically, the Contact - Create operation allows users to add new contacts into their ContactShip organization database. This is useful for automating contact management workflows such as CRM updates, lead capturing, or syncing contacts from other systems.
Typical use cases include:
- Automatically creating a new contact when a form is submitted.
- Importing contacts from external sources into ContactShip.
- Adding detailed contact information including custom properties for segmentation or personalization.
Properties
| Name | Meaning |
|---|---|
| Full Name | The full name of the contact to be created. |
| Phone Number | The contact's phone number in E.164 format (e.g., +12124567890). |
| Country | The country associated with the contact. |
| Optional email address of the contact. | |
| Description | Optional notes or description about the contact. |
| Additional Fields | A collection of extra data fields that can be added to the contact: |
| - Contact Properties | Predefined properties available in the organization; each has a property type and value. |
| - Custom Properties | User-defined additional data fields with types like Text, URL, Location, Number, Calendar, Select. |
Output
The output JSON contains the response data returned by the ContactShip API after creating the contact. This typically includes the newly created contact's details such as its unique ID, full name, phone number, country, email, description, and any additional data stored.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the ContactShip API.
- The node uses the ContactShip REST API endpoints to perform operations.
- Proper configuration of the API base URL and API key is necessary in the node credentials.
Troubleshooting
- Invalid phone number format error: The node validates phone numbers to ensure they follow the E.164 format (e.g., +12124567890). If you receive an error about invalid phone number format, verify that the phone number input matches this format exactly.
- API authentication errors: Ensure that the API key credential is correctly configured and has sufficient permissions.
- Parsing errors on additional properties: When adding predefined contact properties, the node attempts to parse JSON strings describing the property type and field. Malformed JSON here will cause errors; double-check the formatting of these inputs.
- Network or API errors: Check network connectivity and API service status if requests fail unexpectedly.
Links and References
- ContactShip API Documentation (Assumed URL for reference)
- E.164 Phone Number Format
- n8n Documentation on Creating Custom Nodes