SuperSend → Make → Salesforce Setup

Purpose

Send contact data from SuperSend into Make.com, which then syncs to Salesforce. Use this when you need events (replies, opens, contact added, etc.) in SuperSend to trigger CRM updates in Salesforce via Make.

Field Mapping

Custom fields: Any custom data you add to contacts (via CSV or API) is sent in the webhook under contact.custom. The field name in the webhook matches whatever you named it when adding the contact—your CSV column header or the key you used in the API.

Step 1: Add Custom Fields in SuperSend

Option A: CSV Upload

1. Add a column to your CSV (e.g. Gross_Monthly_Revenue_Dropdown__c or any name you prefer).
2. During CSV import, map that column to Custom Field (not a standard field).
3. When the webhook fires, that data is sent under contact.custom using the column name as the field name.

Option B: API

When creating contacts via API, include custom fields:

{
  "email": "john@acme.com",
  "first_name": "John",
  "last_name": "Doe",
  "company_name": "Acme Corp",
  "phone": "+1234567890",
  "TeamId": "your-team-id",
  "CampaignId": "your-campaign-id",
  "custom": {
    "Gross_Monthly_Revenue_Dropdown__c": "100k-500k"
  }
}

Step 2: Configure Webhook in SuperSend

1. Go to Campaign → Settings → Integrations.
2. Add a Webhook integration.
3. Enter your Make.com webhook URL (from Step 3).
4. Enable the events you need:

• Contact Added — when contacts enter the campaign
• Reply — when a contact replies
• Open — when an email is opened
• Click — when a link is clicked
• Finished — when contact completes the sequence

5. Save.

Step 3: Create Make.com Scenario

1. In Make, create a new scenario.
2. Add Webhooks → Custom webhook as the trigger.
3. Copy the webhook URL and paste it into SuperSend (Step 2).
4. Add Salesforce → Create a record (or Update a record).
5. Connect your Salesforce account in Make.
6. Map fields from the webhook to Salesforce:

| Map from (Make) | To Salesforce |

|-----------------|----------------|

| 1.contact.first_name | First Name |

| 1.contact.last_name | Last Name |

| 1.contact.company_name | Company |

| 1.contact.email | Email |

| 1.contact.phone | Phone |

| 1.contact.custom.Gross_Monthly_Revenue_Dropdown__c | Gross_Monthly_Revenue_Dropdown__c |

7. In Make, use the data inspector on the webhook trigger to see the incoming data and map each field. The structure SuperSend sends is shown below. Activate the scenario.

What SuperSend Sends to Make

When an event fires (reply, open, contact added, etc.), SuperSend sends a JSON payload to your webhook. Here's the structure:

{
  "event_id": "a1b2c3d4-...",
  "timestamp": "2026-01-19T14:32:15.123Z",
  "type": "reply",
  "CampaignId": "campaign-uuid",
  "conversationId": "conv-uuid",
  "app_url": "https://app.supersend.io/...",
  "campaign": { "id": "...", "name": "..." },
  "team": { "id": "...", "name": "..." },
  "org": { "id": "...", "name": "..." },
  "contact": {
    "id": "contact-uuid",
    "email": "john@acme.com",
    "first_name": "John",
    "last_name": "Doe",
    "company_name": "Acme Corp",
    "phone": "+1234567890",
    "title": "CEO",
    "custom": {
      "Gross_Monthly_Revenue_Dropdown__c": "100k-500k"
    }
  }
}

Custom fields: If you added custom data when importing the contact (CSV column mapped to Custom Field, or custom in the API), it appears in contact.custom. The key is whatever you named the field. If the contact has no custom fields, contact.custom may be empty or missing.

Custom Fields Quick Reference

• From CSV: Add a column, map it to Custom Field during import. The column header is the field name in the webhook.
• From API: Include custom: { "YourFieldName": "value" } in your request. That key is the field name in the webhook.
• In Make: Use the webhook’s data inspector to see the incoming data. Custom fields appear under the contact object.

Troubleshooting

• Custom field empty or wrong path in Make: Use Test webhook in SuperSend (Campaign Settings → Integrations → Webhook) or check Webhook delivery logs to see the exact payload we sent. Verify your custom field appears in the contact data and note the exact field name you used.
• Webhook not firing: Check that the event (e.g. Reply, Contact Added) is enabled in the Webhook integration.
• Salesforce API name: Use the Salesforce API name (e.g. Gross_Monthly_Revenue_Dropdown__c), not the label.

Related Articles

• Webhook Integration
• Zapier and Make Setup
• Integrations Overview

Updated on: 18/03/2026