Overview

This node acts as a webhook trigger for Teamwork, starting a workflow when a Teamwork webhook is called. It processes incoming webhook data, parses the message header, and maps various fields based on the message type to structure the output data. This node is useful for automating workflows that respond to Teamwork events such as messages, audio messages, or file sharing within Teamwork sessions.

Use Case Examples

1. Automatically trigger a workflow when a new message is received in Teamwork.
2. Start a workflow to process audio messages or shared files from Teamwork webhooks.

Properties

Output

JSON

• workflowData
  • 0
    * 0
    * json
    * sessionId - Unique session identifier combining sender and receiver IDs.
    * messageType - Type of the message received from Teamwork webhook.
    * messageContent - Content of the message (for message type 1 and default).
    * messagePushContent - Push notification content of the message.
    * audioDuration - Duration of the audio message (for message type 2).
    * files - Array of file objects with preview URL, file URL, and content type (for message type 3).

Dependencies

• Requires an API key credential or authentication to receive Teamwork webhook calls.

Troubleshooting

• Ensure the webhook path matches the path configured in Teamwork to receive webhook calls correctly.
• If the webhook payload is not parsed correctly, verify that the incoming messageHeader is a valid JSON string.
• Common errors may include missing or malformed webhook data, which can be resolved by checking the webhook configuration and payload format.

Links

• Teamwork Webhooks Documentation - Official documentation for setting up and using Teamwork webhooks.