Skip to main content

Wiza Salesforce Integration — Everything You Need to Know

A complete guide to the Wiza + Salesforce integration: setup, key settings, sync experience, troubleshooting, and FAQ.

Written by Justyn

What Wiza + Salesforce Does

Wiza can send people from your lists into Salesforce as either Leads or Contacts, and it supports account/contact association behavior based on your settings.

You connect Salesforce from the Integrate page and can set it as your Primary sync destination. Users can sync from both list-level and person-level workflows, and view a clear sync report showing what was created, updated, skipped, or errored.

If the connection breaks, Wiza surfaces a Broken state with a dedicated Fix now path. Admins can also lock integration management to admins only, while still allowing users to repair broken integrations.


How to Set It Up

  1. Go to Integrate and click Connect on Salesforce

  2. Complete the Salesforce login and authorization flow

  3. Click Configure on the Salesforce card to open field mapping and settings

  4. Choose your Primary object type (where new records go — typically Contact or Lead)

  5. Choose your Object types to update (where Wiza looks for existing matches before creating new records)

  6. Configure account/contact association behavior and overwrite logic

  7. Save settings and start syncing from lists or individual contacts

A View setup guide link is also available directly on the Salesforce integration card in the UI.


Key Settings Users Should Know

  • Primary object type — controls where new records are created in Salesforce

  • Object types to update (Salesforce-specific) — controls where Wiza looks for existing matches to update before creating new records

  • Update regardless of ownership — lets updates happen even if records are owned by other Salesforce users (subject to Salesforce permissions)

  • Account configuration — toggle create/update behavior for account records

  • Contact configuration — toggle contact-account association and whether to override existing associations

  • Apply settings to all users — admins and managers can enforce one mapping and settings standard for the whole account


Day-to-Day Sync Experience

List-level sync:

  • Users choose a segment to sync: Valid Emails, Valid + Risky, Found Phones, or All (depending on list type)

  • Sync summary is shown in plain language: "X created, Y updated, Z errors"

  • Users can open detailed sync reports showing categories: created, updated, skipped, duplicate, and errors

Person-level sync (individual contacts):

  • Add as Contact or Lead in Salesforce

  • Link to an existing Salesforce record

  • Unlink and relink if the match was wrong

  • Open the Salesforce record directly from Wiza

LinkedIn extension sync: Users can also configure Salesforce field mapping directly from the extension's "Configure Fields" experience, including choosing, reordering, and resetting fields.


Recent User-Visible Updates

  • Integration access control — admins can restrict who is allowed to manage integrations at the account level

  • "Broken" integration recovery — dedicated Fix now action when a connection needs to be repaired

  • Salesforce-specific "Object types to update" control in settings — gives users more precise control over matching behavior

  • Improved sync reporting — multi-category summary lines with clearer status labels

  • Sequencing support in sync flows — reconnect prompts appear if required sequencing permissions are missing


Support Troubleshooting Checklist

1) Confirm connection health

  • Is Salesforce shown as connected and not broken?

  • If showing as Broken, click Fix now and reconnect

2) Confirm user permissions

  • Is integration management restricted to admins only on this account?

  • If yes, ensure the user has admin access or involve an admin to configure the integration

3) Confirm Salesforce is set as Primary (if expected)

  • If sync seems to be going elsewhere, check the Primary toggle on the Integrations page

4) Confirm mapping and settings are saved

  • Open Configure and verify: object type, update behavior, overwrite logic, and account/contact configuration

5) Confirm the expected sync segment

  • If records are "missing," verify the sync segment choice — Valid only vs. Valid + Risky vs. Found Phones vs. All

6) Check record ownership and overwrite expectations

  • If updates didn't apply, verify that "Update existing contacts regardless of ownership" is enabled

  • Also verify the overwrite field choices in settings

7) Check for Salesforce-side restrictions

  • If some fields stay blank or updates fail, confirm Salesforce field-level permissions, validation rules, and picklist values on the Salesforce side

8) Review sync report details

  • Open the sync task details and read the category counts and error lines for specific failure reasons

9) For person-level issues

  • Use Link to existing record if the record matching was wrong

  • Use Unlink Contact then resync if needed

10) For sequencing users

  • If "Add to Sequence/Cadence" is unavailable, reconnect the sequencing integration to restore required permissions

11) If still failing — escalate with:

  • List/contact ID

  • Screenshot of sync report error message

  • Selected sync segment

  • Screenshot of current mapping and settings


FAQ

Q: Can Wiza send to Salesforce as a Lead or a Contact?
A: Yes — users choose the object behavior in settings. Salesforce has specific update-object controls that determine where records go.

Q: Why did nothing sync?
A: Most common causes are: no primary integration selected, the integration is disconnected or broken, or there are no eligible rows in the selected sync segment.

Q: Why were some records skipped?
A: Usually due to duplicates, no new data to update, ownership constraints, or Salesforce permission/validation rule limitations.

Q: Why are fields blank in Salesforce after sync?
A: Often caused by unmapped fields, Salesforce field-level permission restrictions, validation or picklist mismatches, or the source value simply being unavailable.

Q: Can non-admin users manage the Salesforce integration?
A: It depends on the account setting. Admins can restrict integration management to admins only.

Q: What does "Broken" mean on the integration card?
A: The connection is no longer valid and needs to be repaired. Click Fix now to reconnect.

Q: Can we standardize one field mapping for the whole team?
A: Yes — admins and managers can apply integration settings and field mappings to all users from the Salesforce configuration page.

Q: Can users sync individual contacts from inside Wiza?
A: Yes — they can sync, resync, and open the Salesforce record directly from any individual contact in Wiza.

Q: Can users link to an existing Salesforce record instead of creating a new one?
A: Yes — there is a "Link to existing record" flow available at the person level.

Q: Why does "Add to Sequence/Cadence" prompt a reconnect?
A: The required sequencing permissions are missing on the connected integration. Reconnecting will restore them.


💡 Best positioning for customers: "The Wiza + Salesforce integration lets you send enriched contacts directly into Salesforce as Leads or Contacts, update existing records automatically, and open any Salesforce record from inside Wiza — all with full control over field mapping and sync rules."

Did this answer your question?