# Receive webhooks (`riceman/receive-webhooks`) Actor

Receives webhook data and saves it to Apify dataset storage. Ideal for Clay users on the Starter plan who still want or need to build tables that can receive webhooks.

- **URL**: https://apify.com/riceman/receive-webhooks.md
- **Developed by:** [RICEMAN](https://apify.com/riceman) (community)
- **Categories:** Developer tools, Automation, Integrations
- **Stats:** 79 total users, 2 monthly users, 100.0% runs succeeded, 3 bookmarks
- **User rating**: No ratings yet

## Pricing

$5.00 / 1,000 webhook receiveds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## 📬 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

# Actor input Schema

## Actor input object example

```json
{}
```

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("riceman/receive-webhooks").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("riceman/receive-webhooks").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call riceman/receive-webhooks --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,riceman/receive-webhooks"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/jQ0ccCffD9dBBJvQN/builds/j3cbB5w3dSlMoKe2O/openapi.json