📬 Webhook Receiver to Apify Storage This actor receives webhook data via HTTP requests and automatically saves it to Apify dataset storage. It's especially useful if you're a Clay user - you can bypass webhook table limitations on the Starter plan by starting with data collected via this actor. ## 🚀 How It Works When a webhook or HTTP POST request is sent to this actor's endpoint, the JSON payload is captured and pushed directly into the actor's dataset. This lets you store incoming data and easily reference or process it later. ## ✅ Recommended Setup For best results, create a separate Apify Task for each Clay table or use case. Why? Each task comes with: - A unique API endpoint — ideal for sending webhooks from different sources. - A separate dataset — keeping your data clean and segmented for each use case. This setup ensures your Clay tables only receive the specific data they're meant to work with, without any risk of overlap or confusion. ## 🔗 Getting Your Webhook Endpoint To get the URL where you should send webhook or HTTP requests: 1. Navigate to your actor or task on Apify. 2. Click API in the top-right corner. 3. Select API endpoints. 4. Copy the URL under Run task. You can now send your webhook payloads (typically via HTTP POST) to this URL. ## 🙌 Use Cases - Sending webhook form submissions to Apify - Capturing data from Zapier, Make, or other automation tools - Starting Clay tables with external webhook data