ContactShip icon

ContactShip

Interact with ContactShip API for AI Phone Calls
Join our community

Actions20

Overview

This node interacts with the ContactShip API to manage contacts and their organization within boards. Specifically, the "Move Contact in Board" operation allows users to move a contact's card from one stage to another within a specified board, adjusting its position/order in the new stage.

Common scenarios where this node is beneficial include:

  • Managing sales pipelines or customer journey stages by moving contacts between different stages on a board.
  • Automating workflow progressions for contacts based on external triggers or conditions.
  • Organizing contacts visually in project management or CRM boards.

For example, if a contact has completed an initial qualification stage, you can use this node to move their card to the "Negotiation" stage on the sales board, optionally specifying the card's order in that stage.

Properties

Name Meaning
Board The board where the contact's card currently exists. Options are dynamically loaded boards.
Card ID The unique identifier of the card representing the contact to be moved.
New Stage The target stage within the board where the contact will be moved. Options depend on the selected board.
Order The position index of the card within the new stage (0 means the first position).

Output

The output JSON contains the response data from the ContactShip API after moving the contact card. This typically includes details about the updated card such as its new stage, order, and other metadata returned by the API.

No binary data is output by this operation.

Example output structure (simplified):

{
  "id": "card-id",
  "stage_id": "new-stage-id",
  "order": "0",
  "entity_id": "contact-id",
  "entity_type": "CONTACT",
  ...
}

Dependencies

  • Requires an API key credential for authenticating with the ContactShip API.
  • The node depends on the ContactShip API endpoints for boards, stages, and cards.
  • The board and stage options are dynamically loaded via API calls.
  • Proper configuration of the API base URL and API key in n8n credentials is necessary.

Troubleshooting

  • Invalid Card ID or Board ID: If the card or board ID is incorrect or does not exist, the API will return an error. Verify IDs are correct and correspond to existing entities.
  • Stage Not Found: Selecting a stage that does not belong to the specified board will cause failure. Ensure the stage belongs to the chosen board.
  • API Authentication Errors: If the API key is invalid or missing, requests will fail. Confirm the API key credential is correctly set up.
  • Order Value Issues: The order should be a string representing a numeric position; invalid values may cause unexpected placement or errors.
  • Network or API Downtime: Temporary network issues or ContactShip API downtime can cause request failures.

To resolve errors, check the error message returned in the node output, verify all input parameters, and ensure API credentials are valid.

Links and References

Discussion