RocketVerifier
Docs/Integrations/Salesforce
☁️

Salesforce Integration

Beta

Native connector

Verify Salesforce Leads and Contacts and write the result into custom fields on both objects.

Connect Salesforce

Dashboard → Integrations → Salesforce

Dashboard

Bounce guarantee

Connect your sending provider and bounced "deliverable" addresses are refunded automatically

How it works

Connect with

OAuth

Category

CRM

Write-back

Fields

Auto-verify new

No

How to Connect

1

In RocketVerifier open Dashboard → Integrations → Salesforce and click Connect. You are sent to Salesforce to approve access, then back to the dashboard. Sandboxes and My Domain logins are supported.

2

Create the four custom fields below on both Lead and Contact before the first write-back.

3

Pick the source to sync, the schedule and the write-back options in the integration settings, then click Sync now or wait for the schedule.

Tokens are stored encrypted and, where the platform issues expiring tokens, refreshed automatically. If access is revoked the integration is marked as needing re-authorization; reconnect it from the dashboard.

What It Syncs

Sources

All Leads, All Contacts, all Leads and Contacts, any Lead or Contact list view, and active campaigns (their Lead and Contact members).

Incremental syncs

Records with LastModifiedDate after the last sync.

Schedules & Credits

  • Schedule: Manual only, Daily, Weekly or Monthly. Each run syncs the source chosen in the settings; Sync now starts one immediately. Only one sync runs per integration at a time.
  • Mode: Full re-checks every contact in the source except those verified in the last N days (default 30, 0-365); Incremental only checks contacts changed since the last sync.
  • Each sync creates a regular verification job: 1 credit per unique address, and unknown results are refunded when it completes. If the balance is too low the sync stops with insufficient_credits before anything is charged.
  • Results are written back when the job completes; the sync history in the dashboard shows updated, failed and skipped counts per run.

Write-back

Fields ("Write status fields")

  • RV_Email_Status__c (Text 40)
  • RV_Email_Sub_Status__c (Text 80)
  • RV_Email_Score__c (Number 3,0)
  • RV_Verified_At__c (Date/Time)

Written 200 records at a time with per-record results. Missing fields are reported by name instead of failing the whole run; map other field names in the integration settings if you already have them.

Status values are deliverable, undeliverable, risky and unknown (disposable addresses are undeliverable, catch-all addresses unknown). Sub-status is a sub_status value (none when there is no extra detail), score is 0-100 and verified-at is an ISO 8601 UTC timestamp.

Action Rules

In the integration settings, pick an action per result: Invalid, Disposable, Risky, Catch-all, Unknown or Valid. Actions run after the field/tag write-back.

Unsubscribe

Sets the standard HasOptedOutOfEmail field to true.

Beta: the Salesforce connector is new. Sync reports list every contact that could not be updated; please tell us if something looks wrong.

The custom fields must exist on both Lead and Contact (create them in Setup → Object Manager).

Need Help?

Having trouble connecting Salesforce? We're here to help.

Contact SupportAll Integrations