Connector library

Implemented source Marketing, Analytics & Revenue APIs

Salesforce Marketing Cloud connector.

Read Marketing Cloud Engagement journey and entry-event definition metadata through four named REST actions with managed bearer credentials, tenant-specific endpoints, version selection and checked pagination.

Connector download

Download Salesforce Marketing Cloud

Versioned ZIP for your CXFabric tenant.

Use this connector in a flow

  1. Register the ZIP in your tenant, or add a new version if the connector is already installed.
  2. Create or select a credential if the action requires one.
  3. In a Draft flow, add an available action, choose its version, connect it, and map inputs.
  4. Test the step and flow; review output and failures before activation.

See readme.md in the ZIP for settings and limitations.

Version
v0.2.0.0 Choose version
Release
2026-10-04
Package
Implemented source
Schema credentials
Bearer token
Connection settings
Tenant Subdomain
Package size
10 KB
SHA-256
f4e821488d421928ed97bf721d908d431d07c9205ff4c3a1184c663f2f651898

Version history

What's new

  1. v0.2.0.0Latest · 2026-10-04 · Implemented source

    Read Marketing Cloud Engagement journey and entry-event definition metadata through four named REST actions with managed bearer credentials, tenant-specific endpoints, version selection and checked pagination.

  2. v0.1.1.0Earlier · 2026-10-02 · Starter scaffold

    Historical readable HTTP scaffold.

Included in this version

Included actions

Implemented in v0.2.0.0. Use a separate flow trigger; no webhook trigger is included.

List journeys

Read selected metadata for the most recent version of each visible journey.

Get journey

Read selected metadata for one original journey definition, optionally at a chosen version.

List event definitions

Read selected entry-event names, keys, type and optional mode/visibility across checked pages.

Get event definition

Read selected metadata for one exact entry-event definition GUID.

Vendor API

API and access

Implementation considerations
  • Journey lookups: List the most recent visible journey versions or look up an original definition at the latest or a selected version.
  • Entry-event definition lookups: List selected entry-event names, keys, type and optional mode/visibility, or look up an exact definition GUID.
  • Bounded metadata reads: Read selected definition metadata with checked page/count totals, without activities, message content or contact data.
  • Use scheduled flows for metadata reads; no webhook trigger is included.
  • Use a managed Bearer Token credential containing the issued Marketing Cloud OAuth access token and the tenant subdomain from the installed package REST Base URI.
  • Get journey uses the original definitionId, distinct from versionId. An optional version selects and verifies a specific version; blank requests the latest.
  • The package reads Engagement definitions. Sending messages, firing events, changing journeys and reading contact data are outside its scope. Package read actions do not make a broadly permitted token read-only.

Support

Need help with Salesforce Marketing Cloud?

Tell us what you need to connect or change.