Apify → Clay Results Pusher

Push results from the most recent run of any Apify task or actor directly into Clay via webhook — safely, predictably, and without duplicates.

This actor is designed as workflow glue between Apify and Clay. It does not scrape, rerun tasks or actors, or process historical data.

---

Why use this actor

• Safely push Apify results into Clay
• Works with both Apify Tasks and Actors
• Uses ONLY the most recent SUCCEEDED run
• Never re-runs tasks or actors
• Prevents duplicate pushes by default
• Designed for production workflows

---

How it works

1. Paste your Apify Task or Actor URL (or ID)
2. Paste your Clay webhook URL
3. Run the actor

Only the latest SUCCEEDED run is used.
Duplicate pushes are prevented automatically.

---

Quick start (2 minutes)

1. Run any Apify task or actor at least once
2. In Clay, create a table and choose Import → Webhook
3. Copy the Clay webhook URL
4. Paste the Apify source URL and Clay webhook URL into this actor
5. Run the actor

Your data will appear in Clay automatically — one row per result.

---

What this actor does

• Pulls results from ONLY the most recent run
• Supports Apify Tasks and Apify Actors
• Optionally requires the run to be SUCCEEDED (recommended)
• Pushes one row per result to your Clay webhook
• Flattens nested JSON into Clay-friendly flat fields
• Adds optional metadata (_apifyRunId, _apifyRunFingerprint, etc.)
• Prevents duplicate pushes using a run-lock mechanism

---

What this actor does NOT do (important)

• ❌ Does not start or rerun Apify tasks or actors
• ❌ Does not scrape or crawl websites
• ❌ Does not process historical or older runs
• ❌ Does not transform, enrich, or filter data beyond flattening

If you need scraping or enrichment, run those actors before this one.

---

Perfect for

• Lead generation
• Recruitment pipelines
• Data enrichment workflows
• No-code automation stacks
• Clay-based GTM pipelines

---

Required inputs

1) Clay Webhook URL

Create a webhook in Clay:

Clay table → Import → Webhook

Paste the generated webhook URL into this actor.
Each result will be added to Clay as one row.

---

2) Apify Source URL (Task or Actor)

Paste one of the following:

• An Apify Task URL
• An Apify Actor URL
• A raw Task ID
• A raw Actor ID

Only the most recent run of the source will ever be used.

---

Optional inputs

Apify API Token (optional)

Required only if:

• The task or actor belongs to a different Apify account or organisation, or
• The actor does not have permission to read runs or datasets

Required token permissions:

• Read actors and/or tasks
• Read runs
• Read datasets

No other permissions are needed.

---

Deduplication (very important)

This actor adds the following field to each row:

_apifyRunFingerprint =

Recommended Clay setup

• Use _apifyRunFingerprint as a unique / dedupe key in Clay

This guarantees:

• No duplicate rows
• Safe re-runs of this actor
• Idempotent automation pipelines

The actor also uses an internal run-lock, so the same run is never pushed twice.

---

Pricing

This actor is billed per result pushed.

• $1 per 1,000 rows
• Example: pushing 2,500 rows costs $2.50
• A small actor start fee may also apply

This pricing model keeps costs predictable, transparent, and proportional to usage.

---

Common errors and how to fix them

“Insufficient permissions (403)”

Cause:
The actor cannot read runs or datasets for the source.

Fix:

• Provide an Apify API token, or
• Run this actor under the same Apify account or organisation as the source

---

“No runs found”

Cause:
The task or actor has never been executed.

Fix:

• Run the task or actor at least once before using this actor

---

“Latest run status is not SUCCEEDED”

Cause:
The most recent run failed or was aborted.

Fix:

• Fix the upstream task or actor and rerun it
• This behaviour is intentional to prevent partial or corrupt data pushes

---

“Nothing pushed”

Cause:
The dataset from the most recent run is empty.

Fix:

• Check the source run’s output dataset in Apify

---

Recommended workflow

Apify Task or Actor (scheduled or manual) ↓ Apify → Clay Results Pusher (this actor) ↓ Clay (dedupe, enrichment, routing, CRM, outreach)

This actor is intentionally simple and predictable so it can be safely used in scheduled workflows.

---

Notes and guarantees

• Only the most recent run is ever used
• Historical runs are never processed
• The actor is safe to rerun
• Duplicate pushes are prevented by default
• Designed for production and Apify Store usage

---

Summary

If you need a reliable bridge between Apify and Clay — supporting both tasks and actors, without re-scraping, duplicate rows, or brittle glue code — this actor is built for exactly that.