Webhook Relays

Many external services — including Slack, GitHub, and Jira — communicate with your applications by sending webhooks: HTTP requests to a public URL whenever something happens (a message is sent, a pull request is opened, an issue is updated). Since your Errand installation runs on your local network and doesn’t have a public URL, these webhooks can’t reach it directly.

Errand Cloud solves this by acting as a webhook relay. It provides public URLs that external services can send webhooks to, and forwards those requests to your local Errand installation through the encrypted connection.

How Webhook Relay Works

1. When you connect to Errand Cloud, it generates unique webhook URLs for your installation
2. You configure your external services (Slack, GitHub, Jira) to send webhooks to these URLs
3. When a webhook arrives at Errand Cloud, it’s immediately forwarded to your local installation through the encrypted tunnel
4. Your local Errand server processes the webhook and takes the appropriate action

If your installation is temporarily offline, webhooks are queued for up to 48 hours and delivered as soon as it comes back online.

Cloud Endpoints

After connecting to Errand Cloud, you’ll find your webhook URLs on the Settings > Cloud Service page. These are the URLs you’ll use when configuring external services.

Slack

Slack requires three separate webhook URLs:

• Events URL — receives messages and other workspace events
• Commands URL — handles slash commands like /errand
• Interactivity URL — processes button clicks, menu selections, and other interactive components

Copy these URLs into your Slack app configuration under Event Subscriptions, Slash Commands, and Interactivity & Shortcuts respectively. See the Slack integration guide for detailed setup instructions.

GitHub

GitHub uses a single webhook URL for all events. When setting up a webhook on your repository or organisation:

• Payload URL — use your Errand Cloud GitHub webhook endpoint
• Content type — select application/json
• Events — choose which events to send (or select “Send me everything”)

See the GitHub integration guide for detailed setup instructions.

Jira

Jira Cloud uses a webhook URL to notify Errand when issues are created or updated. When configuring your Jira webhook:

• URL — use your Errand Cloud Jira webhook endpoint
• Events — select the issue events you want to trigger tasks

See the Jira integration guide for detailed setup instructions.

Troubleshooting

Webhooks not arriving?

• Verify that the cloud endpoint URLs are correctly configured in your Slack app, GitHub webhook, or Jira settings
• Check that your installation is online and connected to the cloud service (the settings page will show the connection status)
• Confirm your Errand Cloud subscription is active

Delayed webhooks?

• If your installation was recently offline, queued webhooks may take a moment to be delivered after reconnection
• Check your server logs for any processing errors

Webhook URL changed?

• Your webhook URLs remain stable as long as your installation stays connected to the same Errand Cloud account. If you disconnect and reconnect, new URLs may be generated — update your external service configurations if this happens.