Homecast Docs

Appearance

HomePortal

Webhook ​

Category: Trigger

Fires when an HTTP POST request is sent to the automation's webhook URL. Use this to trigger automations from external services, IFTTT, scripts, or other systems.

When to use ​

  • Receive events from external services (weather alerts, calendar events)
  • Trigger automations from a custom script or cron job
  • Integrate with IFTTT, Zapier, or other webhook-based platforms
  • Let other automations trigger this one via HTTP

Configuration ​

  • Webhook ID — A unique identifier for this webhook endpoint. The full URL will be shown after saving.

Output data ​

The incoming request body is available to downstream nodes:

  • {{ trigger.webhook_payload }} — The full JSON body of the incoming request
  • {{ trigger.timestamp }} — When the webhook was received

If the incoming body is JSON, you can access nested fields:

  • {{ trigger.webhook_payload.temperature }}
  • {{ trigger.webhook_payload.event.type }}

Examples ​

Weather alert automation:

  1. Webhook → receives { "alert": "storm", "severity": "high" }
  2. IF → trigger.webhook_payload.severity == 'high'
  3. Set Device → close all blinds
  4. Notify → "Storm warning — blinds closed"

External script trigger:

bash
curl -X POST https://your-relay/mcp \
  -H "Content-Type: application/json" \
  -d '{"action": "arm_night_mode"}'

Tips ​

  • Webhook payloads are available as trigger.webhook_payload — use dot notation to access nested fields
  • Secure your webhook URL — anyone with the URL can trigger your automation
  • Use an IF node after the webhook to validate the payload before taking action