ContactShipInstall

Overview

This node integrates with the ContactShip API to manage contacts and their associated data, including tags. Specifically, the "Remove Tag from Contact" operation allows users to remove a tag from a specified contact by providing the contact identifier and the tag ID. This is useful in scenarios where you want to dynamically update or clean up contact metadata, such as removing outdated or irrelevant tags from contacts in your CRM or marketing system.

Practical examples:

• Removing a promotional tag from a contact after a campaign ends.
• Cleaning up tags that no longer apply to a contact based on updated customer status.
• Automating tag management workflows to keep contact data organized.

Properties

Output

The output JSON contains the response from the ContactShip API after attempting to remove the tag from the contact. Typically, this will be an object indicating success or failure of the removal operation. For example, it may include confirmation fields or status messages returned by the API.

No binary data output is involved in this operation.

Example output structure (simplified):

{
  "success": true
}

or an error message if the operation fails.

Dependencies

• Requires an API key credential for authenticating with the ContactShip API.
• The node uses the ContactShip API base URL and API key configured in the credentials.
• The "Tag ID" options are dynamically loaded from the ContactShip API's tags endpoint.
• Proper phone number formatting (E.164) is validated for related operations but not directly relevant here.

Troubleshooting

• Invalid Contact Identifier: If the contact ID, phone number, or email provided does not exist or is incorrect, the API will return an error. Verify the contact identifier is correct.
• Invalid Tag ID: If the tag ID does not exist or is not associated with the organization, the removal will fail. Ensure the tag ID is valid and belongs to your account.
• API Authentication Errors: Missing or invalid API key credentials will cause authentication failures. Confirm that the API key is correctly set up in n8n credentials.
• Network or API Errors: Temporary network issues or API downtime can cause request failures. Retry or check the ContactShip service status.
• Permission Issues: The API key used must have sufficient permissions to modify contact tags.

Common error messages:

• "Invalid phone number format" — Not applicable directly here but relevant for other contact operations.
• "Contact not found" — Check the contact identifier.
• "Tag not found" or "Cannot remove tag" — Verify the tag ID.
• "Unauthorized" — Check API key credentials.

Links and References

• ContactShip API Documentation (hypothetical link as actual URL not provided)
• E.164 Phone Number Format
• n8n Documentation on Creating Custom Nodes

If you need details on other operations or resources, feel free to ask!