Connecting to Hospitable.com via Webhooks

Overview

Hospitable.com supports outbound webhooks that fire on reservation and messaging events. You can point those webhooks at your OpenClaw agent so it receives and acts on them automatically — for example, sending a personalised welcome message when a new booking arrives.

AgentClaw provides a Webhook Relay— a public URL that accepts requests from Hospitable (or any service) without requiring custom authentication headers. AgentClaw automatically adds the required authorization header when forwarding the request to your agent. This means you do not need to configure any secret or token on Hospitable's side.

Step 1 — Create a webhook endpoint

1. Go to your AgentClaw Dashboard and open your instance.
2. Click the Webhooks tab.
3. Click New endpoint.
4. Fill in the form:
   • Name — e.g. Hospitable
   • Endpoint path — a URL-safe slug such as hospitable. This becomes the last segment of your relay URL.
   • Target — choose Agent run (/hooks/agent) to trigger a full agent task on each event.
   • IP allowlist— optionally restrict which IPs can call this endpoint. You can add Hospitable's outbound IP ranges here. Leave blank to allow all IPs.
5. Click Create endpoint. AgentClaw will enable webhooks on your instance and restart the agent automatically (takes about 1 minute).
6. Once saved, copy the Relay URL shown on the endpoint card. It looks like:

   https://agentclaw.app/api/webhooks/instance/<instanceId>/hospitable

Step 2 — Add the webhook in Hospitable

1. Log in to app.hospitable.com
2. Go to Settings → Integrations → Webhooks (or Automations → Webhooks, depending on your plan).
3. Click Add webhook.
4. Paste your Relay URL into the Endpoint URL field.
5. No secret or authorization header is required — AgentClaw handles authentication automatically on your behalf.
6. Select the events you want to receive, for example:
   • Reservation created
   • Reservation cancelled
   • Guest message received
   • Review submitted
7. Save the webhook. Hospitable will send a test ping to verify the URL is reachable.

Step 3 — Verify the connection

1. After saving, Hospitable sends a test event to your relay URL.
2. In AgentClaw, open your instance and go to the Terminal tab (or view Logs) to confirm the request was received by OpenClaw.
3. A successful test ping returns HTTP 200. Your integration is now live.

How the relay works

When Hospitable sends a POST request to your relay URL, AgentClaw:

1. Looks up the endpoint record for your instance and path.
2. Checks the caller's IP against your allowlist (if configured).
3. Forwards the original request body to your agent's /hooks/agent endpoint, automatically adding the Authorization: Bearer <token> header that OpenClaw requires.
4. Returns your agent's response back to Hospitable.

You can manage your webhook endpoints (edit, delete, or refresh the cached token) at any time from the Webhooks tab on your instance page.

Troubleshooting

• Hospitable reports a timeout or connection error — check that your instance status is Running. If it was just restarted after creating the endpoint, wait about 1 minute for it to become ready.
• Relay returns 404 — the endpoint path in the URL does not match any saved endpoint for this instance. Double-check the Relay URL shown on the Webhooks tab.
• Relay returns 403— the caller's IP is not in your IP allowlist. Either add Hospitable's IP range or leave the allowlist empty to allow all IPs.
• Relay returns 503 — Webhook not configured — the endpoint was created before the instance was running, so no token was cached. Click the Refresh token button on the endpoint card while the instance is running.
• Events not triggering agent responses — verify the OpenClaw skill or automation that handles /hooks/agent is installed and enabled. Check the instance logs for errors.

Next steps

• Learn about Telegram integration to route Hospitable guest messages to a Telegram bot.
• Review managing API keys to configure the AI model that processes your webhook events.
• Read the Hospitable webhooks documentation for the full list of supported events and payload formats.