Messaging and customer data

Connect Salesforce Marketing Cloud

Send trigger data to a Marketing Cloud journey or Data 360 ingestion endpoint.

All connectors · Checked against AXO’s implementation in October 2026.

Prepare access

Use an owner or admin account in AXO and confirm the selected site. Have permission to authorize the external account or create its server credentials. Keep secrets in the connector’s protected configuration.

Setting	Value to prepare
`mc_edition`	engagement (default) or advanced.
`client_id`	OAuth client ID for the edition.
`client_secret`	Matching client secret.
`subdomain`	Engagement tenant subdomain.
`event_definition_key`	Engagement journey API event definition key.
`my_domain`	Advanced only: Salesforce My Domain.
`connector_name`	Advanced only: Data 360 ingestion connector.
`object_name`	Advanced only: ingestion object.

Connect

The current catalog form does not expose the full configuration for this connector. Use Advanced setup below before completing these steps.

Create a trigger, select this integration as its destination, and render the provider’s expected payload in its template. Selecting Events to forward alone does not invoke this native trigger adapter.
For Engagement, provision the API integration and activate the intended journey entry event. For Advanced, provision the ingestion connector and matching object schema.

Verify the result

The check validates credentials for the chosen edition. Verify the journey event or ingested object separately.

Record the AXO integration or trigger result and the receiving system’s result. A saved configuration, credential check, and completed delivery establish different things. Use a controlled destination for a test that writes data or sends a message.

Fix a failed connection

Do not mix Engagement tenant values with Advanced Data 360 values. Check edition-specific permissions and template shape.

For a saved catalog connector, open Health to read the latest error, then repair the settings through the setup method on this page. Pause delivery while correcting an unintended destination. Reconnect OAuth when its grant is revoked; for key-based connections, save the replacement key, verify it, then revoke the old key at the provider.

Advanced setup with an AXO MCP client

Connect the AXO MCP server with write access to the intended site. The authenticated account must have owner/admin permission.
Call create_integration with the type below and a config object using the exact field names above. Start with active: false and no event subscriptions. Supply credential values through your protected tool configuration.
Keep the returned integration ID. Use update_integration for corrections rather than creating duplicates.
Complete any authorization steps above, configure the trigger or source, and perform the verification described here. Source imports need the integration enabled before scheduled synchronization can run. Use test_integration only if this guide describes a supported test.
Use update_integration with the returned integration_id and active: true to enable the integration after checking its external account and payload. Enable the intended trigger separately. Copy expected_revision from the latest get_integration read when one is returned.

Create integration arguments

{
  "type": "sfmc",
  "config": {
    "mc_edition": "engagement",
    "client_id": "REPLACE_WITH_YOUR_VALUE",
    "client_secret": "REPLACE_WITH_YOUR_VALUE",
    "subdomain": "REPLACE_WITH_YOUR_VALUE",
    "event_definition_key": "REPLACE_WITH_YOUR_VALUE"
  },
  "events": [],
  "active": false
}

The example is a configuration checklist. Replace placeholders and omit optional or inapplicable fields before calling the tool. A dry run previews the request but does not validate provider access.

Next: create an event-triggered action, or implement a webhook receiver.