Send a Listful export to Clay, n8n, or Make
CSV download works without an account. To POST rows to Clay, n8n, or Make, sign in, add a destination in Settings, and verify the signature. Batch mode sends export.completed with rows[]; One row mode sends one export.row POST per person for Clay.
Steps
Full payload and signature docs: /docs/webhook.
CSV first, webhook optional
Every successful export still downloads a local CSV. Destinations are an extra path for teams that already live in Clay, n8n, or Make — not a requirement to use Listful.
Signed delivery
Create a free Listful account, add an HTTPS destination in Settings, and verify the signature header on each POST. Batch vs row mode, chunking, and retry notes live in /docs/webhook.
What arrives
Batch destinations receive export.completed with jobId, surfaceType, sourceUrl, and rows[]. Row destinations receive one flat export.row object per person. Map columns the same way you would from the CSV header.
Questions.
Q01Do I need an account for CSV?
No. Webhooks are optional. The file still downloads locally.
Q02Where are webhook docs?
See /docs/webhook for the payload shape, signature header, and setup steps.
Q03Clay specifically?
Add a destination in Settings, choose One row mode, paste the Clay monitor webhook URL, and map profile_url. Optional auth header for Clay’s token. Listful does not host a Clay marketplace app.
Q04Failed webhook — is the CSV lost?
No. The CSV download is independent. Check webhook retries and signature verification if the POST fails.
Q05Enrichment in the webhook?
Webhook rows match the export. Enrichment is a separate optional step when you buy hits.
Q06Rate of delivery?
One completion event per finished job. Large row arrays follow the docs size notes — prefer local CSV if your automation times out.
Related exports
Export a listwhen you’re ready.
No account, no row credits. LinkedIn’s own page caps still apply.