> ## Documentation Index > Fetch the complete documentation index at: https://docs.ziplined.io/llms.txt > Use this file to discover all available pages before exploring further. # Send People to Clay > Private connection setup, explicit samples and safe future-member exports. > [!WARNING] > > Clay incoming export is not available for live use yet. The incoming webhook contract and controlled-provider acceptance must be verified before sending can be enabled. Saving connection details does not verify access or send a row. This guide covers sending People to Clay. To import Ziplined data through Clay's HTTP API enrichment instead, use [the Clay API guide](https://docs.ziplined.io/integrations/clay.md). ## Connection details [Open Clay setup in Ziplined](https://app.ziplined.io/settings/integrations?connect=clay). 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 for `Ziplined 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. | Field key | Google Sheets column | Default | | - | - | - | | `first_name` | First name | on | | `last_name` | Last name | on | | `full_name` | Full name | | | `job_title` | Job title | on | | `headline` | Headline | | | `seniority` | Seniority | | | `location` | Location | on | | `country` | Country | | | `linkedin_url` | LinkedIn URL | on | | `company` | Company | on | | `company_website` | Company website | on | | `company_size` | Company size | on | | `industry` | Industry | on | | `signal` | Signal | on | | `signal_text` | Comment or post text | on | | `post_text` | Post text | on | | `post_topic` | Post topic | on | | `post_url` | Post link | on | | `signal_date` | Signal date | on | | `added_on` | Added on | on | | `ziplined_url` | Open in Ziplined | on | | `view_name` | View | | | `warmth_score` | Warmth score | | | `is_lead` | Lead | | | `ziplined_id` | Ziplined ID | | `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 | What you see | What to do | | - | - | | Incoming contract is being verified | Save privately if needed; sending is unavailable until provider acceptance is complete. | | Not tested | Saving and local URL validation do not test Clay access. | | Authentication changed | Update the token on the existing connection. An unclear earlier request stays held. | | Result is unclear | Check the intended table and downstream actions. Contact support before retrying. | | Accepted but no downstream result | Inspect Clay's own processing, credits and automations; Ziplined does not import their status. | The exact Settings link above opens setup only. A view-specific link has the form `https://app.ziplined.io/engagers?view=&sync=open&connect=clay`. Opening a link grants no write permission and sends nothing. Unavailable features remain disabled. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.