> ## 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. # Outreach sync > Connect an outreach account and understand which people are sent, when, and how to manage transfers. An outreach sync sends new people from one saved People view to a destination you choose. Connect [HeyReach](https://docs.ziplined.io/integrations/heyreach.md), [Instantly](https://docs.ziplined.io/integrations/instantly.md), or [Waalaxy](https://docs.ziplined.io/integrations/waalaxy.md). | Provider | Destination | Required person data | | - | - | - | | HeyReach | Active campaign | Valid LinkedIn profile URL | | Instantly | Active campaign | Verified email already available in Ziplined | | Waalaxy | Prospect list only | Valid LinkedIn profile URL | This is a one-way transfer. Replies, campaign results and engagement are not imported into Ziplined. Waalaxy campaign enrollment is not included. ## Connect an account Open **Settings → Integrations** and choose a provider. Follow its guide to create an API key, enter an **Account label**, then select **Check access**. Checking access is read-only: it sends no test lead and starts no sync. Select **Done** to save only the account. The same connection can be reused for another view with **Use account**. If a provider is unavailable in your workspace, contact Ziplined support. Do not paste its API key into another provider's form. ## Start a sync Select **Set up a sync**, choose a People view and a target, then select **Start sync**. From a view, open its sync setup and choose the outreach provider. Review campaign content and sending settings in the provider first. Adding leads to an active HeyReach or Instantly campaign can trigger real outreach. | State | What happens | | - | - | | Preparing | Ziplined records the people currently in your view. No people are sent during preparation. | | On | New eligible people observed entering the view can be sent. | | Paused | Waiting transfers are held. New arrivals while paused are excluded. | | Needs action | Check the account and reconnect if access changed. | | Stopped | Pending transfers are cancelled and history remains. | People already present during preparation are excluded. This is not a historical export. View membership is checked periodically; someone who enters and leaves between checks may not be observed. Ziplined avoids submitting the same person again to the same connected account and destination across views, including after stopping and starting a sync again. Provider duplicate rules also apply. Reconnect an existing account when rotating a key; a new connection is not a way to intentionally resend people. ## First transfer Use a dedicated test target and an eligible person you have permission to test with. Wait for **On**, then let that person enter the view. Check the recent transfer history and the provider's own destination. The provider guides explain the data requirements for each tool. **Accepted by provider** is not proof that a message was sent or that an asynchronous import has finished. Confirm the result in the provider before widening your rollout. ## Transfer history | Result | Meaning and next step | | - | - | | Added | The provider reported that the person was added. Check sending activity in the provider. | | Accepted by provider | The provider accepted the request. Verify the final import in the provider. | | Skipped | The person was not added, for example because required data was missing or the provider skipped an existing prospect. | | Held. Your action is required. | The transfer is held. Review the sync state before retrying. | | Needs a check. This request will not repeat automatically. | Ziplined cannot safely confirm the result. Check the provider before taking further action. | | Cancelled | Pending delivery authority was cancelled. A request already accepted by the provider cannot be recalled. | History shows recent transfers, not a full provider activity log. Ziplined does not pull final campaign outcomes back into the app. ## Manage a sync * **Pause:** holds existing waiting people. It excludes new arrivals during the pause. A request already sent to the provider may still complete. * **Resume:** prepares a fresh baseline. People currently in the view are excluded; previously held people do not automatically flush. * **Retry waiting people:** explicitly resumes eligible held transfers after preparation. Uncertain writes remain held to avoid duplicates. * **Stop:** cancels pending transfers and keeps history. It cannot remove leads or retract messages already accepted by the provider. * **Reconnect:** replaces a connection's API key and checks access again. It does not automatically resend waiting transfers. Paused syncs remain paused; review their state afterwards. * **Disconnect account:** removes its credentials and stops its pending transfer authority. Review every sync that uses this shared connection. ## Troubleshooting If no person arrives, first confirm the sync is **On**, then check that the person entered after preparation and has the provider's required data. Check the selected account and destination, provider quotas and recent transfer history. For **Needs a check**, search for the person in the provider before taking further action. Do not create a second connection to force a retry. Contact Ziplined support with the provider name, destination, transfer time and visible result. Never include your API key. For account-specific help, use the [HeyReach](https://docs.ziplined.io/integrations/heyreach.md#troubleshooting), [Instantly](https://docs.ziplined.io/integrations/instantly.md#troubleshooting), or [Waalaxy](https://docs.ziplined.io/integrations/waalaxy.md#troubleshooting) guide. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.