The Salesforce Marketing Cloud connector is a Palantir-provided driver for Salesforce Marketing Cloud.
To create a new Salesforce Marketing Cloud source, follow the standard setup flow for Palantir-provided drivers, then use the sections below for Salesforce Marketing Cloud-specific configuration and networking. For the complete property reference, see the official Salesforce Marketing Cloud driver documentation ↗.
The properties below are mandatory or recommended.
| Property | Required? | Description | Default |
|---|---|---|---|
Schema ↗ | Mandatory | Specify the Salesforce Marketing Cloud server version to connect with. | SOAP |
Subdomain ↗ | Mandatory | The subdomain of the Salesforce Marketing Cloud API. | — |
InitiateOAuth ↗ | Recommended | Specifies the process for obtaining or refreshing the OAuth access token, which maintains user access while an authenticated, authorized user is working. | REFRESH |
OAuthClientId ↗ | Recommended | Specifies the client Id that was assigned when the custom OAuth application was created. (Also known as the consumer key.) This ID registers the custom application with the OAuth authorization server. | — |
OAuthClientSecret ↗ | Recommended | Specifies the client secret that was assigned when the custom OAuth application was created. (Also known as the consumer secret). This secret registers the custom application with the OAuth authorization server. | — |
Password ↗ | Recommended | Specifies the password of the authenticating user account. | — |
UseLegacyAuthentication ↗ | Recommended | A boolean determining if the connection should be made to Salesforce Marketing Cloud REST API using the legacy authentication. | TRUE |
User ↗ | Recommended | Specifies the user ID of the authenticating Salesforce Marketing Cloud user account. | — |
The table below lists the domains that the source needs to be able to access in order to successfully run.
For each domain, add a corresponding egress policy. If the source is hosted on-premises and not directly reachable from Foundry, use an agent proxy egress policy instead; the agent host itself must also be able to reach the listed domains. See using an agent as a proxy for details.
| Domain | Required |
|---|---|
| <Subdomain>.soap.marketingcloudapis.com | If Schema=SOAP (default) |
| <Subdomain>.rest.marketingcloudapis.com | If Schema=REST |
| <Subdomain>.auth.marketingcloudapis.com | If UseLegacyAuthentication=FALSE (default) AND AuthScheme=OAuth, OAuthClient |