Connection details
Open Clay setup in Ziplined. Give the connection an account label your team recognizes. Paste the complete incoming webhook URL generated for your intended Clay table and, if that webhook requires it, its authentication token. Copy these from the incoming webhook setup, rather than using a Public API key or an outbound webhook URL. Clay menus and incoming authentication must be confirmed against an owned test table before this feature is released; no menu sequence or token header is verified here. Never paste secrets into support messages or shared links. The URL and token are stored privately; they are not a link to open from the app. Save without starting stores the connection only. Not tested means that Clay has not acknowledged a test request. Changing the token preserves the destination. A different webhook URL creates a separate destination and can receive the same person again. Reuse the saved connection for the same endpoint.Send a sample
Sample sending remains disabled while the incoming contract is unverified. When it becomes available, Send sample row requires an explicit confirmation and sends one synthetic row forZiplined test person. It contains no real person, email, phone or customer view URL. It does not start a sync.
A row accepted by Clay may trigger Clay automations, enrichments, credits or downstream actions. Review those settings first. Accepted by Clay means the verified incoming request was acknowledged; it does not prove enrichment or downstream delivery finished. If the result is unclear, check the intended Clay table and use Check sample status. Do not send another sample to work around an uncertain result.
What gets exported
You choose the fields when you set up the sync. The default set is marked below. Clay and webhooks receive the field keys; Google Sheets uses the column labels, in the order you chose. A Google Sheets tab keeps its columns once it exists: for other columns, make a new tab. Work email and phone are coming soon.is_lead is true when the person passed your ideal client. A hand-picked view may hold someone who did not.
Missing optional values stay blank. No email address, phone number or paid enrichment is added. Headlines are profile text; the job title is the current position on the profile.
Start and manage
When available, Start puts the sync in Preparing. The first valid view check establishes the starting set and sends nobody. Only people first observed on later checks qualify. Someone who enters and leaves between checks may never be observed. There is no backfill of everyone already in a view. A filter change prepares the view again. Pause stops new sends. Resume establishes a new excluded starting set and keeps previously waiting people held. Send waiting people is an explicit action for eligible safe waiting work; it does not resend uncertain transfers. Stop removes local sending authority. Disconnect revokes local connection authority. Neither can undo an external write that already started. A recorded person/destination transfer is not repeated when views overlap or a sync restarts. A separate destination can receive that person again. An uncertain result stays held: do not repeatedly reconnect or create a new destination to force another transfer. Use History and contact support.Troubleshooting
The exact Settings link above opens setup only. A view-specific link has the form
https://app.ziplined.io/engagers?view=<view-id>&sync=open&connect=clay. Opening a link grants no write permission and sends nothing. Unavailable features remain disabled.