ContactShip Trigger icon

ContactShip Trigger

Handle webhook events from ContactShip with multiple outputs based on call result
Join our community

Overview

This node acts as a webhook trigger for ContactShip events, specifically handling incoming webhook calls and routing them to different outputs based on the call result status. It supports multiple outputs such as "Answered", "Voicemail", "No Answer", "Failed", and "Other" to categorize the call outcomes.

Common scenarios where this node is beneficial include:

  • Automating workflows triggered by phone call events from ContactShip.
  • Routing calls differently in your automation depending on whether the call was answered, went to voicemail, was not answered, or failed.
  • Logging or processing call data with detailed debugging enabled.

For example, you could use this node to start a workflow that sends an SMS notification when a call goes unanswered or logs call details into a CRM system when a call is answered.

Properties

Name Meaning
Authentication Method of authentication to use with the webhook. Options: None, Basic Auth
Username Username for Basic Authentication (shown only if Basic Auth is selected)
Password Password for Basic Authentication (shown only if Basic Auth is selected)
Headers List of HTTP headers to check in the webhook request. Each header has a name and expected value. The webhook request must contain these headers with matching values to be accepted.
Debug Mode Enable debug mode to log payload details to the console for troubleshooting purposes

Output

The node outputs data through five separate outputs corresponding to the call result:

  1. Answered — Triggered when the call result is "answered".
  2. Voicemail — Triggered when the call result is "voicemail".
  3. No Answer — Triggered when the call result is "no_answer" or "busy".
  4. Failed — Triggered when the call result is "failed".
  5. Other — Triggered for any other call results or if the call result is missing.

Each output receives an array of items containing a single JSON object representing the webhook payload received from ContactShip under the json field.

If debug mode is enabled, the full payload and call result are logged to the console.

The node does not output binary data.

Dependencies

  • Requires a publicly accessible webhook URL configured in ContactShip to send events to this node.
  • Supports optional Basic Authentication for securing the webhook endpoint.
  • No external API keys or credentials are strictly required unless Basic Auth is enabled.
  • No additional environment variables or n8n configurations are necessary beyond standard webhook setup.

Troubleshooting

  • Basic Auth errors: If Basic Authentication is enabled but the Authorization header is missing or credentials do not match, the node responds with HTTP 401 Unauthorized and no workflow execution occurs. Ensure the correct username and password are set and that ContactShip sends the Authorization header properly.
  • Header validation failures: If custom headers are configured, the webhook request must include all specified headers with exact matching values; otherwise, the node responds with HTTP 403 Forbidden.
  • Invalid webhook payload: If the webhook body cannot be parsed as JSON, the node responds with HTTP 400 Bad Request.
  • Unexpected call results: Calls with unrecognized call results are routed to the "Other" output.
  • Debugging: Enable Debug Mode to log the full webhook payload and call result to the console for easier troubleshooting.

Links and References

Discussion