DinMo Documentation
  • 📙Core Concepts
  • Guides
    • ⚡Get started with DinMo
      • Initial Configuration of DinMo
        • Connect a Source
        • Create your Models
        • Create a Destination
      • Create and Activate Segments on DinMo
        • Create your first Segment
        • Activate your first Segment
    • 🌐Workspaces & Organizations
    • 💭Need Help?
  • Integrations
    • Data Sources
      • AWS Redshift
      • Databricks
      • Google BigQuery
      • PostgreSQL
      • Snowflake
    • Destination Platforms
      • Actito
        • Synchronize users attributes
        • Export contact lists
      • All My SMS
      • Batch
        • Synchronize contacts (MEP)
        • Synchronize profiles (CEP)
        • Send events (CEP)
      • Braze
        • Synchronize users attributes
        • Send track events
        • Synchronize subscription statuses
        • Export user lists
      • Brevo
        • Synchronize contacts
        • Export contact lists
      • Criteo
        • Export contact lists
      • Dialog Insight
        • Synchronise Contacts
      • Emarsys
        • Export contact lists
        • Synchronize contacts data
        • Synchronize custom table's data (RDS)
      • Firestore
        • Create and update Collection Documents
        • Export Audiences
      • Google Ads
        • Export audiences
        • Enhanced Conversions for Web
        • Upload click or offline conversions
          • Prerequisites and walkthrough
        • Adjust conversion events
        • Retract conversion events
      • Google Display & Video 360
        • Export audiences
      • Google Search Ads 360
      • Hubspot
        • Synchronize objects
      • Intercom
        • Export segments
        • Synchronize contacts
        • Synchronize companies
      • Iterable
        • Synchronize user attributes
        • Export contact lists
      • June Email Marketing
        • Export Contact Lists
      • Klaviyo
        • Export contact lists
        • Synchronise contacts
        • Create subscription list
      • LinkedIn Ads
        • Export user audiences
        • Export company audiences
      • Mailchimp
        • Export segments
      • Meta Ads
        • Export audiences
        • Send conversion events
      • Microsoft Ads (Bing)
        • Export audiences
      • Pinterest Ads
        • Export audiences
        • Send conversions
      • Reddit Ads
        • Export Audiences
      • Salesforce Marketing Cloud
        • Synchronize data extensions
      • SendGrid
        • Synchronize contacts
        • Export contact lists
      • Selligent
      • Snapchat Ads
        • Export Audiences
      • Splio
        • Synchronize contacts
      • TikTok Ads
        • Export Audiences
        • Send Offline Conversions
        • Send Web Conversions
      • X (Twitter)
        • Export audiences
      • Zendesk
        • Synchronize users
        • Synchronize custom objects' data
  • Models
    • Overview
    • Primary Keys
      • Detect duplicate primary keys
    • Calculated Fields
  • Identity resolution
    • Overview
  • Segments
    • Visual Builder
    • Breakdowns
    • Overlap Analysis
  • Activations
    • Overview
    • Sync Scheduling
    • Troubleshooting Syncs
      • Automatic pause or resume Activations
      • Sync warnings
  • AI PREDICTIONS
    • Overview
    • LTV and Churn
    • Product Recommendations
  • WORKSPACE MANAGEMENT
    • Set Up
    • Managing Users & Roles
    • Audit Logs
    • Enterprise Single Sign-On (SSO)
  • Security & Privacy
    • Overview
    • Networking
    • Privacy
    • Data Processing
Powered by GitBook
On this page
  • Overview
  • Destination setup
  • Activation configuration
  • Fields mapping
  • Custom Attributes
  1. Integrations
  2. Destination Platforms
  3. Zendesk

Synchronize custom objects' data

PreviousSynchronize usersNextOverview

Last updated 10 months ago

Overview

In this destination service, DinMo will synchronize rows of a custom object, and optionally, insert new records in this object.

To create such an activation, you will need to go through these three steps:

  • Creating a Zendesk destination specifying the target custom object to update. Refer to the for more info.

  • Creating a custom model or custom segment composed of all the data that will populate the custom object.

  • Activating the model or segment to the Zendesk destination to start sending data. Refer to the for more info.

Each time the activation will be running:

  • If you ticked the insert mode option, all new rows of the model will be inserted in the custom object (upsert)

  • All rows that have changed since the last activation will be updated in Zendesk

If you chose not to insert new records, only records of the model which are already present in Zendesk will be updated (update only).

The target custom object should already exist in Zendesk, it is not possible to create it from DinMo.

Destination setup

To start synchronizing custom objects' data, you are first required to create a Zendesk destination with the corresponding destination service.

In this process, you must specify which custom object will be updated in this destination. If you wish to update different custom objects, please create one distinct destination for each of these objects.

Learn how to create such a destination in our

Activation configuration

Once the destination has been setup, and your DinMo model created, you can create an activation to start sending data to Zendesk right away.

Fields mapping

In the Fields mapping section, you are asked to specify the field contained in your DinMo model corresponding to the external ID of the target object. This field will be used to link the model's records to existing records in Zendesk. Zendesk API also requires that you map a Name field, which should not be blank. This will be the name of the record created in Zendesk side.

You can then map any other fields existing in the custom object. These fields will then be updated by DinMo during each activation.

Custom Attributes

In this section, any field you select will be exported as a new column in the Zendesk custom object. The associated field will have the same name in Zendesk and DinMo.

The values of the attributes selected here will then also be updated during each activation.

Learn how to activate a model in our

step-by-step tutorial
step-by-step tutorial
corresponding section
corresponding section