Tailwind Trigger icon

Tailwind Trigger

Starts the workflow when tailwind events occur
Join our community

Overview

This node acts as a trigger that starts an n8n workflow when specific events occur in the Tailwind service related to a selected device. It listens for incoming webhook calls from Tailwind, validates them using an API key, and then passes the event data into the workflow.

Common scenarios include automating processes based on device events such as status updates, alerts, or other Tailwind-generated triggers. For example, you could use this node to start a workflow that sends notifications or logs data whenever a particular device reports an event.

Properties

Name Meaning
Device Selects the Tailwind device to monitor for events. The node will listen for triggers related to this device.

Output

The node outputs JSON data representing the event payload received from Tailwind. This data combines both the webhook body and query parameters, providing all relevant information about the triggered event.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for authenticating with the Tailwind service.
  • Needs network access to receive webhooks from Tailwind.
  • Uses Tailwind's API to manage webhook subscriptions (create, check existence, delete).
  • The node expects the user to configure the device to monitor via the input property.

Troubleshooting

  • Access Denied (403): If the incoming webhook request does not contain the correct API key in the x-api-key header, the node responds with a 403 error and denies processing. Ensure the API key configured in the node matches the one used by Tailwind to send webhooks.
  • Invalid Credentials (403): If the node cannot retrieve the stored API key credential, it will reject requests. Verify that the API key credential is properly set up in n8n.
  • Webhook Not Triggering: Confirm that the webhook URL registered with Tailwind matches the URL generated by the node and that the device ID is correct.
  • Webhook Creation Failures: If the node fails to create or delete webhook subscriptions, check network connectivity and API permissions.

Links and References

  • Tailwind API documentation (for managing devices and webhooks)
  • n8n documentation on creating webhook triggers
  • General webhook best practices and security guidelines

Discussion