Skip to main content
Use the @bijection/connectors/salesforce-marketing-cloud entrypoint to declare Salesforce Marketing Cloud Engagement resources.

​
Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

​
Resources and modes

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

​
Data extension rows

​
pull: Anchored row walk, optionally from a carried modified-date column

The following example matches configuration standard.

​
Configuration: standard

Case: salesforce-marketing-cloud/rows/pull/standard. Connection and resource configuration are declared by this exact case. Credential kind: salesforce_marketing_cloud. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: rows
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

​
Configuration: whole

Case: salesforce-marketing-cloud/rows/pull/whole. Connection and resource configuration are declared by this exact case. Credential kind: salesforce_marketing_cloud. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: rows
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

​
Provider guidance

Compiled declaration examples and configuration details are published in the connector reference. Endpoints are tenant-specific: the connection’s subdomain (the mc... value on the installed package) selects https://<subdomain>.rest.marketingcloudapis.com. The salesforce_marketing_cloud credential is a server-to-server client-credentials grant against https://<subdomain>.auth.marketingcloudapis.com/v2/token with a JSON body; its answer names the REST origin in rest_instance_url, which the credential’s resource-origin rule confines to marketingcloudapis.com. The grant’s account_id (business unit MID) is not a field the credential sends, so the token acts for the package’s own business unit. The REST host answers no tenant identity (/v2/userinfo is on the auth host), so the connection is its own namespace. A 429’s Retry-After is honoured. rows.pull reads one data extension through GET /data/v1/customobjectdata/key/<key>/rowset ($pagesize 100, $offset) with an anchored offset walk, keyed by its primary key columns (compound for several). Values are the text the API wrote. Without modifiedColumn every pass walks the whole extension in the order rows were added. With it, the first pass walks the whole extension and later passes read $orderBy=<column> DESC from the newest row until a page reaches ten minutes below the latest value carried. Marketing Cloud keeps no row modification date and its REST filter admits primary keys only, so the bound is the writers’ column. Ordering and paging need a sendable extension; a non-sendable one answers at most 200 rows. Deleted rows stay published. Not built: SOAP retrieval (the OAuth token travels inside the SOAP header as fueloauth, which no credential can write into an XML body) and with it the tracking event objects (SentEvent, OpenEvent, BounceEvent, UnsubEvent), which have no REST read. Nothing here has run against Marketing Cloud.

​
Provider references

Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.

​
Source and evidence

Canonical connector source, native analysis and check receipts. Connector artifact: 905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305. The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.