Skip to main content

Pitchly to Dynamics 365: Sync Updates from Pitchly

Push updates from Pitchly back to existing records in Dynamics 365

This article walks through how to update existing records in Dynamics 365 that were originally synced into Pitchly via a Dynamics β†’ Pitchly automation. This setup supports update-only sync β€” no new records will ever be created in Dynamics.


Permissions Required

  • Pitchly: Admin access required

NOTE: You must first set up a record sync from Dynamics to Pitchly before setting up this automation. Only records created via that initial sync can be updated in Dynamics.

IMPORTANT: You must sync and map the unique identifier (Record ID or GUID) from Dynamics during your Dynamics β†’ Pitchly setup. This field is required in order to enable update sync back to Dynamics.


Step 1: Access the Pitchly Integration

  1. Log in to Pitchly with an Admin account

  2. Select the Integrations tab from the left navigation

  3. Locate the Pitchly tile and click Connect


Step 2: Configure Your Source

  1. On the Configure Source screen:

    • Confirm Pitchly is selected in the From dropdown

    • In the I want to sync dropdown, select Records

    • In the With the account dropdown, select your authorized Pitchly account

  2. Click Next


Step 3: Select the Source Workspace and Table

  1. Choose the Pitchly workspace that contains the records originally synced from Dynamics

  2. Select the table where those records exist

  3. In the Ignore Updates flag value dropdown, select No

  4. Click Next


Step 4: Configure Your Dynamics Destination

  1. In the To dropdown, select Dynamics

  2. In the I want to sync dropdown, select Records

  3. Under With the account, select your previously authorized Dynamics account

  4. Click Next


Step 5: Select the Destination Table and Primary Key

  1. Choose the Dynamics table where the records originally came from

  2. In the Primary Key Field dropdown, select the unique identifier for the record

    • Example: Account ID Primary for the Account table

  3. Click Next


Step 6: Map Fields

  1. On the left, select the Pitchly fields you want to send back to Dynamics

  2. On the right, select the corresponding field in the Dynamics table

  3. You must map the primary key field (e.g., Do Not Modify Account Primary) to ensure Pitchly can match the record correctly

  4. Optionally map any other fields you want Pitchly to update

    • Examples: Tombstone Description, Approval Status, etc.


Step 7: Complete and Activate the Sync

  1. Review your configuration and field mapping

  2. Click Finish

  3. When prompted, click Turn On to activate the automation or select Not Now to activate it later

Did this answer your question?