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.
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
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.