Webhooks
Create webhook endpoints for MCP-visible events such as generated media, failed jobs, published posts, automation output, and completed tool calls.
Supported events
avatar.generated
avatar.failed
product_scene.generated
product_scene.failed
hook.generated
hook.failed
ai_clone.generated
ai_clone.failed
video.completed
video.failed
slideshow.exported
product_asset.uploaded
slideshow_video.generated
slideshow_video.failed
scheduled_post.published
scheduled_post.failed
scheduled_post.cancelled
automation.generated
tool.completedCreate a webhook
Open Account → MCP → Webhook security. Enter the HTTPS destination and create the endpoint there. Agents cannot create, change, or delete webhook destinations.
Security boundary
Webhook management is dashboard-only in Review, Creator, and Autopilot. Deliveries use DNS-pinned HTTPS egress and do not follow redirects.
Secret is returned once
The signing secret starts with rfmcpwh_ and is returned only when the webhook is created. Store it immediately.
Signature headers
Webhook deliveries include event metadata and an HMAC signature. Verify the signature before trusting the payload.
user-agent: ReelsFarm-MCP-Webhooks/1.0
x-reelsfarm-event-id: evt_123
x-reelsfarm-event-type: scheduled_post.published
x-reelsfarm-signature: sha256=...Inspect activity
reelsfarm webhooks list --agent
reelsfarm events recent --type scheduled_post.published --agentconst webhooks = await rf.webhooks.list();
const events = await rf.events.recent({
type: "scheduled_post.published",
limit: 20,
});