Webhooks

Send event data to external services—Slack, Discord, Zapier, or your own endpoints. Webhooks let your automations communicate with the outside world.

Setting up webhooks

Configure webhooks in your account settings. Each webhook has:

• Name — a friendly identifier you'll use in your code (e.g., slack, discord)
• URL — the endpoint that receives the POST request
• Headers — optional HTTP headers (e.g., for authentication)

Using webhooks in code

Call webhooks from your automation code using context.webhooks:

// Send a simple message to Slack context.webhooks.slack.post({ text: "Buy Box lost on " + event.asin }); // Send structured data to your own endpoint context.webhooks.analytics.post({ event: event.type, asin: event.asin, price: event.buyBoxPrice, timestamp: event.timestamp });    

Common integrations

Slack

Use a Slack Incoming Webhook URL. The payload should include a text field:

context.webhooks.slack.post({ text: "🏆 Won Buy Box on " + event.asin + " at $" + (event.buyBoxPrice / 100) });    

Discord

Use a Discord Webhook URL. The payload should include a content field:

context.webhooks.discord.post({ content: "Price changed on " + event.asin });

Zapier

Use a Zapier Webhook (Catch Hook) URL. Send any JSON payload—Zapier will parse it automatically.

Error handling

Webhook calls are fire-and-forget. If the endpoint is down or returns an error, your automation continues running. Failed webhook calls are logged so you can diagnose issues later.