Geprüfte Kontaktdaten, als Clay-Spalte.

Support boundary

Run it in this order

1. 1

   Choose source or enrichment

   Decide whether Clay starts with rows to enrich or needs Argorant to create the company and contact universe.

   Expected: The request maps to the correct Argorant endpoint and output shape.
2. 2

   Secure and test one row

   Store the key as a credential, map inputs, and run success, miss, 401, and 429 cases on one row.

   Expected: Known response and error branches without table-wide cost.
3. 3

   Add run conditions

   Require complete inputs, empty target fields, eligible status, and bounded row scope before calling.

   Expected: No duplicate or pointless calls.
4. 4

   Scale and reconcile

   Run a limited batch, compare Clay Actions/Data Credits to Argorant successful output, and inspect every reject.

   Expected: Predictable cost and complete row accounting.

Confirm the audience before handoff

The matching count is visible before contact output. Check it and a masked sample before a paid export or destination push is allowed.

Current source pages