New accounts get 1,000 free credits.Start for free →

GitHubSign up
Gist logo

Integration

Verify your Gist audience before you send

Gist combines contacts, live chat, and automation triggers on one record, so a bad import can start outbound sequences immediately after upload. Exporting contacts, verifying them with Bounceless, and re-importing only send-decision rows catches invalid addresses before they match live campaign criteria or enter automated email flows.

Start for freeQuickstart

How it works

[01]Export your Gist contactsOn the Contacts page, filter or segment the audience you want to check. Use Gist bulk operations (requires Bulk Operations permission on your role) to export the selection. Gist also supports JSON export through its REST API for larger portability requests documented in its GDPR help article.
[02]Verify the export in BouncelessUpload the exported CSV to Bounceless and run a bulk verification job. Each address receives a confidence level, reason codes, and a Pre-Send Decision before you re-import anything into Gist.
[03]Download the verified resultsWhen the job completes, download the results and keep only send-decision and review-decision rows for re-import. Exclude suppress-decision addresses so they do not re-enter automations after upload.
[04]Re-import the clean contactsIn Gist, open Contacts, click More > Import contacts, upload the verified CSV (under 10 MB and 10,000 rows per file), map columns to Gist properties, confirm you have permission to email the contacts, and click Start Import. Check Only update existing contacts if you are refreshing an existing segment.

Steps are sourced from Gist's official documentation (reference) and have not yet been walked on a live Gist account by a Bounceless team member — treat exact menu labels as indicative until this note is removed.

When to run it

Before enabling a live automationGist warns that imported contacts immediately match live campaigns and automations. Verify a CSV before import so invalid addresses do not trigger outbound emails the moment Start Import finishes.
Segment export and refreshFilter contacts by owner, tag, or property, export the segment, verify it in Bounceless, and re-import with Only update existing contacts checked to refresh deliverability without duplicating records.
ESP migration into GistGist import docs assume a header row with Email Address plus optional properties. Verify the migration file in Bounceless first, split files larger than 10,000 rows, then import each cleaned batch separately.

Common questions

Does Gist require an email address on every imported row?

Yes. Gist import documentation states that Email Address is the only required property for each contact. Bounceless verification aligns with that constraint: every row in your export should contain one mappable email column before you upload to either system, and malformed addresses should be fixed or dropped before re-import.

What are Gist import file limits?

Gist caps CSV imports at 10,000 rows and 10 MB per file. If your export is larger, split it after verification and import multiple batches. Bounceless bulk jobs can process the full export first so you split only the cleaned send-decision rows Gist will actually accept per upload.

Do I need API access to export from Gist?

Not necessarily. Gist documents bulk export through Contacts permissions and JSON export via REST API for data-portability requests. This guide assumes a CSV export path marketing teams can run without writing code, though teams with API access can produce the same file programmatically if bulk UI export is unavailable on their role.

[ 06 / 06 ]GET STARTED
[ SEND ]

Spot risky contacts before your next send, not after

Test your list on 1,000 free credits: no card, no commitment, same engine as the playground above.

Start for freeTalk to us