Skip to content

Webhooks

Jump to bottom
itsDNNS edited this page Apr 30, 2026 · 1 revision

Webhooks

Webhooks let Tribu notify another system when selected household events happen.

What webhooks support

  • admin-managed webhook endpoints
  • event subscriptions
  • test deliveries
  • delivery status
  • outbound events for household activity such as calendar, tasks, shopping, birthdays, quick capture, and related updates
  • Home Assistant integration through webhook automation

Recommended setup

  1. Create a receiving endpoint in the target system.
  2. Create a webhook endpoint in Tribu.
  3. Subscribe only to the events you need.
  4. Send a test delivery.
  5. Check delivery status in Tribu and logs in the receiving system.
  6. Add real automations only after the test is stable.

Privacy and safety

  • Treat webhook URLs as secrets when they contain random IDs or tokens.
  • Do not paste full webhook URLs into public issues or screenshots.
  • Subscribe to the smallest useful event set.
  • Avoid sending family data to systems you do not control.

Example: Home Assistant persistent notification

  1. Create a Home Assistant webhook automation.
  2. Store the webhook ID in Home Assistant secrets.
  3. Point Tribu to https://home-assistant.example.com/api/webhook/<id>.
  4. Subscribe to an event such as task.created.
  5. Use Tribu's test button and inspect the Home Assistant automation trace.

See Home Assistant for the package path.

Troubleshooting

Test delivery fails

  • Confirm the target URL is reachable from the Tribu backend container.
  • Confirm TLS certificates are valid if using HTTPS.
  • Confirm the receiving system expects the method and payload Tribu sends.
  • Check whether a reverse proxy or firewall blocks the request.

Events arrive too often

Reduce subscriptions to the minimum useful set. Start with one event type, then expand.

Related pages

Clone this wiki locally