Help with Two-Way Automation Between Salesforce & Constant Contact – New Nonprofit User

Hi Make Community,

We are a nonprofit organization and new to Make. We’re trying to set up a two-way automation between Salesforce and Constant Contact, so that:

  1. Adding or deleting a contact in Salesforce updates Constant Contact automatically.

  2. Adding or deleting a contact in Constant Contact updates Salesforce automatically.

We’ve attempted to set this up, but it isn’t working as expected. Some contacts are not syncing, and updates sometimes fail to appear on the other platform.

Here are the details of our setup:

  • Trigger modules: Salesforce and Constant Contact “Watch Contacts”

  • Actions: Create/Update/Delete contacts on the other platform

  • Filters/conditions: [Briefly describe any filters or conditions you applied]

  • Errors or unexpected behavior: [Include screenshots or error messages if available]

We would greatly appreciate guidance or examples for:

  • Ensuring full two-way syncing for both new and existing contacts

  • Best practices for setting this up as a nonprofit new to Make

Thank you so much in advance for your help! Any tips, templates, or example scenarios would be extremely helpful.

Best,

BCA Global

Welcome to the Make community!

Two-way syncing is generally not practicable in Make. Plus your question is quite broad and without specific details of what’s not working.

To allow others to assist you with your scenario, please provide the following:

1. All Relevant Screenshots

We need to see what you’re working with to give you the best advice. Screenshots are extremely important because Make is a visual editor — a picture provides us with more context.

It would help us identify the issue by having screenshots of:

  • the full scenario,
  • any error messages,
  • individual module fields,
  • relevant filter settings (conditions), and
  • each module’s output bundles
  • any external services (spreadsheet headers, sample data, regex101.com, etc.)

2. Scenario Blueprint

Please export the scenario blueprint. Providing your scenario blueprint file will allow others to quickly recreate and see how you have set up the mappings in each module, and also allows us take screenshots or provide module exports of any solutions we have for you in return - this would greatly benefit you in implementing our suggestions as you can simply paste module exports back into your scenario editor!

To export your scenario blueprint, click the three dots at the bottom of the editor then choose ‘Export Blueprint’.

3. Module Output Bundles

Please provide the output bundles of each of the relevant modules by running the scenario (you can also get this without re-running your scenario from the History tab).

Click on the white speech bubbles on the top-right of each module and select “Download input/output bundles”.

A. Upload as a Text File

Save each bundle contents in a plain text editor (without formatting) as a bundle.txt file.

You can upload the file here by clicking on this button:

B. Insert as Formatted Code Block

If you are unable to upload files on this forum, alternatively you can paste the formatted bundles.

To provide code/text using Markdown format, you can type a code fence.
Add three backticks ``` in a separate line before and after the content, like this,

```
text goes here
```

Alternatively, you can upload your file and share the public link** —
(this method is only recommended for large files exceeding the forum upload limit)

Providing the input/output bundles will allow others to replicate what is going on in the scenario, especially if there are complex data structures (nested arrays and collections) or if external services are involved, and help you with mapping the raw property names from collections.

Sharing these details will make it easier for others to assist you.