ContactShip Trigger icon

ContactShip Trigger

Starts the workflow when a ContactShip voice agent finishes a call, or when a text agent closes a follow-up

ContactShip Trigger

AI-generated

Summary

Receive and process incoming webhook POST requests from ContactShip, triggering the workflow with data about call results or follow-up closures.

Inputs

  • Authentication — Optionally enforce Basic Auth by specifying a username and password to ensure requests come from ContactShip.
  • Username — Username for Basic Auth, if enabled.
  • Password — Password for Basic Auth, if enabled.
  • Required Headers — Specify exact HTTP headers and their values that each incoming request must contain; requests missing these or with differing values are rejected.

Output shape

Multiple output channels depending on event type: for v2, six outputs labeled 'Answered', 'Voicemail', 'No Answer', 'Failed', 'Other', and 'Follow-Up Closed'. For v1, five outputs without 'Follow-Up Closed'. Each output provides a JSON array with the webhook payload for matching event types.

Route selection is automatic based on webhook POST request content from ContactShip. To activate, paste this node's Production URL into ContactShip's respective agent configurations (voice agent for call results, text agent for follow-up closures) and activate the workflow. Authentication and required headers settings control security. If authentication or required headers checks fail, the webhook responds with HTTP 401 or 403 and no workflow trigger occurs.

Links

Discussion