A spreadsheet row should become a campaign lead only after a person approves its audience fit and checks the address against your exclusion rules. The supported connection is straightforward: Google's spreadsheet event triggers Zapier's Add lead to campaign action for one selected Instantly campaign. The difficult part is making sure an edit, duplicate, opt-out, or wrong campaign does not create an unwanted send.
Instantly publishes an exact Google Sheets → Instantly Zapier recipe. It documents a New or Updated Spreadsheet Row trigger, the target campaign choice, a skip-existing-leads option, and a launch-campaign option. Those instructions, Zapier's matching template, and Instantly's blocklist guidance were checked October 22, 2026. We have not run the Zap in a private account. The approval workflow below is a proposed control, not a built-in Instantly feature.
Pick the connection method
For an occasional batch, Instantly's direct Google Sheets import lets you review the file, field mapping, duplicate choice, and skipped count before uploading. That route requires making the Sheet accessible to anyone with the link under Instantly's documented instructions; assess whether that sharing model suits your data policy before using it.
For a continuing intake queue, Zapier's row trigger and Instantly action can move rows as they change. This guide covers that ongoing approved-row job. A scheduled manual review may be more appropriate if approval volume is low or the team cannot monitor Zap failures.
Design the sheet as an approval queue
Keep one row per candidate address. Suggested columns are Email, Campaign, Approval, Approved at, Approved by, Exclusion checked at, Imported at, Instantly result, and the campaign variables you actually use. These are your internal operating fields, not fields the connector promises to generate. Avoid putting credentials, private notes, or unnecessary personal data in the sheet.
Define eligibility before activating the Zap:
| Check | Proposed rule |
|---|---|
| Approval | Only rows explicitly marked Approved by an authorized reviewer may pass the Zap filter. A blank or draft row stays in the sheet. |
| Campaign | The approved row's campaign label must equal the single target campaign configured in the Instantly action. Do not trust the sheet label to select a destination dynamically. |
| Address | Email is present, valid-looking, and normalized for your comparison process. Instantly requires an Email mapping. |
| Previous outreach | Search the relevant CRM and sending history for an existing conversation, opt-out, active opportunity, or recent send. |
| Exclusions | Confirm the address or domain is not under a client, customer, competitor, unsubscribe, or other workspace exclusion policy. |
A reviewer should approve the specific address and destination together. If either changes later, return the row to review rather than treating the old approval as reusable. This matters because Zapier's documented trigger can run on updates, not just newly created rows. Use an approval transition as the Zap's trigger column or filter only if your connected Zapier interface supports the exact behavior you need; test whether a later unrelated edit re-fires the action. Do not assume a “processed” column alone makes an action idempotent.
Configure the Zap for one campaign
- Create the target Instantly campaign and inspect its audience, sender accounts, sequence, schedule, and status. The pre-launch checklist says a campaign needs leads and active assigned sending accounts before it sends. Decide who owns final launch approval.
- In Instantly Integrations, find Zapier and copy its API key. Connect the account in Zapier; keep the key in the connector, never in a Sheet cell or report.
- Choose Google Sheets New or Updated Spreadsheet Row, select the spreadsheet, worksheet, and trigger column, and test with a controlled row. Configure a Zapier filter so only an explicitly approved row for this campaign continues. The filter and approval fields are your workflow design; confirm their names and available operators in your own Zap.
- Add Instantly Add lead to campaign and select the one approved campaign. Instantly's recipe lets you choose whether to skip leads already in other campaigns. Keep that enabled for a conservative pilot. It also presents a launch campaign after adding leads choice; leave automatic launch off until the owner has reviewed the campaign, unless your organization has an approved launch process.
- Map Email and only needed personalization fields. Instantly says Email is mandatory and custom variables must match the intended column names. Check a sample row for blanks, stale company names, and accidental private notes before publishing.
- Test the action, inspect the target campaign's Leads list, then publish the Zap. Instantly notes that Zapier may report success even when a lead was skipped because it already exists elsewhere. Reconcile the actual campaign row rather than treating a green Zap run as proof of import.
Duplicates and suppression are different controls
The skip leads already in other campaigns choice is a duplicate safeguard. It does not replace an opt-out policy or prove a person is appropriate to contact. Instantly's global blocklist guide says addresses and domains in the Blocklist tab are checked at import and during ongoing campaigns; entries in its separate Google Sheets blocklist are checked only on import or upload. Maintain the Blocklist tab for exclusions that must stop an already active lead, and verify how your Zap action handles a blocked test address. Do not remove a legitimate opt-out to make an import succeed.
A repeated approval edit may re-trigger the Zap. During the pilot, test a row already in the target campaign, a row in another campaign, and a blocked address. Record the Zap outcome, the Instantly lead state, and the reason for a skip. If the connector's behavior for same-campaign duplicates is unclear, hold those rows for manual review rather than declaring them safe because the action returned success.
Reconcile the intake queue
At the end of each review cycle, compare approved Sheet rows with Instantly leads in the selected campaign. Separate added, skipped duplicate, blocked, invalid or missing email, and Zap failure. Instantly's upload troubleshooting lists duplicates, malformed addresses, blocklisted entries, formatting, and whitespace as reasons a lead may not appear. Fix the source row or exclusion decision, then retry deliberately; do not create a second row just to force a send.
If the campaign sends nothing after an approved import, confirm the lead is actually present and follow the campaign-not-sending guide. For opt-outs, use the Instantly unsubscribe guide. OutboundXYZ has a commercial relationship with Instantly; the Instantly.ai review covers the wider product choice. This guide reports documented connector behavior and a proposed control process, not a private integration test.
FAQ
Can I point one Zap at several campaigns from a Sheet column?
The documented recipe tells you to select a campaign in the action. Build and test a separate approved route for each target or another verified mapping design; do not assume a free-text Sheet value chooses a campaign safely.
Does a successful Zap run prove the lead was added?
No. Instantly warns that a success result can accompany a skip when the lead already exists in another campaign. Check the target Leads list.
Does a Google Sheets blocklist stop leads already in active campaigns?
Instantly says no. Its Blocklist tab applies to active campaigns; its Google Sheets blocklist is checked on import or upload.
