Skip to content

EXPLORE SYNCAPPS FEATURES

Powerful features.
Simpler workflows.

Everything you need to connect your CRM, marketing, and business apps. From two-way data syncing and custom field mapping to audience segmentation and automation, SyncApps keeps your data flowing and your teams moving.

Your apps, connected through SyncApps SyncApps adds Salesforce leads to Mailchimp, syncs NetSuite customers to Constant Contact, organizes CRM contacts into marketing tags, updates email unsubscribes in CRM, and returns campaign opens and clicks to CRM. Salesforce NetSuite Mailchimp Constant Contact ActiveCampaign New Salesforce LeadsAdded to Mailchimp NetSuite CustomersSynced to Constant Contact CRM Contacts Organizedinto Marketing Tags Email UnsubscribesUpdated in CRM Campaign Opens & ClicksSent Back to CRM

FEATURES BY WORKFLOW

What needs to move
between your apps?

Features vary by integration, account plan, enabled options, and connected app permissions. Check your app's details below or talk with our team about your workflow.

Keep customer records aligned.

Connect your apps and match the people already in them.

Application integration

Connects supported business applications through configurable Set Ups.

Use case

Connect a CRM with a marketing application without building a custom connector.

Record synchronization

Creates and updates supported contacts, leads, customers, accounts, and other records between connected applications.

Use case

Keep customer details current across sales and marketing systems.

One-way and two-way synchronization

Controls supported record flows and update priority between applications. Some response and subscription flows have separate controls.

Use case

Send customer records to marketing while receiving selected profile updates back.

Record matching

Uses supported email addresses, external IDs, or connector-specific identifiers to associate records across applications.

Use case

Update an existing customer instead of creating another record for the same person.

Build audiences from your data.

Map the details you need. Choose who belongs in each audience.

Field mapping and transformation

Maps standard and custom fields, translates values, and supports eligible static values and expressions.

Use case

Convert source classifications into the destination's expected field values.

Data filtering

Selects records using configured field conditions, source lists, campaigns, or saved searches.

Use case

Sync only active customers in a selected region.

Audience segmentation

Maintains supported lists, groups, or tags based on source membership and field values.

Use case

Build separate audiences for different product interests.

Keep preferences in step.

Carry subscription changes and record updates into your connected apps.

Subscription preference synchronization

Transfers supported opt-out and resubscription states using standard or eligible custom fields.

Use case

Reflect a newsletter unsubscribe in the connected customer record.

Record lifecycle handling

Applies supported email change, deletion, archival, conversion, and inactive record behavior.

Use case

Keep destination records aligned after CRM cleanup.

Set the pace. See the results.

Choose when to sync, reconcile membership, and check each run.

Scheduled and manual synchronization

Runs eligible integrations on recurring schedules or starts a sync on demand.

Use case

Refresh records overnight and run an extra sync after correcting data.

Full Sync reconciliation

Rechecks supported membership against the source and applies configured cleanup rules.

Use case

Remove stale audience membership after source criteria change.

Webhook updates

Receives supported application events to process selected profile or email activity changes.

Use case

Reflect a subscriber profile edit without waiting for scheduled retrieval.

Sync monitoring and troubleshooting

Provides run history, progress, record outcomes, error details, downloadable logs, and supported notifications.

Use case

Find rejected records and investigate a failed sync.

Connect the work around your customers.

Bring campaign activity, events, sales, support, and training into supported workflows.

Campaign engagement reporting

Returns supported marketing responses, including opens, clicks, bounces, and clicked links.

Use case

Let sales staff review a prospect's email engagement in CRM.

Historical data retrieval

Uses supported start dates and campaign history options to retrieve earlier data.

Use case

Import historical campaign responses into a newly connected system.

Event and registration integration

Transfers supported event, registrant, registration status, and custom question data.

Use case

Track event signups and attendee preferences in CRM.

Lead capture

Imports supported lead form submissions and maps their answers into destination fields.

Use case

Send advertising signups into the sales follow-up process.

Commerce and sales data integration

Transfers supported customer, product, opportunity, or commerce data through eligible integration pairs.

Use case

Give sales and marketing teams access to relevant ERP data.

Support ticket and case integration

Exchanges supported tickets, cases, comments, customer details, and time tracking.

Use case

Connect the support team's ticket workflow with ERP case records.

Learning user provisioning

Creates and updates supported learner accounts, profile fields, and active status.

Use case

Maintain training accounts from employee records managed in CRM.

Find the features for your apps.

Open an application to explore its features and example workflows. Supported records, sync direction, and available options depend on the integration pair.

Salesforce

32 features

Connects with Constant Contact, Mailchimp, Act-On, Relias Learning, TalentLMS, MIR3, Klaviyo, ActiveCampaign, Brevo, Infusionsoft, Mandrill, Eventbrite, NetSuite, Facebook.

Contact, lead, and account sync

Selects the Salesforce record type to send to a supported marketing application. Person Account handling is available where configured.

Use case

Send customer contacts and prospect leads through separate Set Ups.

New subscriber record type

Chooses the Salesforce object to create for new subscribers received from the marketing application.

Use case

Create new newsletter subscribers as leads.

Campaign member sync

Uses Salesforce Campaign membership to populate marketing lists, groups, or tags.

Use case

Build an email audience from a product launch Campaign.

List View sync

Uses selected Salesforce List Views as the source of records and segments.

Use case

Send only contacts in a regional sales List View to marketing.

Marketing List sync

Supports Salesforce marketing lists where the required list functionality is configured.

Use case

Let sales manage membership in Salesforce.

Campaign selection rules

Selects Campaigns and limits them by creation date, record type, or Campaign Member status.

Use case

Sync only active Campaigns with approved member statuses.

Checkbox segmentation

Turns configured Salesforce checkbox fields into marketing segment membership.

Use case

Maintain a separate audience for each checked product interest.

Multi-select picklist segmentation

Uses selected values in a multi-select field to assign marketing groups or tags where supported.

Use case

Add a contact to several interest groups from one Salesforce field.

Campaign response sync

Returns supported campaign engagement metrics to Salesforce.

Use case

Show email engagement beside the lead record.

Campaign and activity response modes

Controls whether responses create campaign records, activities, or the supported combination.

Use case

Give managers campaign reporting and sales representatives activity history.

Response event selection

Limits response processing to opens and clicks, bounces, or other supported event selections.

Use case

Record bounces without importing every send event.

Clicked URL reporting

Includes clicked links in campaign response details.

Use case

Identify contacts who clicked a pricing page.

Send event tasks

Creates Salesforce tasks for supported email send events.

Use case

Keep a record of which campaign messages a lead received.

Completed activity status

Creates campaign response tasks with a completed status.

Use case

Keep historical email activity out of the open task queue.

Responses on all matching records

Can attach campaign responses to all Salesforce records with the same email address.

Use case

Record engagement on duplicate contact records used by separate teams.

Salesforce Files for response data

Uses Salesforce Files instead of older attachments for supported response output.

Use case

Make response files available through Salesforce Lightning.

Opportunity field mapping to Mailchimp

Exposes supported Opportunity fields for mapping through the primary contact relationship.

Use case

Segment primary contacts using opportunity data.

Event and registrant sync

Creates campaign-related event data and maps registrants, statuses, and supported custom questions.

Use case

Track Eventbrite registrations in Salesforce Campaigns.

CRM opt-out propagation

Unsubscribes or removes marketing records when configured Salesforce opt-out fields change.

Use case

Apply a sales representative's opt-out update to the marketing audience.

Resubscription handling

Clears the configured Salesforce opt-out flag when a supported marketing resubscription occurs.

Use case

Reflect a returning subscriber's changed status in Salesforce.

Source deletion handling

Propagates supported Salesforce record deletions to the marketing destination when enabled.

Use case

Remove marketing records associated with deleted CRM contacts.

Converted lead cleanup

Removes previously synced leads after conversion, with controls for the main list and prior lead records.

Use case

Avoid leaving old lead entries alongside converted contacts.

Blank email cleanup

Removes a previously synced marketing record when its Salesforce email becomes blank, if enabled.

Use case

Stop retaining an address removed from the CRM record.

Email change handling

Offers supported update or recreate behavior when the source email address changes.

Use case

Update a Mailchimp or Constant Contact address while retaining supported history.

Alternate email matching

Checks configured additional email fields before creating or updating a Salesforce record.

Use case

Match a subscriber's work email to an existing contact.

Same-object matching

Can limit duplicate matching to the selected Salesforce object type.

Use case

Create a lead even when a contact already uses that email address.

Account creation control

Controls whether a missing company creates a new Salesforce Account.

Use case

Keep company creation under the CRM administrator's control.

Missing name fallback

Can supply "Unknown" for missing required first or last names.

Use case

Import a subscriber whose form collected only an email address.

Namespace support

Accepts a configured namespace for supported packaged fields and objects.

Use case

Map fields belonging to a Salesforce package.

NetSuite customer, item, and opportunity integration

Uses a dedicated process with separate customer, item, and opportunity sync mode controls.

Use case

Keep Salesforce sales data connected to NetSuite customer and product records.

Learner provisioning integrations

Sends selected Salesforce student records to Relias Learning or TalentLMS through dedicated processes.

Use case

Maintain training users from Salesforce-managed employee records.

Facebook lead import

Receives leads from a selected Facebook Page and form.

Use case

Send advertising form submissions into the Salesforce sales workflow.

NetSuite

23 features

Connects with Constant Contact, Mailchimp, iContact, Nimble, HubSpot, Klaviyo, Brevo, Mandrill, ActiveCampaign, Salesforce, Zendesk.

Customer and contact sync

Sends selected NetSuite entity records to a supported destination.

Use case

Build a customer newsletter list from NetSuite.

Saved Search selection

Uses configured NetSuite Saved Searches to select records and supply segmentation.

Use case

Send only customers returned by an approved Saved Search.

Subscription-based selection

Uses a named NetSuite subscription to select the people to sync.

Use case

Maintain a marketing audience for one subscription category.

Subscription-specific unsubscribe

Updates selected subscription statuses instead of the Global Subscription Status when configured.

Use case

Record a newsletter unsubscribe without changing unrelated subscriptions.

Checkbox segmentation

Uses configured NetSuite checkbox fields to determine marketing membership.

Use case

Assign contacts to product-interest lists.

Campaign response sync

Writes supported marketing campaign engagement back to NetSuite.

Use case

Let account managers see customer email engagement.

Email subject in responses

Includes the email subject in supported campaign response output.

Use case

Identify which message generated a response.

Empty-response campaign creation

Can create a campaign record even when no engagement responses exist.

Use case

Retain campaign coverage before recipients engage.

Opt-out propagation

Applies configured NetSuite opt-out statuses to the marketing destination.

Use case

Stop sending to customers marked opted out in NetSuite.

Inactive record handling

Can remove or unsubscribe inactive customers and contacts from the destination.

Use case

Exclude inactive accounts from an ongoing email program.

Source deletion sync

Propagates supported NetSuite customer or contact deletions when enabled.

Use case

Remove destination records after NetSuite cleanup.

Resubscription and soft opt-in

Can clear opt-out state or apply supported soft opt-in status based on marketing subscription state.

Use case

Reflect a customer's subscription change in NetSuite.

New subscriber entity type

Selects the NetSuite entity type for new marketing subscribers.

Use case

Create inbound subscribers as leads rather than customers.

Parent customer assignment

Creates new customers under a configured parent customer.

Use case

Group newly created branch customers under their corporate parent.

Company versus individual creation

Can create customers or leads as companies when a company name is present.

Use case

Keep business subscribers in company-style NetSuite records.

Email as entity ID

Can use an email address as the entity ID for a new customer or contact.

Use case

Apply an email-based naming convention to inbound records.

OneWorld subsidiary default

Assigns a configured default subsidiary to new records.

Use case

Create subscribers in the correct OneWorld subsidiary.

NetSuite custom field mapping

Maps supported custom record fields, including configured Center Sales Rep fields.

Use case

Send business-specific account attributes to marketing.

Character compatibility option

Can remove unsupported UTF-16 characters from supported payloads.

Use case

Prevent rejected records caused by incompatible characters.

Salesforce customer sync modes

Controls the customer flow used by the NetSuite and Salesforce integration.

Use case

Maintain customer details across sales and ERP systems.

Salesforce item and opportunity sync modes

Separately configures product/item and opportunity synchronization.

Use case

Keep sales teams' product and opportunity information aligned with NetSuite.

Nimble contact integration

Uses a dedicated contact integration with Nimble.

Use case

Give relationship managers access to NetSuite contact information.

Zendesk support case integration

Exchanges supported ticket, case, customer, and contact data with Zendesk.

Use case

Connect support operations to NetSuite customer records.

Constant Contact

21 features

Connects with Salesforce, NetSuite, Navatar, Propertybase, Apto, Agentforce Nonprofit, Nonprofit Accelerator, Salesforce Nonprofit Success Pack.

Main List sync

Creates or uses a named Main List for the Set Up.

Use case

Keep an integration's subscribers in a designated list.

CRM segment to list sync

Creates or matches Constant Contact lists from supported source segments.

Use case

Mirror Salesforce Campaigns or NetSuite Saved Searches as email lists.

Selected lists back to CRM

Retrieves subscribers from selected Constant Contact lists.

Use case

Bring subscribers from several signup lists into CRM.

All active contacts retrieval

Can retrieve active contacts beyond the specified Main List.

Use case

Import contacts maintained across the account.

Campaign recipient import

Can include campaign recipients outside the Main List.

Use case

Create missing CRM records for campaign recipients.

Two-way list membership

Can send supported list membership changes back to the connected CRM.

Use case

Reflect a subscriber's list membership in the matching CRM list.

Campaign response selection

Selects supported campaigns for response synchronization.

Use case

Report on a chosen campaign rather than every campaign.

Unique open reporting

Can retrieve unique opens for response reporting.

Use case

Focus reporting on recipients who opened a message.

Field update precedence

Offers supported source-priority choices for contact updates.

Use case

Keep the CRM authoritative for shared contact fields.

One-way contact sync

Prevents Constant Contact contact creation in the source system while preserving separately configured metrics and unsubscribe flows.

Use case

Keep subscriber creation in CRM while receiving campaign results.

Unsubscribe status sync

Updates the connected system when Constant Contact contacts unsubscribe, with an option to suppress that flow.

Use case

Show marketing opt-outs in the CRM record.

Full Sync list cleanup

Reconciles list membership and optionally removes records that no longer belong to the Set Up. Some removal options affect all lists.

Use case

Remove contacts who no longer meet the source Campaign criteria.

Role email filtering control

Controls whether supported role-based email addresses are filtered.

Use case

Include an approved shared departmental email address.

State name conversion

Can retrieve state names instead of abbreviations.

Use case

Populate CRM fields that expect full state names.

Address and company sync controls

Separately controls physical address and company name updates.

Use case

Maintain destination addresses manually while syncing other fields.

Phone country formatting

Formats valid local phone numbers using a selected default country.

Use case

Send local telephone numbers in a consistent format.

Default phone mapping

Can copy Work Phone into the default phone field.

Use case

Populate destinations that rely on the default phone field.

Typed address mapping

Enables supported Home, Work, and Other address mappings.

Use case

Keep personal and business addresses in the correct fields.

SMS phone synchronization

Syncs the supported mobile phone field as the Constant Contact SMS phone number.

Use case

Make a CRM mobile number available to the SMS workflow.

Explicit SMS consent mapping

Can leave consent unset or use a configured source consent field.

Use case

Transfer an explicit source SMS consent value with the number.

SMS consent date mapping

Uses a configured consent date field or record modified date according to the selected mode.

Use case

Send the source consent date alongside the consent status.

Mailchimp

17 features

Connects with Salesforce, NetSuite, Navatar, Propertybase, Apto, Agentforce Nonprofit, Nonprofit Accelerator, Salesforce Nonprofit Success Pack.

Main Audience sync

Uses a selected existing Mailchimp Audience for record creation and updates.

Use case

Keep CRM subscribers in the correct audience.

Group or tag segmentation

Creates supported groups or tags from source lists, campaigns, or filtering segments.

Use case

Target subscribers by Salesforce Campaign membership.

Multiple Group Categories

Supports multiple group categories when the option is available.

Use case

Maintain separate product-interest and regional categories.

Group category naming

Sets the group category used by the integration.

Use case

Keep integration-created groups under a recognizable category.

Obsolete group cleanup

Removes groups that no longer correspond to supported active source segments.

Use case

Retire groups left behind by closed Campaigns.

Full Sync audience reconciliation

Reconciles audience membership against the source criteria.

Use case

Remove subscribers who no longer qualify for the Set Up.

Deletion method selection

Controls supported archive or deletion behavior during cleanup.

Use case

Choose the required cleanup behavior for records leaving the integration.

Tag-based deletion protection

Protects qualifying contacts from cleanup when they have existing Mailchimp tags.

Use case

Preserve tagged contacts managed by another marketing process.

Archived contact restoration

Can add archived records back while treating unsubscribed and deleted records separately.

Use case

Restore an archived CRM contact who remains eligible for sync.

Double opt-in

Enables Mailchimp's supported double opt-in behavior.

Use case

Require confirmation for newly synced subscribers.

Unsubscribe status sync

Returns unsubscribe state to the source, with a control to suppress it.

Use case

Update the CRM opt-out field after a Mailchimp unsubscribe.

Subscriber profile webhooks

Uses Mailchimp webhooks to send supported contact profile changes back to the source.

Use case

Update CRM profile fields after a subscriber edits their details.

Administrator profile updates

Can include contact profile edits performed by a Mailchimp administrator.

Use case

Reflect corrections made by the marketing operations team in CRM.

Existing subscriber refresh

Can update existing source records when a new subscription occurs.

Use case

Recheck membership when a known contact subscribes again.

eCommerce data sync

Sends supported commerce data with configured store name and currency.

Use case

Make supported NetSuite commerce information available in Mailchimp.

One-way subscriber control

Prevents Mailchimp subscribers from creating records in the source system.

Use case

Keep new CRM record creation controlled by the sales team.

Campaign selection and responses

Selects campaigns and returns supported engagement data to the source.

Use case

Give account managers visibility into email activity.

ActiveCampaign

9 features

Connects with Salesforce, NetSuite, Agentforce Nonprofit, Nonprofit Accelerator.

List and tag segmentation

Creates supported lists, tags, or both from source segmentation.

Use case

Group contacts by CRM Campaign or NetSuite Saved Search.

Default target list

Selects a default destination list, or permits contacts without a default list selection.

Use case

Put inbound CRM contacts into the right subscription list.

Selected list retrieval

Limits records received from ActiveCampaign to selected lists.

Use case

Bring back only contacts in a designated signup list.

One-way subscriber control

Prevents subscribers from creating source records while preserving separately configured response and unsubscribe flows.

Use case

Use CRM as the source of new records.

Profile update synchronization

Sends supported subscriber profile changes back to the source.

Use case

Keep CRM contact details aligned with subscriber edits.

Administrator update handling

Can include profile updates made by ActiveCampaign administrators.

Use case

Transfer marketing team's contact corrections to CRM.

Unsubscribe status sync

Returns unsubscribed state to the source unless disabled.

Use case

Keep the source opt-out field current.

Campaign engagement sync

Returns supported campaign responses to the connected source.

Use case

Make opens, clicks, and bounces available to account managers.

NetSuite list-box field mapping

Supports eligible NetSuite and ActiveCampaign list-box mapping combinations.

Use case

Transfer values between supported selection fields.

HubSpot

5 features

Connects with NetSuite.

Contact sync and precedence

Synchronizes supported contact data with a chosen update priority. The configuration notes that the sync mode cannot be changed within an existing Set Up.

Use case

Keep NetSuite authoritative for shared contact details.

Selected HubSpot lists

Restricts records retrieved from HubSpot to selected lists.

Use case

Create NetSuite records only for a designated HubSpot audience.

One-way contact control

Prevents HubSpot contacts from creating NetSuite records.

Use case

Send ERP contacts into HubSpot without importing new contacts back.

Form and UI profile updates

Sends supported updates made through HubSpot forms or its UI back to NetSuite.

Use case

Reflect a subscriber's updated details in ERP.

Unsubscribe status sync

Returns supported unsubscribe state unless disabled.

Use case

Keep subscription state visible in NetSuite.

Klaviyo

8 features

Connects with Salesforce, NetSuite.

Main List synchronization

Creates or uses a named Klaviyo list for the integration.

Use case

Maintain an audience for ERP customers.

Source segment membership

Uses supported source segments to maintain destination list membership.

Use case

Target a subset of Salesforce contacts.

One-way contact control

Prevents Klaviyo contacts from creating source records.

Use case

Keep CRM in control of new contact creation.

All active contact retrieval

Can retrieve active contacts beyond the Main List.

Use case

Import existing Klaviyo contacts into the source system.

Profile change events

Can create an event whenever a person is created or updated by the integration.

Use case

Trigger a Klaviyo flow after a synced profile change.

Campaign response selection

Selects supported campaigns for response sync.

Use case

Report campaign activity in Salesforce or NetSuite.

Unsubscribe status sync

Returns unsubscribe state unless disabled.

Use case

Reflect a Klaviyo opt-out in CRM.

Full Sync cleanup

Reconciles source membership and optionally removes contacts beyond the integration's lists.

Use case

Remove contacts who no longer qualify for a segment.

Brevo

4 features

Connects with Salesforce, NetSuite.

Main List contact sync

Synchronizes supported source contacts into a configured Brevo Main List.

Use case

Maintain a Brevo audience from Salesforce or NetSuite.

One-way subscriber control

Can prevent Brevo subscribers from creating source records.

Use case

Keep source record creation under the CRM team's control.

Unsubscribe status sync

Returns supported unsubscribe state unless disabled.

Use case

Keep CRM opt-out status aligned with Brevo.

Contact field mapping

Maps supported source and Brevo contact fields.

Use case

Send customer attributes required for campaign personalization.

Act-On

4 features

Connects with Salesforce.

Main List synchronization

Creates or uses a configured Act-On Marketing or Signup List.

Use case

Send Salesforce contacts into a marketing audience.

One-way contact control

Prevents Act-On contacts from creating Salesforce records.

Use case

Keep sales responsible for CRM record creation.

Unsubscribe synchronization

Sends supported opt-out state back to Salesforce unless disabled.

Use case

Update the Salesforce opt-out field after an unsubscribe.

Campaign selection and response sync

Selects supported campaigns and returns engagement responses.

Use case

Show Act-On engagement in Salesforce campaign history.

iContact

4 features

Connects with NetSuite.

Main List synchronization

Creates or uses a named list for NetSuite records.

Use case

Maintain a customer email list from ERP.

Main List only mode

Can suppress creation of additional segmentation lists.

Use case

Keep all synced subscribers in a single list.

One-way subscriber control

Prevents iContact subscribers from creating NetSuite records.

Use case

Keep NetSuite as the record creation source.

Do Not Contact synchronization

Returns supported Do Not Contact state unless disabled.

Use case

Reflect marketing contact restrictions in NetSuite.

Mandrill

3 features

Connects with Salesforce, NetSuite.

Transactional email response integration

Builds supported campaign response data from Mandrill message activity.

Use case

Show transactional email engagement in CRM.

Message campaign details

Includes supported message subject, sent date, and campaign identification in response records.

Use case

Identify which transactional message generated engagement.

Email event webhooks

Registers and receives supported Mandrill webhook events.

Use case

Receive email activity updates without relying only on scheduled retrieval.

Infusionsoft

5 features

Connects with Salesforce.

Contact synchronization

Exchanges supported contact data with Salesforce.

Use case

Maintain marketing contacts from CRM.

Tag-based source selection

Restricts records retrieved from Infusionsoft to configured tags.

Use case

Bring only qualified subscribers into Salesforce.

One-way contact control

Can prevent Infusionsoft contacts from creating Salesforce records.

Use case

Keep new CRM record creation controlled by sales.

Unsubscribe state sync

Returns supported opt-out state unless disabled.

Use case

Reflect an Infusionsoft unsubscribe in Salesforce.

Note synchronization

Sends supported Infusionsoft notes back to matched Salesforce records when enabled.

Use case

Give sales staff access to notes recorded in Infusionsoft.

Eventbrite

6 features

Connects with Salesforce.

Event to Campaign integration

Synchronizes supported Eventbrite events into Salesforce campaign-related records.

Use case

Manage an event's CRM follow-up through a Salesforce Campaign.

Registrant integration

Sends supported attendee and registrant details into the Salesforce event workflow.

Use case

Associate event signups with CRM contacts and leads.

Campaign Member name mapping

Maps Eventbrite registrant names to supported Campaign Member fields.

Use case

Retain attendee names in the Campaign Member record.

Registration and payment details

Maps supported event registration and payment statuses through event fields.

Use case

Identify registrants with different registration or payment states.

Custom question mapping

Exposes supported Eventbrite custom questions for mapping.

Use case

Send a registrant's session preference into Salesforce.

Separate event fields

Can use separate custom fields for event-related data.

Use case

Keep event registration fields separate from email campaign fields.

Zendesk

22 features

Connects with NetSuite.

Zendesk ticket to NetSuite case

Creates and updates supported NetSuite cases from Zendesk tickets.

Use case

Give ERP users visibility into support issues.

NetSuite case to Zendesk ticket

Sends supported NetSuite case data to Zendesk tickets.

Use case

Let the support team work on cases originating in ERP.

Create-once and reverse-update mode

Can create the initial case from Zendesk and then apply NetSuite updates to Zendesk.

Use case

Establish the case in NetSuite before using it as the update source.

Customer and contact synchronization

Links or synchronizes supported customer and contact details.

Use case

Show the correct ERP customer behind a ticket.

Organization creation

Can create a Zendesk organization for a synced contact's company.

Use case

Group ticket requesters by their NetSuite company.

Related customer field mapping

Allows eligible Zendesk field mappings to update related NetSuite customer fields.

Use case

Update a customer attribute through the connected support workflow.

Ticket tag filtering

Restricts ticket synchronization to configured tags.

Use case

Send only ERP-related tickets to NetSuite.

Brand filtering

Limits synchronization to selected Zendesk brands.

Use case

Integrate one support brand with an ERP account.

Comment synchronization

Transfers supported ticket comments, including a private comment option.

Use case

Keep internal support discussion in the connected case.

HTML comments

Can transfer supported comments as HTML instead of plain text.

Use case

Preserve comment formatting in the destination.

Time tracking sync

Sends supported Zendesk time tracking to NetSuite with a configured service item.

Use case

Record support time against the ERP case.

Ticket field defaults

Supports overriding configured priority, type, and status defaults.

Use case

Apply the destination team's case classification.

NetSuite ID acknowledgment

Can add an internal Zendesk indication that a NetSuite case was created.

Use case

Let agents confirm that a ticket reached ERP.

Requester and assignee creation controls

Controls new NetSuite entity or employee creation when matching fails.

Use case

Avoid creating ERP records for unknown ticket participants.

Blank requester handling

Can create an orphan ticket customer identity when the requester has no email.

Use case

Process a supported ticket without an email-based requester match.

Welcome email control

Can suppress welcome emails for Zendesk users created by SyncApps.

Use case

Import existing customers without sending extra welcome messages.

External ID and entity ID handling

Configures supported external ID prefixes and the NetSuite identifier shown in Zendesk notes.

Use case

Make customer references recognizable to support agents.

Field length compatibility

Can truncate supported case subject or phone values to destination limits.

Use case

Process an overlong ticket subject without a field-length rejection.

Embedded NetSuite app actions

Provides implemented NetSuite customer and transaction views through the Zendesk app.

Use case

Look up customer transactions while handling a ticket.

Customer search and creation in the app

Searches NetSuite customers and supports customer creation through the embedded app.

Use case

Find or create the customer associated with a support request.

Transaction address updates

Updates supported billing or shipping addresses through the app's NetSuite transaction workflow.

Use case

Correct the address associated with a customer order.

Return authorization option

Adds eligible RMA viewing and creation from an existing sales order.

Use case

Start a return authorization during a support conversation.

Nimble

3 features

Connects with NetSuite.

NetSuite contact integration

Uses a dedicated process to synchronize supported contact data with Nimble.

Use case

Give relationship managers access to ERP contacts.

Contact field mapping

Makes supported Nimble and source fields available to the integration.

Use case

Include the customer attributes used by relationship managers.

NetSuite financial fields

Creates a NetSuite field group with supported balance, overdue balance, days overdue, deposit, and unbilled order fields.

Use case

Give relationship managers account payment context in Nimble.

Relias Learning

4 features

Connects with Salesforce.

Learner creation and updates

Creates or updates supported Relias learner records from Salesforce student data.

Use case

Provision training accounts from Salesforce employee records.

Worker ID matching

Uses supported external or worker identifiers when matching learner records.

Use case

Match an existing learner to the correct employee.

Learner profile fields

Transfers supported profile, department, location, job, and employment date fields.

Use case

Keep training profiles aligned with employee details.

Learner active status

Applies supported active status changes from the source.

Use case

Update a learner's status when their employment status changes.

TalentLMS

4 features

Connects with Salesforce.

Training user synchronization

Creates or updates supported TalentLMS users from Salesforce student records.

Use case

Maintain training accounts from Salesforce.

Employee ID matching

Requires the configured Employee ID field for the learner integration.

Use case

Associate users with a stable employee identifier.

Custom registration field mapping

Discovers supported custom registration fields for mapping.

Use case

Transfer department, title, or location information.

User status sync

Updates supported TalentLMS active status.

Use case

Reflect source activation or deactivation in the learning account.

MIR3

3 features

Connects with Salesforce.

Recipient synchronization

Sends supported Salesforce contact data to MIR3 recipients.

Use case

Maintain notification recipients from CRM.

Recipient role and division

Uses configured recipient role and division settings.

Use case

Assign synced recipients to the intended notification division.

Inactive recipient handling

Applies supported inactive record handling during recipient updates.

Use case

Reflect source status changes in the notification directory.

Facebook

2 features

Connects with Salesforce, Salesforce Nonprofit Success Pack.

Lead submission retrieval

Imports supported submissions from a selected Facebook Page and lead form into the Salesforce destination.

Use case

Move advertising leads into the sales or nonprofit CRM workflow.

Lead form answer mapping

Maps supported lead form answers into destination fields.

Use case

Store a form's qualification answers in Salesforce fields.

Propertybase

4 features

Connects with Mailchimp, Constant Contact.

CRM contact synchronization

Synchronizes supported Propertybase contact data with the selected marketing application.

Use case

Maintain an audience of real estate prospects.

CRM-based audience segmentation

Uses available Salesforce-based Campaign, List View, or field segmentation options.

Use case

Target a selected group of property contacts.

Marketing engagement return

Uses supported campaign response options to return marketing activity.

Use case

Show a contact's response to a property email campaign.

Subscription status handling

Uses supported opt-out and resubscription behavior from the shared connector.

Use case

Keep contact subscription preferences aligned.

Apto

6 features

Connects with Mailchimp, Constant Contact.

Apto contact sync

Synchronizes supported Apto contacts through the Salesforce-based connector.

Use case

Maintain a marketing audience from brokerage contacts.

List View segmentation

Uses selected Apto List Views to control audience membership.

Use case

Send a campaign to contacts in a broker-managed List View.

Checkbox segmentation

Uses supported checkbox fields to populate marketing segments.

Use case

Group contacts by selected property interests.

Campaign response sync

Returns supported email responses using the CRM campaign and activity options.

Use case

Show which contacts engaged with a listing email.

Event mapping

Exposes supported event, registrant, and custom question options.

Use case

Associate event participation with brokerage contacts.

Subscription and record lifecycle controls

Supports configured opt-out, resubscription, email change, and deletion handling.

Use case

Keep audience membership aligned with CRM changes.

Agentforce Nonprofit

7 features

Connects with Constant Contact, Mailchimp, ActiveCampaign.

Nonprofit CRM record synchronization

Uses the configured Salesforce-based nonprofit object selections.

Use case

Maintain marketing audiences from nonprofit CRM records.

Campaign and field segmentation

Uses available nonprofit Campaign, List View, and field-based selections.

Use case

Target constituents associated with a fundraising Campaign.

Marketing campaign response sync

Returns supported campaign engagement to the nonprofit CRM.

Use case

Show outreach engagement to fundraising staff.

Alternate email matching

Checks supported personal, work, and alternate email fields.

Use case

Match a constituent who subscribes with a second email address.

Organization affiliation handling

Exposes configured organization affiliation creation options.

Use case

Associate an incoming subscriber with their organization.

Primary contact selection

Can restrict supported account-derived records to the primary contact.

Use case

Contact the designated person for an organization.

Subscription and deletion controls

Uses configured opt-out, resubscription, and record lifecycle behavior.

Use case

Keep constituent preferences aligned with marketing.

Nonprofit Accelerator

4 features

Connects with Constant Contact, Mailchimp, ActiveCampaign.

Nonprofit record synchronization

Uses supported Salesforce-based NPA record configuration.

Use case

Build an outreach audience from the nonprofit CRM.

Campaign and List View segmentation

Selects supported source groups for marketing audience membership.

Use case

Target constituents in a particular outreach Campaign.

Campaign response integration

Returns supported email engagement through CRM response options.

Use case

Give nonprofit staff access to campaign engagement.

Subscription preference handling

Uses the configured opt-out and resubscription controls.

Use case

Reflect a constituent's subscription change across the integration.

Salesforce Nonprofit Success Pack

19 features

Connects with Mailchimp, Constant Contact, Facebook.

Available marketing features depend on your Salesforce integration, enabled nonprofit options, and account eligibility.

Constituent record synchronization

Synchronizes supported contacts, leads, or account-related records through the Salesforce integration.

Use case

Build an outreach audience from constituent records.

Campaign member segmentation

Uses selected Salesforce Campaign members to maintain supported marketing lists, groups, or tags.

Use case

Target constituents assigned to a fundraising Campaign.

List View segmentation

Uses selected Salesforce List Views to determine which records belong in the audience.

Use case

Send outreach to constituents in a regional List View.

Campaign eligibility rules

Filters source Campaigns by supported record types, creation dates, and Campaign Member statuses.

Use case

Include only approved members of active fundraising Campaigns.

Checkbox segmentation

Uses supported CRM checkbox fields to assign marketing segment membership.

Use case

Separate volunteer, donor, and event interests.

Campaign engagement sync

Returns supported opens, clicks, bounces, and clicked URL details to the CRM.

Use case

Give fundraising staff visibility into constituent engagement.

Campaign and activity reporting

Uses supported Campaign and activity response modes, including completed task and send-event options.

Use case

Record outreach history alongside constituent records.

Event and registrant integration

Maps supported event registration data, Campaign Member details, and custom questions.

Use case

Track fundraising event signups and attendee preferences.

Personal, work, and alternate email matching

Checks NPSP's supported additional email fields before creating records from marketing subscribers.

Use case

Match an existing constituent who subscribes with a work email address.

Organization affiliation creation

Creates supported NPSP organization affiliations using the company name received from the connected application.

Use case

Associate a constituent with their employer or sponsoring organization.

Household account handling

Uses the nonprofit affiliation workflow to create a household account while retaining the company as an organization affiliation.

Use case

Keep a constituent's household separate from their employer relationship.

Primary contact synchronization

Can retrieve only the NPSP primary contact from an account and skip accounts without one.

Use case

Send organization-level outreach to the designated primary contact.

Account contact synchronization

Can retrieve all supported contacts associated with an account.

Use case

Include the relevant people associated with an organization.

Opt-out propagation

Applies supported native or eligible custom opt-out fields to the connected marketing audience.

Use case

Reflect a constituent's CRM subscription preference in marketing.

Resubscription handling

Clears the configured CRM opt-out field after a supported marketing resubscription.

Use case

Reflect a constituent's renewed subscription in the CRM.

Email address updates

Supports eligible email update behavior that retains destination history instead of deleting and recreating the record.

Use case

Keep email engagement history when a constituent changes address.

Converted lead and deleted record cleanup

Applies supported converted lead, source deletion, and blank email cleanup rules.

Use case

Avoid leaving obsolete constituent records in the marketing audience.

Facebook lead import to NPSP

Receives supported lead form submissions through the Facebook and Salesforce-based connectors.

Use case

Bring volunteer or donor interest form submissions into NPSP.

Submission field mapping

Maps supported form data into available destination fields.

Use case

Retain signup answers with the constituent's CRM record.

Fine-tune every Set Up.

Explore the field mapping, scheduling, and reporting controls available across supported integrations.

Shared SyncApps features

23 features

Additional field mapping

Maps supported standard and custom fields.

Use case

Transfer customer classifications or account attributes.

Mapping direction

Controls supported field-level direction independently of the general record flow.

Use case

Accept a specific field update from marketing.

Field value translation

Translates configured source values to destination values.

Use case

Convert CRM picklist values into the destination's labels.

Static value mapping

Maps a fixed value into a destination field.

Use case

Mark records with the source integration's name.

Expression mapping

Uses supported expressions to calculate mapped values.

Use case

Combine or transform source values for a destination field.

Mapping exclusions

Excludes supported fields from updates.

Use case

Keep a destination-managed field from being overwritten.

Record filtering

Applies conditions to supported source or destination records.

Use case

Sync only records for a selected region.

Named segmentation

Builds multiple named segments with configured conditions.

Use case

Create separate audiences for different customer types.

Custom opt-out field

Uses an eligible custom source field for subscription state instead of the standard opt-out field.

Use case

Apply the business's existing subscription field to the integration.

Integration start date

Sets the starting date for supported record retrieval.

Use case

Limit an initial import to recent data.

Scheduled sync

Runs integrations at supported recurring intervals.

Use case

Refresh customer data at a regular interval.

Selected-day scheduling

Runs eligible integrations on selected days of the week.

Use case

Schedule updates on working days.

Sync on demand

Starts an eligible integration manually.

Use case

Send a corrected record through immediately.

Full Sync

Reconciles supported source and destination membership beyond incremental changes. Removal behavior depends on the connector and enabled cleanup options.

Use case

Remove stale segment membership after changing source criteria.

Full Sync interval control

Configures the supported reconciliation interval.

Use case

Run membership reconciliation on an agreed cadence.

Historical campaign responses

Expands supported campaign history retrieval beyond the usual age restriction.

Use case

Migrate older campaign engagement into CRM.

Responses on every sync

Runs eligible response processing on every scheduled sync rather than its usual daily cycle.

Use case

Return campaign results more frequently.

Concurrent integrations

Allows eligible Set Ups to run concurrently.

Use case

Process independent integrations without waiting for each to finish.

Live progress and run history

Displays execution progress and past sync instances.

Use case

Check whether the latest scheduled run finished.

Sync reports and record errors

Shows supported record counts, outcomes, and detailed errors.

Use case

Find records rejected by the destination.

Downloadable reports and logs

Downloads available sync files, reports, or error logs, including supported date-based ZIP downloads.

Use case

Share a failed run's details with the integration team.

API call reporting

Displays available API usage information in run logs and reports.

Use case

Investigate a destination API limit error.

Error notifications

Configures supported sync-level and record-level error notifications.

Use case

Alert the account owner when a run needs attention.

Put your features to work.

Connect your apps and test your first Set Up with your own data.