Marketing Automation · Beta
Salesforce Marketing Cloud Engagement
API integration
Ship Marketing Automation features without building the integration. Full Salesforce Marketing Cloud Engagement API access via Proxy and 320+ MCP-ready tools for AI agents — extend models and mappings to fit your product.
Built for specific customer use cases. Issues are resolved quickly.
Talk to usUse Cases
Why integrate with Salesforce Marketing Cloud Engagement
Common scenarios for SaaS companies building Salesforce Marketing Cloud Engagement integrations for their customers.
Sync Customer Data into Marketing Cloud Data Extensions
Let your users push product usage, scores, or audience cohorts from your platform directly into SFMC Data Extensions so marketers can segment and target without manual CSV uploads. Ideal for CDPs, reverse ETL, analytics, and lead scoring products.
Trigger Real-Time Customer Journeys from Product Events
Fire behavioral events (cart abandoned, tier upgraded, payment failed, webinar registered) into SFMC Journey Builder so your users' marketing teams can orchestrate omnichannel follow-ups without engineering involvement.
Send Transactional Email, SMS, and Push via the Customer's SFMC
Deliver OTPs, receipts, booking confirmations, and reminders through your users' pre-approved SFMC transactional definitions, keeping sends on their verified domains, IP pools, and compliance posture.
Publish Content Directly into SFMC Content Builder
For DAM, headless CMS, and AI copy tools — push images, HTML blocks, and templates into categorized folders in SFMC's asset library so marketers can drag-and-drop them into campaigns.
Manage Consent, Preferences, and Contact Lifecycle
Keep opt-ins, opt-outs, and custom communication preferences in sync between your product and SFMC to help mutual customers stay compliant with GDPR, CCPA, and internal consent policies.
What You Can Build
Ship these features with Truto + Salesforce Marketing Cloud Engagement
Concrete product features your team can ship faster by leveraging Truto’s Salesforce Marketing Cloud Engagement integration instead of building from scratch.
Data Extension Row Upserts
Bulk upsert rows into any customer-selected Data Extension to keep attributes like lifetime value, loyalty points, or churn score continuously fresh in SFMC.
Journey Event Injection
Let users map your product events to SFMC Journey entry events, with a single API call injecting contacts into live journeys in real time.
Transactional Email & SMS Dispatch
Ship a transactional messaging module that sends 1:1 email, SMS, push, and OTT messages through your users' existing SFMC transactional definitions.
Content Builder Asset Publisher
Allow users to create asset categories (folders) and upload images, HTML, and text blocks directly into SFMC Content Builder from your UI.
Contact & Preference Sync
Create contacts, update their communication preferences, and process restriction or deletion requests to maintain a compliant subscriber base.
Campaign & Automation Orchestration
Create campaigns, link assets, and start or schedule Automation Studio automations programmatically so your product can trigger reporting-ready marketing workflows.
SuperAI
Salesforce Marketing Cloud Engagement AI agent tools
Comprehensive AI agent toolset with fine-grained control. Integrates with MCP clients like Cursor and Claude, or frameworks like LangChain.
list_all_salesforce_marketing_cloud_engagement_account_settings
Retrieve information about settings that apply to your account. Retrieves the status of the Einstein Data Pooling. To retrieve the status of this business rule for all business units in an enterprise, include the entire_enterprise=true query parameter (GET /platform/v1/settings).
list_all_salesforce_marketing_cloud_engagement_approval_roles
Retrieves a list of roles for a given approval item as well as the users assigned to those roles (GET /hub/v1/approvals-v2/{id}/roles). Required: approval_id.
list_all_salesforce_marketing_cloud_engagement_approval_settings
Retrieves the approvals settings based on the current user context (GET /hub/v1/approvals-v2/settings).
approval_settings_bulk_update
Updates the approvals settings with the values provided in the request body. Currently only the EnableEmailApprovals setting can be updated using the API (PATCH /hub/v1/approvals-v2/settings).
create_a_salesforce_marketing_cloud_engagement_approval
Create Approval and an associated workflow item (POST /hub/v1/approvals-v2).
get_single_salesforce_marketing_cloud_engagement_approval_by_id
Get Approval item for current user (GET /hub/v1/approvals-v2/{id}). Required: id.
list_all_salesforce_marketing_cloud_engagement_approvals
Get all Approval items (GET /hub/v1/approvals-v2). The connector pages through all results with $page and $pageSize.
update_a_salesforce_marketing_cloud_engagement_approval_by_id
Update Approval item (PATCH /hub/v1/approvals-v2/{id}). Required: id.
salesforce_marketing_cloud_engagement_asset_archives_bulk_update
Archive an asset. When you archive an asset, Marketing Cloud Engagement removes it from availability for queries, triggered sends, and journeys, as if the asset were deleted (PATCH /asset/v1/content/assets/{id}/archive). Required: asset_id.
list_all_salesforce_marketing_cloud_engagement_asset_categories
Get categories. Returns one or more Content Builder categories that are owned by or reside in your MID. To request categories that have been shared with your MID, add a scope parameter to the call (GET /asset/v1/content/categories). The connector pages through all results with $page and $pagesize.
create_a_salesforce_marketing_cloud_engagement_asset_category
Create category. Creates a category in Content Builder. A category is a folder that contains assets (POST /asset/v1/content/categories).
get_asset_category_by_id
Get category by ID. Returns one Content Builder category by ID (GET /asset/v1/content/categories/{categoryId}). Required: id.
update_asset_category_by_id
Update category. Updates a Content Builder category (PUT /asset/v1/content/categories/{categoryId}). Required: id.
delete_asset_category_by_id
Delete category. Deletes a Content Builder category (DELETE /asset/v1/content/categories/{categoryId}). Required: id.
get_asset_channel_view_by_id
Get channel view. Returns the compiled HTML for a requested channel view of an asset (GET /asset/v1/content/assets/{id}/channelviews/{viewName}). Required: asset_id, id.
list_all_salesforce_marketing_cloud_engagement_asset_files
Get asset file. Gets the binary file for an asset (GET /asset/v1/content/assets/{id}/file). Required: asset_id.
list_all_asset_headers_footers
Get email salutations. Retrieves the header and footer of an email asset by specifying the asset ID (GET /asset/v1/content/assets/{id}/salutations). Required: asset_id.
create_a_salesforce_marketing_cloud_engagement_asset_query
Get assets by advanced query. Use an advanced query to retrieve a collection of assets (POST /asset/v1/content/assets/query).
salesforce_marketing_cloud_engagement_asset_restores_bulk_update
Restore asset. Restore an asset hidden by a prior archive operation, and make it available again for queries, triggered sends, journeys, and other operations (PATCH /asset/v1/content/assets/{id}/restore). Required: asset_id.
list_all_salesforce_marketing_cloud_engagement_asset_salutations
Get default salutations. Retrieves the default header and footer for an account (GET /asset/v1/content/assets/salutations).
list_all_salesforce_marketing_cloud_engagement_assets
Get assets by simple filter. Retrieve a collection of assets by applying basic filters and sorting rules (GET /asset/v1/content/assets). The connector pages through all results with $page and $pagesize.
create_a_salesforce_marketing_cloud_engagement_asset
Create asset. Creates a new asset (POST /asset/v1/content/assets).
get_single_salesforce_marketing_cloud_engagement_asset_by_id
Get asset by ID. Retrieves an asset by its ID (GET /asset/v1/content/assets/{id}). Required: id.
update_a_salesforce_marketing_cloud_engagement_asset_by_id
Update an asset. Modify the properties of an existing asset (PUT /asset/v1/content/assets/{id}). Required: id.
salesforce_marketing_cloud_engagement_assets_partial_update
Patch an asset. Modify the properties of an asset deleted in the last 30 days (PATCH /asset/v1/content/assets/{id}). Required: asset_id.
delete_a_salesforce_marketing_cloud_engagement_asset_by_id
Delete an asset. Deletes an asset (DELETE /asset/v1/content/assets/{id}). Required: id.
list_all_async_request_results
Retrieve the results of a request to asynchronously insert rows into a data extension. For information about the limits that apply to this API, see _Salesforce Help_: [Limits and Guidelines]( (GET /data/v1/async/{requestId}/results). Required: request_id.
list_all_async_request_statuses
Retrieve the status of a request to asynchronously insert rows into a data extension. For information about the limits that apply to this API, see _Salesforce Help_: [Limits and Guidelines]( (GET /data/v1/async/{requestId}/status). Required: request_id.
list_all_salesforce_marketing_cloud_engagement_audit_events
GET /data/v1/audit/auditEvents. Retrieve logged Audit Trail audit events for the current account and its child accounts. Logins are audited at the enterprise level. Timestamps for Audit Trail data use the US Central Standard Time (GMT-6, CST) timezone (GET /data/v1/audit/auditEvents). The connector pages through all results with $page and $pagesize.
list_all_salesforce_marketing_cloud_engagement_auth_discovery
Get base URLs. Obtain the base URLs for the Marketing Cloud Auth and REST APIs. These application-specific URLs are unique to your Marketing Cloud account and installed package (GET /v2/discovery). Required: clientId, resource.
get_automation_definition_by_id
Retrieve an automation definition, including its steps and activities, by providing its ID. Each activity in the steps array includes an objectTypeId that identifies the type of activity. For the list of activity types, see Automation Activity Types (GET /automation/v1/automations/automation/definition/{id}). Required: id.
update_automation_definition_by_id
Update the name, description, or key of an automation definition by providing its ID. Include only the properties that you want to change. If another automation in your business unit already uses the name or key, the API returns a 409 response. This operation changes only the name, description, and key (PATCH /automation/v1/automations/automation/definition/{id}). Required: id.
delete_automation_definition_by_id
Delete an automation definition by providing its ID. You can’t delete an automation while it’s running. In that case, the API returns a 409 response (DELETE /automation/v1/automations/automation/definition/{id}). Required: id.
list_all_automation_definitions_by_key
Retrieve an automation definition, including its steps and activities, by providing the external key of the automation. Identify the automation by its external key instead of its ID. The request body and the response are the same as for Get an automation definition (GET /automation/v1/automations/automation/definition/key:{key}). Required: definition_key.
automation_definitions_by_key_bulk_update
Update the name, description, or key of an automation definition by providing the external key of the automation. Identify the automation by its external key instead of its ID. The request body and the response are the same as for Update an automation definition (PATCH /automation/v1/automations/automation/definition/key:{key}). Required: definition_key.
automation_definitions_by_key_bulk_delete
Delete an automation definition by providing the external key of the automation. Identify the automation by its external key instead of its ID. The request body and the response are the same as for Delete an automation definition (DELETE /automation/v1/automations/automation/definition/key:{key}). Required: definition_key.
update_automation_file_trigger_by_id
Activate or deactivate an automation file trigger by providing its ID. ## Required Scopes To update the status of a trigger request, your API user must have this permission: - Automation Write (automations_write) (PATCH /automation/v1/automations/filetrigger/{id}). Required: id.
automation_file_triggers_by_key_bulk_update
Activate or deactivate an automation file trigger by providing its key. ## Required Scopes To update the status of a trigger request, your API user must have this permission: - Automation Write (automations_write) (PATCH /automation/v1/automations/filetrigger/key:{key}). Required: filetrigger_key.
list_all_automation_folders
Retrieve a list of all folders in the account. ## Required Scopes To retrieve automation folders, your API user must have this permission: - Automation Read (automations_read) (GET /automation/v1/folders). Required: filter.
create_automation_run_once
Run all activities in an automation one time by specifying its ID. ## Required Scopes To run the activities in an automation, your API user must have these permissions: - Automation Execute (automations_execute) (POST /automation/v1/automations/{id}/actions/runallonce). Required: automation_id.
create_automation_run_once_by_key
Run all activities in an automation one time by specifying its external key. ## Required Scopes To run the activities in an automation, your API user must have these permissions: - Automation Execute (automations_execute) (POST /automation/v1/automations/key:{key}/actions/runallonce). Required: automation_key.
create_a_salesforce_marketing_cloud_engagement_automation_start
Start an automation by providing its ID. Start a one-time run of an automation. In the request body, list the activities to include in the run by their IDs. To get the activity IDs, retrieve the automation (POST /automation/v1/automations/{id}/actions/start). Required: automation_id.
create_automation_starts_by_key
Start an automation by providing its external key. Identify the automation by its external key instead of its ID. The request body and the response are the same as for Start an automation (POST /automation/v1/automations/key:{key}/actions/start). Required: automation_key.
get_automation_trigger_status_by_id
Check the status for a specified Trigger API requestID. > Note > > To see the automation details, make sure that the request’s file details meet the criteria for exactly one automation trigger configuration. See _Salesforce Help_: Configure a Trigger Automation (GET /automation/v1/automations/trigger/status/{requestId}). Required: id.
create_automation_trigger_validation
Validate the settings for a new automation trigger. Check the settings for an automation trigger start source before you create the automation (POST /automation/v1/automations/trigger/validate).
create_automation_trigger_validations_by_id
Validate the trigger settings for an existing automation by providing its ID. Check updated settings for the trigger start source of an existing automation (POST /automation/v1/automations/trigger/validate/{id}). Required: validate_id.
create_automation_trigger_validations_by_key
Validate the trigger settings for an existing automation by providing its external key. Check updated settings for the trigger start source of an existing automation, identified by its external key. This operation performs the same checks as Validate an automation trigger by ID (POST /automation/v1/automations/trigger/validate/key:{key}). Required: validate_key.
create_automation_trigger
Start an automation that uses a trigger start source. When you upload a file, the Trigger API request passes the file details for Automation Studio to evaluate. You can queue a maximum of 200 Trigger requests at a time in each member ID (MID) (POST /automation/v1/automations/trigger).
update_automation_trigger_by_id
Activate or Deactivate an Automation Trigger. If no automation has the specified ID, or if the automation doesn’t use a trigger start source, the API returns a 404 response (PATCH /automation/v1/automations/trigger/{id}). Required: id.
automation_triggers_by_key_bulk_update
Activate or deactivate an automation trigger by providing the external key of the automation. Identify the automation by its external key instead of its ID. The request body and the response are the same as for Update automation trigger (PATCH /automation/v1/automations/trigger/key:{key}). Required: trigger_key.
list_all_salesforce_marketing_cloud_engagement_automations
Retrieve a list of all automations in the account. ## Required Scopes To retrieve the automations in your account, your API user must have this permission: - Automation Read (automations_read) (GET /automation/v1/automations). The connector pages through all results with $page and $pagesize.
create_a_salesforce_marketing_cloud_engagement_automation
Create an automation using existing Automation Studio activities. Each activity in steps has an objectTypeId that identifies the type of activity and an activityObjectId that identifies the activity to run (POST /automation/v1/automations).
get_automation_by_id
Retrieve a specific automation by providing its ID. Each activity in the steps array includes an objectTypeId that identifies the type of activity. For the list of activity types, see Automation Activity Types (GET /automation/v1/automations/{id}). Required: id.
update_a_salesforce_marketing_cloud_engagement_automation_by_id
Update an automation by providing its ID. Include only the properties that you want to change. If the automation is running, the API returns a 403 response. Updating an automation can assign new IDs to its activities, even when the request doesn’t include steps (PATCH /automation/v1/automations/{id}). Required: id.
list_all_automations_by_key
Retrieve a specific automation by providing its external key. Identify the automation by its external key instead of its ID. The request body and the response are the same as for Get an automation (GET /automation/v1/automations/key:{key}). Required: automation_key.
automations_by_key_bulk_update
Update an automation by providing its external key. Identify the automation by its external key instead of its ID. The request body and the response are the same as for Update an automation (PATCH /automation/v1/automations/key:{key}). Required: automation_key.
create_bulk_ingest_batch_completion
Complete data staging for a bulk data ingest job. ## Required Scopes To complete data staging for a bulk data ingest job, your API user must have this permission: - Automation Execute (automations_execute) (POST /data/v1/bulk/ingest/{bulkApiDefinitionId}/batches/complete). Required: bulk_api_definition_id.
bulk_ingest_batches_bulk_update
Stage data for a bulk data ingest job. Stage data to import in a bulk job. To complete a bulk ingestion job, you must use this resource to stage data at least one time. A data ingestionjob can include up to 1,000 staging requests (PUT /data/v1/bulk/ingest/{bulkApiDefinitionId}/batches). Required: bulk_api_definition_id.
create_a_salesforce_marketing_cloud_engagement_bulk_ingest_job
Create a bulk data ingestion job. You can create up to 100 jobs in 24 hours. When you create a job, the jobStatus is set to New, and changes to Staging when you stage data for the job (POST /data/v1/bulk/ingest).
delete_bulk_ingest_job_by_id
Delete the job definition of a bulk data ingest job. Deletes an active bulk data ingest job. When you delete a bulk data ingest job, all of the staged data for the job is deleted. You can only delete a job that has a status of New or Staging (DELETE /data/v1/bulk/ingest/{bulkApiDefinitionId}). Required: id.
get_bulk_ingest_job_by_id
Get the job definition of a bulk data ingest job. The response includes the status of the job and its creation and expiration dates (GET /data/v1/bulk/ingest/{bulkApiDefinitionId}). Required: id.
update_bulk_ingest_job_by_id
Update the job definition of a bulk data ingest job. You can change the data extension or the update type. Updating the job definition doesn’t reset the expiration time (PATCH /data/v1/bulk/ingest/{bulkApiDefinitionId}). Required: id.
list_all_bulk_ingest_summaries
Get a summary for a completed bulk data ingestion job. View a summary of a completed bulk data ingest job. ## Required Scopes To get the summary of a bulk data ingest job, your API user must have this permission: - Automation Read (automations_read) (GET /data/v1/bulk/ingest/{bulkApiDefinitionId}/summary). Required: bulk_api_definition_id.
list_all_bulk_ingest_validation_results
Get the validation results for a completed bulk data ingest job. ## Required Scopes To get the validation results of a bulk data ingest job, your API user must have this permission: - Automation Read (automations_read) (GET /data/v1/bulk/ingest/{bulkApiDefinitionId}/validation/result). The connector pages through all results with page and pageSize. Required: bulk_api_definition_id.
list_all_bulk_ingest_validation_summaries
Get the validation summary of a bulk data ingest job. Get a validation summary for a completed bulk data ingest job. ## Required Scopes To get the validation summary of a bulk data ingest job, your API user must have this permission: - Automation Read (automations_read) (GET /data/v1/bulk/ingest/{bulkApiDefinitionId}/validation/summary). Required: bulk_api_definition_id.
list_all_salesforce_marketing_cloud_engagement_campaign_assets
Retrieve a list of assets that are associated with a campaign. Required permission scope: Campaign > Read (GET /hub/v1/campaigns/{id}/assets). Required: campaign_id.
create_a_salesforce_marketing_cloud_engagement_campaign_asset
Associate an asset with a campaign. Required permission scope: Campaign > Write (POST /hub/v1/campaigns/{id}/assets). Required: campaign_id.
get_campaign_asset_by_id
Retrieve information about a specific asset that is associated with a campaign. Required permission scope: Campaign > Read (GET /hub/v1/campaigns/{id}/assets/{assetId}). Required: campaign_id, id.
delete_campaign_asset_by_id
Remove an association between an asset and a campaign. Required permission scope: Campaign > Write (DELETE /hub/v1/campaigns/{id}/assets/{assetId}). Required: campaign_id, id.
list_all_salesforce_marketing_cloud_engagement_campaigns
Retrieve a list of campaigns in your account. Required permission scope: Campaign > Read (GET /hub/v1/campaigns/). The connector pages through all results with $page and $pageSize.
create_a_salesforce_marketing_cloud_engagement_campaign
Create a campaign. Required permission scope: Campaign > Write (POST /hub/v1/campaigns/).
get_single_salesforce_marketing_cloud_engagement_campaign_by_id
Retrieve information about a single campaign. Required permission scope: Campaign > Read (GET /hub/v1/campaigns/{id}). Required: id.
update_a_salesforce_marketing_cloud_engagement_campaign_by_id
Update a campaign. Required permission scope: Campaign > Write (PATCH /hub/v1/campaigns/{id}). Required: id.
delete_a_salesforce_marketing_cloud_engagement_campaign_by_id
Delete a campaign. Required permission scope: Campaign > Write (DELETE /hub/v1/campaigns/{id}). Required: id.
create_contact_address_count
Get Contact count based on search criteria (POST /contacts/v1/addresses/count).
create_contact_address_search
Fetches all contacts and associated addresses based on search criteria (POST /contacts/v1/addresses/search/{attributeName}). Required: attribute_name.
create_contact_attribute_group_population
Creates a population within Contact Builder (POST /contacts/v1/attributeGroups/population).
list_all_contact_attribute_groups
Retrieves all attribute groups associated with a specified contact data schema (GET /contacts/v1/schemas/{schemaId}/attributeGroups). Required: schema_id.
get_contact_attribute_group_by_id
Retrieves a specified attribute group (by ID, key, or name) associated with a specified contact data schema (GET /contacts/v1/schemas/{schemaId}/attributeGroups/{id}). Required: schema_id, id. To use the external key instead of the ID, pass key:
list_all_contact_attribute_set_definitions
Get All Attribute Set Definitions (GET /contacts/v1/attributeSetDefinitions).
get_contact_attribute_set_definition_by_id
Get Attribute Set Definitions by ID (GET /contacts/v1/attributeSetDefinitions/{id}). Required: id.
create_contact_attribute_set
Inserts a collection of attribute value containers or the data rows of a specified attribute set by ID or name (POST /contacts/v1/attributeSets/{id}). Required: attribute_set_id.
update_contact_attribute_set_by_id
Update Attribute Values by ID (PATCH /contacts/v1/attributeSets/{id}). Required: id.
list_all_contact_attribute_sets_by_name
Search Attribute Sets by Name (GET /contacts/v1/attributeSets/name:{name}). Required: attribute_set_name.
create_contact_delete_operation_retry
Retry failed contact delete operation (POST /contacts/v1/operations/delete/{operationID}/retry). Required: operation_id.
list_all_contact_delete_operations
Retrieves the list of contact delete operations (GET /contacts/v1/contacts/deleteOperations).
list_all_contact_delete_request_summaries
Retrieves a summary of contact delete requests for a date range (GET /contacts/v1/contacts/analytics/deleterequests/summary). Required: startdateutc, enddateutc.
list_all_contact_delete_requests
Get Contact Delete Requests Details (GET /contacts/v1/contacts/analytics/deleterequests). The connector pages through all results with $page and $pagesize. Required: startdateutc, enddateutc.
create_contact_deletion_option
Retrieves delete options based on the specified parameters. You must provide a context request body for this resource, but all listed parameters are optional (POST /contacts/v1/contacts/actions/delete/options).
create_contact_deletion_setting
Sets the configuration settings for the Contact Delete framework and components (POST /contacts/v1/contacts/actions/delete/configSettings).
list_all_contact_deletion_statuses
Retrieves status of contact deletion operation (GET /contacts/v1/contacts/actions/delete/status). Required: operationID.
create_a_salesforce_marketing_cloud_engagement_contact_deletion
Delete Contacts by ID (POST /contacts/v1/contacts/actions/delete). Required: type.
create_contact_email_search
Get Contact Key for Email Addresses (POST /contacts/v1/addresses/email/search).
create_contact_establishment
Get or Create Contacts by Key and Type (POST /contacts/v1/establish).
create_contact_preference_search
Searches for consent management information in contact records by reference type. For best performance, use batches of contact ID values whenever possible (POST /contacts/v1/contacts/preferences/search). Required: ReferenceType.
create_contact_preference
Adds consent management information to contact records for data protection and privacy concerns. The request can include multiple contact IDs in a single JSON payload (POST /contacts/v1/contacts/preferences).
create_contact_preferences_by_id
Add Contact Preferences by Contact ID (POST /contacts/v1/contacts/id:{contactId}/Preferences). Required: contact_id.
list_all_contact_preferences_by_id
Retrieves consent management information from contact records by contact ID for data protection and privacy concerns (GET /contacts/v1/contacts/id:{contactId}/Preferences). Required: contact_id.
list_all_contact_preferences_by_key
Retrieves consent management information from contact records by contact key. GET requests might display values that are reserved for future use and don’t perform any actions at this time (GET /contacts/v1/contacts/key:{contactKey}/Preferences). Required: contact_key.
create_contact_restrict_operation_retry
Retry failed contact restrict operation (POST /contacts/v1/operations/restrict/{operationID}/retry). Required: operation_id.
list_all_contact_restriction_statuses
Retrieves the status of the contact restrict operation (GET /contacts/v1/contacts/actions/restrict/status). Required: operationID.
create_contact_restriction
Restricts processing for contacts identified by ContactID values in the request. This operation runs asynchronously. Use the OperationID value returned to check the status of the delete (POST /contacts/v1/contacts/actions/restrict). Required: type.
list_all_salesforce_marketing_cloud_engagement_contact_schemas
Retrieves the collection of all contact data schemas contained in the current account (GET /contacts/v1/schema).
create_a_salesforce_marketing_cloud_engagement_contact
Creates a new contact with the specified information in the specified attribute groups (POST /contacts/v1/contacts).
salesforce_marketing_cloud_engagement_contacts_bulk_update
Update Contacts (PATCH /contacts/v1/contacts).
create_data_extension_clear
Deletes all of the data in a data extension. ## Required Scopes To retrieve data extensions in your account, your API user must have this permission: - Data Write (data_extensions_write) (POST /data/v1/customobjects/{id}/cleardata). Required: data_extension_id.
data_extension_column_increments_bulk_update
Increase or decrease the value of a data extension column synchronously. For example, you can use this operation to update a customer’s loyalty reward point value after they make a purchase (PUT /hub/v1/dataevents/{dataExtensionId}/rows/{primaryKey}:{primaryKeyValue}/column/{column}/increment). Required: step, data_extension_id, primary_key, primary_key_value, column.
data_extension_column_increments_by_key_bulk_update
Increase or decrease the value of a data extension column synchronously. For example, you can use this operation to update a customer’s loyalty reward point value after they make a purchase (PUT /hub/v1/dataevents/key:{externalKey}/rows/{primaryKey}:{primaryKeyValue}/column/{column}/increment). Required: step, external_key, primary_key, primary_key_value, column.
list_all_data_extension_contact_usages
Retrieves information about whether the contact model for an account uses the custom object (GET /contacts/v1/customObject/{id}/isUsedInContacts). Required: custom_object_id.
list_all_data_extension_data
Retrieve data from a data extension by providing its ID (GET /data/v1/customobjectdata/{id}/rowset). The connector pages through all results with $page and $pagesize. Required: data_extension_data_id.
list_all_data_extension_data_by_key
Retrieve data from a data extension by providing its external key (GET /data/v1/customobjectdata/key/{key}/rowset). The connector pages through all results with $page and $pagesize. Required: key_key.
list_all_data_extension_data_by_token
Retrieve data from a data extension by providing the request token. The $filter, $pagesize, $top, $fields, and $orderby parameters persist from the original query and can’t be specified. To (GET /data/v1/customobjectdata/token/{token}/rowset). The connector pages through all results with $page. Required: token.
list_all_data_extension_field_relationships
Retrieves relationship details for a customobjectfield that is registered in the contacts model (GET /contacts/v1/customobjectfield/{id}/relationships). Required: customobjectfield_id.
list_all_data_extension_fields
Retrieves a list of fields in a data extension. ## Required Scopes To retrieve data extensions in your account, your API user must have this permission: - Data Read (data_extensions_read) (GET /data/v1/customobjects/{id}/fields). Required: data_extension_id.
data_extension_fields_async_bulk_update
Updates a field in a data extension.
To execute this operation, you must have the Data Extensions | Write permission (PATCH /data/v1/customobjectsasync/{id}/fields). Required: data_extensions_async_id.
create_data_extension_fields_async
Inserts a new field into a data extension. ## Required Scopes To retrieve data extensions in your account, your API user must have this permission: - Data Write (data_extensions_write) (POST /data/v1/customobjectsasync/{id}/fields). Required: data_extensions_async_id.
data_extension_row_upserts_bulk_update
Upsert one row in a data extension synchronously by specifying the ID of the target data extension. Specify the primary key and value in the URL path (PUT /hub/v1/dataevents/{dataExtensionId}/rows/{primaryKey}:{primaryKeyValue}). Required: data_extension_id, primary_key, primary_key_value.
data_extension_row_upserts_by_key_bulk_update
Upsert one row in a data extension synchronously by specifying the external key of the target data extension. The API doesn’t accept URLs that contain more than 260 characters. Because character-encoding changes can make URLs longer than expected, we recommend that you limit the length of URLs to 200 characters (PUT /hub/v1/dataevents/key:{externalKey}/rows/{primaryKey}:{primaryKeyValue}). Required: external_key, primary_key, primary_key_value.
create_data_extension_rows_async
Add rows to a data extension asynchronously. For information about the limits that apply to this API, see _Salesforce Help_: [Limits and Guidelines]( (POST /data/v1/async/dataextensions/key:{externalKey}/rows). Required: external_key.
data_extension_rows_async_bulk_update
Asynchronously update rows in a data extension if the primary key exists, or create rows if the primary key doesn't exis. For information about the limits that apply to this API, see _Salesforce Help_: [Limits and Guidelines]( (PUT /data/v1/async/dataextensions/key:{externalKey}/rows). Required: external_key.
create_data_extension_rowset
Upsert one or more rows in a data extension synchronously by specifying the ID of the target data extension (POST /hub/v1/dataevents/{dataExtensionId}/rowset). Required: data_extension_id.
create_data_extension_rowsets_by_key
Upsert one or more rows in a data extension synchronously by specifying the external key of the target data extension (POST /hub/v1/dataevents/key:{externalKey}/rowset). Required: external_key.
list_all_salesforce_marketing_cloud_engagement_data_extensions
Retrieves a list of data extensions that match a search string. ## Required Scopes To retrieve data extensions in your account, your API user must have this permission: - Data Read (data_extensions_read) (GET /data/v1/customobjects). The connector pages through all results with $page and $pagesize. Required: search.
create_a_salesforce_marketing_cloud_engagement_data_extension
Creates a data extension. ## Required Scopes To retrieve data extensions in your account, your API user must have this permission: - Data Write (data_extensions_write) (POST /data/v1/customobjects).
delete_data_extension_by_id
Deletes a data extension. ## Required Scopes To retrieve data extensions in your account, your API user must have this permission: - Data Write (data_extensions_write) (DELETE /data/v1/customobjects/{id}). Required: id.
get_data_extension_by_id
Retrieves information about the specified data extension by providing its ID. ## Required Scopes To retrieve data extensions in your account, your API user must have this permission: - Data Read (data_extensions_read) (GET /data/v1/customobjects/{id}). Required: id.
update_data_extension_by_id
Update the fields in a data extension. ## Required Scopes To retrieve data extensions in your account, your API user must have this permission: - Data Write (data_extensions_write) (PATCH /data/v1/customobjects/{id}). Required: id.
get_data_extensions_by_category_by_id
Retrieves a list of data extensions based on the ID of the parent category. ## Required Scopes To retrieve data extensions in your account, your API user must have this permission: - Data Read (data_extensions_read) (GET /data/v1/customobjects/category/{categoryId}). Required: id.
create_domain_bulk_insert
Create domains in bulk. Creates multiple sender email address records. The specified notification email address receives an email when all of the email address records have been created. Required permission scope: Email | Write (POST /messaging/v1/domainverification/bulk/insert).
create_a_salesforce_marketing_cloud_engagement_domain_deletion
Delete an address or domain. Deletes an email address or domain record. Required permission scope: Email | Write (POST /messaging/v1/domainverification/delete).
create_a_salesforce_marketing_cloud_engagement_domain_push
Push registered domains to other business units. Makes one or more registered domains available in other business units (BUs) that share an Enterprise ID (EID). Required permission scope: Email | Write (POST /messaging/v1/domainverification/push).
create_domain_registration
Register an email domain. Registers a new domain to use for sending email. If the API accepts your request, it outputs a unique token (POST /messaging/v1/domainverification/register).
create_a_salesforce_marketing_cloud_engagement_domain_update
Update an address or domain. Updates the status of the IsSendable field for an email address or domain record. Required permission scope: Email | Write (POST /messaging/v1/domainverification/update).
create_domain_verification_token
Retrieve a domain verification token. Retrieves a verification token for a domain. If the DNS configuration of the domain contains a TXT record that has a value equal to this token, the status of the domain changes to verified (POST /messaging/v1/domainverification/verify).
list_all_salesforce_marketing_cloud_engagement_domains
Get domains. Retrieves a list of email addresses and domains that can be used to send email from a Marketing Cloud Engagement account. This operation returns both verified and unverified addresses and domains (GET /messaging/v1/domainverification). The connector pages through all results with $page and $pageSize.
create_a_salesforce_marketing_cloud_engagement_domain
Create a domain. Creates an email or domain record. When you create a record, Marketing Cloud Engagement sends a verification email. Required permission scope: Email | Write (POST /messaging/v1/domainverification).
create_email_address_validation
Validates an email address. Processes an email address through one or more validators. This operation can perform three types of validation: - SyntaxValidator: Validates that the email address includes a name, an at sign (@), and a domain (POST /address/v1/validateEmail).
encryption_key_rotations_bulk_update
Queue the rotation of an encryption key (PUT /platform/v1/dataencryption/rotateasync).
list_all_encryption_key_types
Retrieves information about the key types and key lengths that your account supports. To retrieve this information, the data at rest encryption feature must be enabled for your account (GET /platform/v1/key/type).
list_all_salesforce_marketing_cloud_engagement_encryption_keys
Retrieve all of the encryption keys associated with an account. To retrieve this data, the data at rest encryption feature must be enabled for your account (GET /platform/v1/key).
create_a_salesforce_marketing_cloud_engagement_encryption_key
Creates or imports an encryption key. To create a key, the data at rest encryption feature must be enabled for your account. Contact your account executive for more information about enabling Data at (POST /platform/v1/key).
get_encryption_key_by_id
Retrieve an existing encryption key by providing its ID (GET /platform/v1/key/{keyId}). Required: id.
delete_encryption_key_by_id
Deletes an encryption key (DELETE /platform/v1/key/{keyId}). Required: id.
event_callback_signature_keys_bulk_update
Regenerate Signature Key (PUT /platform/v1/ens-regenerate).
create_event_callback_verification
Verify Callback (POST /platform/v1/ens-verify).
create_a_salesforce_marketing_cloud_engagement_event_callback
Create Callback (POST /platform/v1/ens-callbacks).
delete_event_callback_by_id
Deletes a registered callback that isn’t used by any subscriptions. Delete all subscriptions for the callback before deleting the callback (DELETE /platform/v1/ens-callbacks/{callbackId}). Required: id.
list_all_salesforce_marketing_cloud_engagement_event_callbacks
Get All Callbacks (GET /platform/v1/ens-callbacks).
get_event_callback_by_id
Retrieves details about a registered callback (GET /platform/v1/ens-callbacks/{callbackId}). Required: id.
event_callbacks_bulk_update
Updates a registered callback. It can take up to two minutes for callback changes to become active (PUT /platform/v1/ens-callbacks).
create_event_subscription
Create Subscription (POST /platform/v1/ens-subscriptions).
delete_event_subscription_by_id
Deletes a subscription (DELETE /platform/v1/ens-subscriptions/{subscriptionId}). Required: id.
get_event_subscription_by_id
Retrieves details for a subscription (GET /platform/v1/ens-subscriptions/{subscriptionId}). Required: id.
event_subscriptions_bulk_update
Updates a single subscription. To pause an active subscription, set the status request parameter to paused. To unpause a paused subscription, set the status request parameter to active (PUT /platform/v1/ens-subscriptions).
get_event_subscriptions_by_callback_by_id
Retrieves details for all subscriptions associated with a callback (GET /platform/v1/ens-subscriptions-by-cb/{callbackId}). Required: id.
list_all_file_transfer_activities
Retrieve a list of all file transfer activities in the account (GET /automation/v1/fileTransfers). The connector pages through all results with $page and $pagesize.
create_file_transfer_activity
Create a file transfer activity (POST /automation/v1/fileTransfers).
delete_file_transfer_activity_by_id
Delete a specific file transfer activity by providing its ID (DELETE /automation/v1/fileTransfers/{fileTransferActivityId}). Required: id.
get_file_transfer_activity_by_id
Retrieve a specific file transfer activity by providing its ID (GET /automation/v1/fileTransfers/{fileTransferActivityId}). Required: id.
update_file_transfer_activity_by_id
Update a file transfer activity by providing its ID (PATCH /automation/v1/fileTransfers/{fileTransferActivityId}). Required: id.
create_file_transfer_activity_start
Add a file transfer activity to the queue for processing (POST /automation/v1/fileTransfers/{fileTransferActivityId}/start). Required: file_transfer_activity_id.
create_file_transfer_location_validation
Validate a file transfer location schema passed in request body. This method validates a file location. For each of the types, parameters differ slightly, with differences shown below. ## Required Scopes Installed Packages > Data > File Locations > Write Scope: 'file_locations_write'; (POST /data/v1/filetransferlocation/validate).
get_file_transfer_location_by_id
Get a file transfer location identified by customerKey. This method returns a single file location for the given customer key. ## Required Scopes Installed Packages > Data > File Locations > Read Scope: 'file_locations_read'; (GET /data/v1/filetransferlocation/{customerkey}). Required: id.
update_file_transfer_location_by_id
Update a file transfer location identified by customerKey. This method updates a file location based on a given customer key. ## Required Scopes Installed Packages > Data > File Locations > Write Scope: 'file_locations_write'; (PATCH /data/v1/filetransferlocation/{customerkey}). Required: id.
delete_file_transfer_location_by_id
Deactivate a file transfer location identified by customerKey. This method deactivates a file location based on a given customer key. ## Required Scopes Installed Packages > Data > File Locations > Write Scope: 'file_locations_write'; (DELETE /data/v1/filetransferlocation/{customerkey}). Required: id.
list_all_file_transfer_locations
Get all file transfer locations for the current MID. This method returns one or more file locations that are owned by, or reside under your member identification code (MID). A file location is also known as a fileTransferLocation (GET /data/v1/filetransferlocations). The connector pages through all results with $page and $pagesize.
create_file_transfer_location
Create a new File Transfer Location in your account. This method creates a new file location. For each of the types, parameters differ slightly, with differences shown below (POST /data/v1/filetransferlocation).
list_all_salesforce_marketing_cloud_engagement_ftp_locations
Retrieve a list of all FTP locations in the account. ## Required Scopes To retrieve FTP locations, your API user must have this permission: - Automation Read (automations_read) (GET /automation/v1/ftpLocations).
list_all_salesforce_marketing_cloud_engagement_import_summaries
Returns the status of a queued data import, including the final number of imported rows and the import status (Success or Error) (GET /data/v1/async/import/{id}/summary). Required: import_id.
list_all_import_validation_results
Get import row-level validation details by ID. Returns details of row-level validation errors that occurred during an import. Use this method after the import job finishes to see how many rows failed to import (GET /data/v1/async/import/{id}/validationresult). Required: import_id.
list_all_import_validation_summaries
Retrieve a list of row-level validation errors that occurred during an import. Use this method after an import finishes to see the total number of failed rows (GET /data/v1/async/import/{id}/validationsummary). Required: import_id.
create_a_salesforce_marketing_cloud_engagement_import
Queue and start a one-time import into a data extension without creating an import definition. Perform a file-based import without creating an import definition. Store the source file in an active file transfer location, or provide a pre-signed URL (POST /data/v1/async/import).
list_all_journey_api_routes
Retrieves the discovery document for the collection of journey resources. To call this resource, assign your API Integration the Automation Read scope (GET /interaction/v1/rest).
list_all_journey_async_event_statuses
Get Status of Async Journey Insertion Request (GET /interaction/v1/async/events/status). The connector pages through all results with $page and $pageSize.
create_journey_async_event
Insert Contacts into a Journey Asynchronously (POST /interaction/v1/async/events).
list_all_salesforce_marketing_cloud_engagement_journey_audits
Get Journey Audit Logs by ID (GET /interaction/v1/interactions/{id}/audit/{action}). The connector pages through all results with $page and $pageSize. Required: journey_id, action.
list_all_journey_audits_by_key
Get Journey Audit Logs by Key (GET /interaction/v1/interactions/key:{key}/audit/{action}). The connector pages through all results with $page and $pageSize. Required: journey_key, action.
create_journey_contact_exit_status
Returns the status of a request to remove a contact from a journey or from one or more versions of a journey (POST /interaction/v1/interactions/contactexit/status).
create_journey_contact_exit
Removes up to 50 contacts from a journey or from one or more versions of a journey (POST /interaction/v1/interactions/contactexit).
create_journey_contact_membership
Get List of Journeys the Contact is in (POST /interaction/v1/interactions/contactMembership).
create_journey_event_definition
Create Event Definition (POST /interaction/v1/eventDefinitions).
delete_journey_event_definition_by_id
Deletes an individual event definition by ID or key (DELETE /interaction/v1/eventDefinitions/{id}). Required: id. To use the external key instead of the ID, pass key:
get_journey_event_definition_by_id
Retrieves an individual event definition by ID or key (GET /interaction/v1/eventDefinitions/{id}). Required: id. To use the external key instead of the ID, pass key:
list_all_journey_event_definitions
Retrieves a collection of event definitions (GET /interaction/v1/eventDefinitions). The connector pages through all results with $page and $pageSize.
update_journey_event_definition_by_id
Update Event definition By Id (PUT /interaction/v1/eventDefinitions/{id}). Required: id. To use the external key instead of the ID, pass key:
create_a_salesforce_marketing_cloud_engagement_journey_event
Fire the Event (POST /interaction/v1/events).
create_journey_history_download
Download Journey History (POST /interaction/v1/interactions/journeyhistory/download).
create_journey_history_estimate
Get Journey History Download Estimate (POST /interaction/v1/interactions/journeyhistory/estimate).
list_all_journey_history_freshness
Get Journey History Download Freshness (GET /interaction/v1/interactions/journeyhistory/freshness).
create_a_salesforce_marketing_cloud_engagement_journey_pause
Pause a Journey by Definition ID (POST /interaction/v1/interactions/pause/{definitionID}). Required: definition_id.
create_journey_pauses_by_key
Pause a Journey by Definition Key (POST /interaction/v1/interactions/pause/key:{definitionKey}). Required: definition_key.
create_journey_publication
Publishes a journey version asynchronously. To call this resource, assign your API Integration the Automation Read scope (POST /interaction/v1/interactions/publishAsync/{id}). Required: versionNumber, publish_async_id.
get_journey_publish_status_by_id
Get Publish Status (GET /interaction/v1/interactions/publishStatus/{statusId}). Required: id.
create_a_salesforce_marketing_cloud_engagement_journey_resume
Resumes the paused journey that matches the specified definitionID (POST /interaction/v1/interactions/resume/{definitionID}). Required: versionNumber, definition_id.
create_journey_resumes_by_key
Resumes the paused journey that matches the specified definitionKey (POST /interaction/v1/interactions/resume/key:{definitionKey}). Required: versionNumber, definition_key.
create_a_salesforce_marketing_cloud_engagement_journey_stop
Stops a running journey. To call this resource, assign your API Integration the Automation Read scope (POST /interaction/v1/interactions/stop/{definitionId}). Required: versionNumber, definition_id.
delete_a_salesforce_marketing_cloud_engagement_journey_by_id
Deletes a journey by ID or key. When deleting last version of a journey, check if the journey is associated with a tag and unassociated the tag using the deleteTags resource (DELETE /interaction/v1/interactions/{id}). Required: id. To use the external key instead of the ID, pass key:
get_single_salesforce_marketing_cloud_engagement_journey_by_id
Retrieves a single journey by ID or key. To call this resource, assign your API Integration the Automation Read scope (GET /interaction/v1/interactions/{id}). Required: id. To use the external key instead of the ID, pass key:
list_all_salesforce_marketing_cloud_engagement_journeys
Search Journeys (GET /interaction/v1/interactions). The connector pages through all results with $page and $pageSize.
create_a_salesforce_marketing_cloud_engagement_journey
Creates or saves a journey. To create a new journey provide the request body in the appropriate Journey Specification (POST /interaction/v1/interactions).
salesforce_marketing_cloud_engagement_journeys_bulk_update
Update Journey Version (PUT /interaction/v1/interactions).
create_object_tag_deletion
Delete Tags (POST /hub/v1/objects/{objectTypeName}/tags/delete). Required: object_type_name.
create_a_salesforce_marketing_cloud_engagement_object_tag
Create Tags (POST /hub/v1/objects/{objectTypeName}/tags/). Required: object_type_name.
get_ott_media_download_by_id
Download rich media inbound messages using the media 'id' received in the ENS notification (GET /ott/v1/media/download/{mediaId}). Required: id.
create_a_salesforce_marketing_cloud_engagement_ott_registration
Register OTT Property (POST /ott/v1/registration).
list_all_salesforce_marketing_cloud_engagement_ott_registrations
Retrieves paginated collection of registered OTT properties by OTT Platform (GET /ott/v1/registration/{platform}). The connector pages through all results with $page and $pagesize. Required: platform.
get_ott_registration_by_id
Retrieves information about a registered OTT property by Platform and ID (GET /ott/v1/registration/{platform}/{ottPropertyId}). Required: platform, id.
get_single_salesforce_marketing_cloud_engagement_ott_send_by_id
Retrieves all the information about an existing OTT send message request (GET /ott/v1/send/{messageId}). Required: id.
create_a_salesforce_marketing_cloud_engagement_ott_send
Send Message to Recipient (POST /ott/v1/send).
list_all_platform_endpoints
Retrieve a list of endpoints for Marketing Cloud Engagement services, such as the authentication, REST API, SOAP API, and FTP servers (GET /platform/v1/endpoints).
get_platform_endpoint_by_id
Retrieve an endpoint URL for a specific service, such as REST or SOAP API (GET /platform/v1/endpoints/{endpointType}). Required: id.
get_push_app_send_delivery_by_id
Retrieve the status of push messages that were sent to users of an app (GET /push/v1/messageApp/{messageId}/deliveries/{tokenId}). Required: message_id, id.
create_a_salesforce_marketing_cloud_engagement_push_app_send
Broadcast a push message to all users of a push-enabled app (POST /push/v1/messageApp/{messageId}/send). Required: message_id.
list_all_push_application_keys
Retrieve a list of custom keys for an app (GET /push/v1/application/{appId}/key). Required: app_id.
push_application_keys_bulk_update
Update the custom keys for an app. When you update the keys for an app, the existing keys are removed and replaced with the keys specified in the request (PUT /push/v1/application/{appId}/key). Required: app_id.
push_application_keys_bulk_delete
Delete the custom keys for an app. A successful deletion request removes all of the keys for the app (DELETE /push/v1/application/{appId}/key). Required: app_id.
delete_push_application_key_by_id
Delete a specific app key by specifying its value (DELETE /push/v1/application/{appId}/key/{key}). Required: app_id, id.
list_all_salesforce_marketing_cloud_engagement_push_applications
Retrieve a list of all applications in an account (GET /push/v1/application).
get_push_application_by_id
Retrieve information about a specific app by providing its ID (GET /push/v1/application/{appId}). Required: id.
create_a_salesforce_marketing_cloud_engagement_push_batch_send
Send a batch of push messages to specific users by specifying tags or device tokens (POST /push/v1/messageBatch/{messageid}/send). Required: message_id.
get_push_contact_send_delivery_by_id
Retrieve the status of push messages that were sent to specific users of a mobile app (GET /push/v1/messageContact/{messageId}/deliveries/{tokenId}). Required: message_id, id.
create_a_salesforce_marketing_cloud_engagement_push_contact_send
Send a push message to specific users of an app by specifying their device tokens or subscriber keys (POST /push/v1/messageContact/{messageId}/send). Required: message_id.
get_push_list_refresh_status_by_id
Retrieve the status of a MobilePush list refresh request (GET /push/v1/contacts/refreshList/{listId}/status/{tokenId}). Required: list_id, id.
create_a_salesforce_marketing_cloud_engagement_push_list_refresh
Refresh a list of recipients in MobilePush. This POST request doesn’t require a request body (POST /push/v1/contacts/refreshList/{listId}). Required: list_id.
get_push_list_send_delivery_by_id
Retrieve the status of push messages that were sent to contacts who are on a MobilePush list (GET /push/v1/messageList/{messageId}/deliveries/{tokenId}). Required: message_id, id.
create_a_salesforce_marketing_cloud_engagement_push_list_send
Send a push message to all contacts in a MobilePush list (POST /push/v1/messageList/{messageId}/send). Required: message_id.
list_all_salesforce_marketing_cloud_engagement_push_locations
Retrieve all locations in your account (GET /push/v1/location). The connector pages through all results with $page and $pageSize.
create_a_salesforce_marketing_cloud_engagement_push_location
Create a new geofenced or beacon-based location (POST /push/v1/location).
get_push_location_by_id
Retrieve details of a specific location (GET /push/v1/location/{locationId}). Required: id.
update_push_location_by_id
Modify the details of an existing location (PUT /push/v1/location/{locationId}). Required: id.
delete_push_location_by_id
Delete a specific location by providing its ID (DELETE /push/v1/location/{locationId}). Required: id.
list_all_salesforce_marketing_cloud_engagement_push_messages
Retrieve all push messages in your account.
To execute this operation, you must have the Channels Read permission (GET /push/v1/message). The connector pages through all results with $page and $pageSize.
create_a_salesforce_marketing_cloud_engagement_push_message
Create a push message.
To execute this operation, you must have the Channels Write permission (POST /push/v1/message).
get_push_message_by_id
Retrieves a single push message in your account (GET /push/v1/message/{messageId}). Required: id.
update_push_message_by_id
Update the content or details of a push message (PUT /push/v1/message/{messageId}). Required: id.
delete_push_message_by_id
Delete a push message in your account (DELETE /push/v1/message/{messageId}). Required: id.
get_push_tag_send_delivery_by_id
Retrieve the status of push messages that were sent to contacts based on their tags (GET /push/v1/messageTag/{messageId}/deliveries/{tokenId}). Required: message_id, id.
create_a_salesforce_marketing_cloud_engagement_push_tag_send
Send a push message to all users of a push-enabled app who have specific tags. The request body must include the inclusionTags or exclusionTags array, or both (POST /push/v1/messageTag/{messageId}/send). Required: message_id.
list_all_salesforce_marketing_cloud_engagement_script_activities
Retrieve a list of automation script activities. ## Required Scopes To retrieve script activities, your API user must have this permission: - Automation Read (scripts_read) (GET /automation/v1/scripts). The connector pages through all results with $page and $pagesize.
create_script_activity_start
Run a script activity one time. ## Required Scopes To run a script activity, your API user must have this permission: - Automation Write (automations_write) (POST /automation/v1/scripts/{ssjsId}/start). Required: ssjs_id.
list_all_salesforce_marketing_cloud_engagement_security_events
GET /data/v1/audit/securityEvents. Retrieve logged Audit Trail security events for the current account and its children. Logins are audited at the enterprise level. Timestamps for Audit Trail data use the US Central Standard Time (GMT-6, CST) timezone (GET /data/v1/audit/securityEvents). The connector pages through all results with $page and $pagesize.
delete_security_header_by_id
Delete all the security headers applied to either a business unit’s SAP-branded view or click domain (DELETE /messaging/v1/securityHeaders/{pageType}). Required: id.
list_all_salesforce_marketing_cloud_engagement_security_headers
Get a list of the security headers applied to a business unit’s SAP-branded view and click domains (GET /messaging/v1/securityHeaders).
create_a_salesforce_marketing_cloud_engagement_security_header
Update HTTP Headers (POST /messaging/v1/securityHeaders).
list_all_security_headers_all_pages
Get the list of all available security headers with their default values (GET /messaging/v1/securityHeaders/all).
list_all_salesforce_marketing_cloud_engagement_seed_list_account
Reads account data for a seed-list. The MID is used from authentication. Returns the partner list and auto-seed options that are in place for the MID (GET /messaging/v1/email/seed-list-account).
seed_list_account_bulk_update
Update account data for a seed-list. The MID is used from authentication. This method returns the partner list and auto-seed options that are in place for the MID as a result of this transaction (PUT /messaging/v1/email/seed-list-account).
create_a_salesforce_marketing_cloud_engagement_seed_list
Creates a seed-list for an account. The MID and Partner AppId is used from authentication. There’s a retention period of 60 days for the seed-list (POST /messaging/v1/email/seed-lists/).
delete_a_salesforce_marketing_cloud_engagement_seed_list_by_id
Delete a Seed-List (DELETE /messaging/v1/email/seed-lists/{id}). Required: id.
list_all_salesforce_marketing_cloud_engagement_seed_lists
Read all seed lists for an account. The MID and partner appId are used from authentication. The View user permission is required (GET /messaging/v1/email/seed-lists).
get_single_salesforce_marketing_cloud_engagement_seed_list_by_id
Read a single seed list for an account. The MID and partner appId is used from authentication. Ensure the MID is activated for MCSeedList (GET /messaging/v1/email/seed-lists/{id}). Required: id.
update_a_salesforce_marketing_cloud_engagement_seed_list_by_id
Update a single seed list for an account. The MID and partner appId are used from authentication. The {id} in the URL path is the globally unique ID assigned by the system at creation. A seed-list is retained for 60 days (PUT /messaging/v1/email/seed-lists/{id}). Required: id.
get_sms_contact_import_status_by_id
Retrieves the status of an import job (GET /sms/v1/contacts/queueImport/{id}/status/{tokenId}). Required: queue_import_id, id.
create_sms_contact_import
Queues a contact import (POST /sms/v1/contacts/queueImport/{id}). Required: queue_import_id.
get_sms_contact_send_delivery_by_id
Get Message Contact Status (GET /sms/v1/messageContact/{messageId}/deliveries/{tokenId}). Required: message_id, id.
get_sms_contact_send_history_by_id
Retrieves the last message sent to a mobile number (GET /sms/v1/messageContact/{messageId}/history/{tokenId}/mobileNumber/{mobileNumber}). Required: message_id, token_id, id.
create_a_salesforce_marketing_cloud_engagement_sms_contact_send
Initiates a message to one or more mobile numbers (POST /sms/v1/messageContact/{id}/send). Required: message_contact_id.
create_sms_import_send_delivery_report
Create ImportSend Delivery Report (POST /sms/v1/automation/importSend/{id}/deliveryReport). Required: import_send_id.
list_all_sms_import_send_statuses
Retrieves the status of a ImportSend automation (GET /sms/v1/automation/importSend/{tokenid}/status). Required: token_id.
create_a_salesforce_marketing_cloud_engagement_sms_import_send
Imports the contact file and data extension, and then sends the message. This API is only supported for Outbound Message template (POST /sms/v1/automation/importSend).
create_a_salesforce_marketing_cloud_engagement_sms_keyword
Creates a keyword on an account (POST /sms/v1/keyword).
delete_a_salesforce_marketing_cloud_engagement_sms_keyword_by_id
Deletes a keyword on an account given a keyword Id (DELETE /sms/v1/keyword/{keywordId}). Required: id.
sms_keywords_by_long_code_bulk_delete
Deletes a keyword on an account given a keyword and long code (DELETE /sms/v1/keyword/{keyword}/{longCode}). Required: keyword, long_code.
sms_keywords_by_short_code_bulk_delete
Deletes a keyword on an account given a keyword, short code, and country code (DELETE /sms/v1/keyword/{keyword}/{shortCode}/{countryCode}). Required: keyword, short_code, country_code.
get_sms_list_refresh_status_by_id
Get Refresh List Status (GET /sms/v1/contacts/refreshList/{id}/status/{tokenId}). Required: refresh_list_id, id.
create_a_salesforce_marketing_cloud_engagement_sms_list_refresh
Refreshes a list (POST /sms/v1/contacts/refreshList/{id}). Required: refresh_list_id.
get_sms_list_send_delivery_by_id
Get Message List Status (GET /sms/v1/messageList/{id}/deliveries/{tokenId}). Required: message_list_id, id.
create_sms_list_send_delivery_report
Triggers a delivery report for messageList API (POST /sms/v1/messageList/{id}/deliveryReport/{tokenId}). Required: message_list_id, tokenid.
create_a_salesforce_marketing_cloud_engagement_sms_list_send
Post Message to List (POST /sms/v1/messageList/{id}/send). Required: message_list_id.
get_sms_queued_mo_delivery_by_id
Retrieves the delivery status of a queued MO (GET /sms/v1/queueMO/deliveries/{tokenId}). Required: id.
get_sms_queued_mo_history_by_id
Retrieves the tracking history of a queued MO (GET /sms/v1/queueMO/history/{tokenId}). Required: id.
create_sms_queued_mo_message
Queues an MO message for send (POST /sms/v1/queueMO).
create_sms_subscription_lookup
Returns subscription status for a mobile number or subscriber key (POST /sms/v1/contacts/subscriptions).
create_a_salesforce_marketing_cloud_engagement_tag
Create Nested Tags (POST /hub/v1/nestedtags).
delete_a_salesforce_marketing_cloud_engagement_tag_by_id
Deletes an existing tag and all of its nested tags (DELETE /hub/v1/nestedtags/{tagId}). Required: id.
get_single_salesforce_marketing_cloud_engagement_tag_by_id
Returns the tag associated with the specified tagId (GET /hub/v1/nestedtags/{tagId}). Required: id.
list_all_salesforce_marketing_cloud_engagement_tags
Returns an array of tags owned by the requesting client (GET /hub/v1/nestedtags).
salesforce_marketing_cloud_engagement_tags_partial_update
Patch Nested Tags (PATCH /hub/v1/nestedtags/{tagId}). Required: tag_id.
update_a_salesforce_marketing_cloud_engagement_tag_by_id
Updates an existing tag. You must provide the entire tag payload because this request modifies the entire tag. To provide only the fields to modify, use the Patch Nested Tags request instead (PUT /hub/v1/nestedtags/{tagId}). Required: id.
list_all_salesforce_marketing_cloud_engagement_token_context
Returns information about an authentication token (GET /platform/v1/tokenContext).
list_all_transactional_email_definitions
Get a list of all email send definitions. You can filter and sort the results by including query parameters (GET /messaging/v1/email/definitions). The connector pages through all results with $page and $pagesize.
create_transactional_email_definition
Create a long-living send definition object that references the email template, subscriber list, sending options, journe. A send definition is referenced in the transactional messaging API when you send a triggered message to recipients. We recommend that you create one definition for each email use-case (POST /messaging/v1/email/definitions).
get_transactional_email_definition_by_id
Get the content of an email send definition by specifying its key (GET /messaging/v1/email/definitions/{definitionKey}). Required: id.
delete_transactional_email_definition_by_id
Delete an email send definition by specifying its key (DELETE /messaging/v1/email/definitions/{definitionKey}). Required: id.
update_transactional_email_definition_by_id
Update an email send definition by specifying its key (PATCH /messaging/v1/email/definitions/{definitionKey}). Required: id.
transactional_email_definitions_queues_bulk_delete
Deletes the queue for a send definition (DELETE /messaging/v1/email/definitions/{definitionKey}/queue). Required: definition_key.
list_all_transactional_email_definitions_queues
Get the queue metrics for an email send definition by specifying its key (GET /messaging/v1/email/definitions/{definitionKey}/queue). Required: definition_key.
create_transactional_email_message_batch
Send an email to multiple recipients by specifying a send definition. You can send messages to up to 2,000 recipients per request. If you send attributes with the recipients, we recommend no more than (POST /messaging/v1/email/messages).
list_all_transactional_email_messages
Gets a paginated list of messages that weren’t sent, ordered from oldest to newest (GET /messaging/v1/email/messages). Required: type.
get_transactional_email_message_by_id
Retrieves the send status for an email. Requests to this endpoint are rate-limited. To monitor message statuses in real time, subscribe to transactional send events using Event Notification Service (GET /messaging/v1/email/messages/{messageKey}). Required: id.
create_transactional_email_message
Send an email to a single recipient by specifying a message key (POST /messaging/v1/email/messages/{messageKey}). Required: message_key.
list_all_transactional_ott_definitions
Get a list of OTT send definitions. The number of records that the method returns is based on the $pageSize and $page parameters. It doesn't necessarily return all the records in one call (GET /messaging/v1/ott/definitions/). The connector pages through all results with $page and $pageSize.
create_transactional_ott_definition
Create an OTT send definition used to make final message sends (POST /messaging/v1/ott/definitions/).
get_transactional_ott_definition_by_id
Retrieve the send definition configuration details for a definition key (GET /messaging/v1/ott/definitions/{definitionKey}). Required: id.
update_transactional_ott_definition_by_id
Update an OTT send definition using the definition key. You can update only the status of the send definition (PATCH /messaging/v1/ott/definitions/{definitionKey}). Required: id.
delete_transactional_ott_definition_by_id
Delete a message definition. You can't restore a deleted definition. The deleted definition is archived, and a delete location of the definition key is provided in the response for reference. You can (DELETE /messaging/v1/ott/definitions/{definitionKey}). Required: id.
create_transactional_ott_message_batch
Send a message to multiple recipients using a send definition. You can provide a messageKey in the request; otherwise, the messageKey is automatically generated in the response (POST /messaging/v1/ott/messages/).
get_transactional_ott_message_by_id
Get message send status for a recipient. This method returns the send status for a message (GET /messaging/v1/ott/messages/{messageKey}). Required: id.
list_all_transactional_push_definitions
Retrieve a list of transactional push send definitions in your account.
To execute this operation, you must have the Channels Read permission (GET /messaging/v1/push/definitions).
create_transactional_push_definition
Create a transactional push send definition.
To execute this operation, you must have the Channels Write permission (POST /messaging/v1/push/definitions).
get_transactional_push_definition_by_id
Retrieve details of a transactional push send definition.
To execute this operation, you must have the Channels Read permission (GET /messaging/v1/push/definitions/{definitionKey}). Required: id.
update_transactional_push_definition_by_id
Update a transactional push send definition.
To execute this operation, you must have the Channels Write permission (PATCH /messaging/v1/push/definitions/{definitionKey}). Required: id.
delete_transactional_push_definition_by_id
Delete a transactional push send definition.
To execute this operation, you must have the Channels Write permission (DELETE /messaging/v1/push/definitions/{definitionKey}). Required: id.
create_transactional_push_message
Send a transactional push notification to one or more subscribers or devices.
To execute this operation, you must have the Channels Send permission (POST /messaging/v1/push/messages/).
get_transactional_push_message_by_id
Retrieve the status of a transactional push notification.
To execute this operation, you must have the Channels Read permission (GET /messaging/v1/push/messages/{messageKey}). Required: id.
create_transactional_sms_definition
Create Send Definition (POST /messaging/v1/sms/definitions).
delete_transactional_sms_definition_by_id
Deletes a message definition. You can’t restore a deleted definition. The deleted definition is archived, and a delete location of the definition key is provided in the response for reference (DELETE /messaging/v1/sms/definitions/{definitionKey}). Required: id.
list_all_transactional_sms_definitions
Get a list of SMS send definitions (GET /messaging/v1/sms/definitions). The connector pages through all results with $page and $pageSize.
get_transactional_sms_definition_by_id
Get Send Definition by Key (GET /messaging/v1/sms/definitions/{definitionKey}). Required: id.
update_transactional_sms_definition_by_id
Updates a specific message definition. It can take up to two minutes for outbound messages to reflect the changes (PATCH /messaging/v1/sms/definitions/{definitionKey}). Required: id.
transactional_sms_definitions_queues_bulk_delete
Delete Messages Queued for a Defintion (DELETE /messaging/v1/sms/definitions/{definitionKey}/queue). Required: definition_key.
list_all_transactional_sms_definitions_queues
Get Queue Metrics for a Definition (GET /messaging/v1/sms/definitions/{definitionKey}/queue). Required: definition_key.
create_transactional_sms_message_batch
Send a Message to Multiple Recipients (POST /messaging/v1/sms/messages/).
list_all_transactional_sms_messages
Get List of Messages Not Sent to Recipients (GET /messaging/v1/sms/messages/).
get_transactional_sms_message_by_id
Get Message Send Status for Recipient (GET /messaging/v1/sms/messages/{messageKey}). Required: id.
create_transactional_sms_message
Send a Message to a Single Recipient (POST /messaging/v1/sms/messages/{messageKey}). Required: message_key.
get_triggered_send_delivery_records_by_key_by_id
Gets the delivery details of an email sent using the MessageDefinitionSends, by the RecipientSendId returned from the send (GET /messaging/v1/messageDefinitionSends/key:{key}/deliveryRecords/{RecipientSendId}). Pass the RecipientSendId as id. Required: triggered_send_key, id.
create_a_salesforce_marketing_cloud_engagement_triggered_send
Sends transactional email using Marketing Cloud’s triggered send functionality. In order to use this service, configure a triggered send definition in Email Studio (POST /messaging/v1/messageDefinitionSends/{triggeredSendDefinitionId}/send). Required: triggered_send_definition_id.
list_all_salesforce_marketing_cloud_engagement_user_info
Get user information. Retrieves information about the account and user that are associated with the access token. Supply the access token in the authorization header. User information includes the account name, email, and ID (GET /v2/userinfo).
create_workflow_item_transition
Transitions the workflow item associated to an approval item from one state to another. For example, a workflow item in Draft state moves to Submitted via the Submit transition (POST /hub/v1/workflowitems/{workflowItemid}/transitions). Required: workflow_item_id.
create_workflow_role_user
Creates a user role to assign to a workflow role (POST /hub/v1/workflowitems/{workflowItemId}/roles/{workflowRoleInstanceId}/Users). Required: workflow_item_id, workflow_role_instance_id.
delete_workflow_role_user_by_id
Removes a user assigned to a workflow role (DELETE /hub/v1/workflowitems/{workflowItemId}/roles/{workflowRoleInstanceId}/Users/{userId}). Required: workflow_item_id, workflow_role_instance_id, id.
get_workflow_team_by_id
Retrieves a list of active workflow teams (GET /hub/v1/workflowteams/{objecttype}). Required: id.
list_all_salesforce_marketing_cloud_engagement_wrapping_keys
Retrieve and create an RSA 4096 wrapping key. This feature isn’t enabled by default. Contact your account executive for more information about enabling this feature. To use this feature, data at rest encryption must be enabled in your account (GET /platform/v1/wrappingKey).
Why Truto
Why use Truto’s MCP server for Salesforce Marketing Cloud Engagement
Other MCP servers give you a static tool list for one app. Truto gives you a managed, multi-tenant MCP infrastructure across 1100+ integrations.
Auto-generated, always up to date
Tools are dynamically generated from curated documentation — not hand-coded. As integrations evolve, tools stay current without manual maintenance.
Fine-grained access control
Scope each MCP server to read-only, write-only, specific methods, or tagged tool groups. Expose only what your AI agent needs — nothing more.
Multi-tenant by design
Each MCP server is scoped to a single connected account with its own credentials. The URL itself is the auth token — no shared secrets, no credential leaking across tenants.
Works with every MCP client
Standard JSON-RPC 2.0 protocol. Paste the URL into Claude, ChatGPT, Cursor, or any MCP-compatible agent framework — tools are discovered automatically.
Built-in auth, rate limits, and error handling
Tool calls execute through Truto’s proxy layer with automatic OAuth refresh, rate-limit handling, and normalized error responses. No raw API plumbing in your agent.
Expiring and auditable servers
Create time-limited MCP servers for contractors or automated workflows. Optional dual-auth requires both the URL and a Truto API token for high-security environments.
How It Works
From zero to integrated
Start with Salesforce Marketing Cloud Engagement in a free sandbox, usually ready within one business day. No boilerplate, no maintenance burden.
Link your customer’s Salesforce Marketing Cloud Engagement account
Use Truto’s frontend SDK to connect your customer’s Salesforce Marketing Cloud Engagement account. We handle all OAuth and API key flows — you don’t need to create the OAuth app.
We handle authentication
Don’t spend time refreshing access tokens or figuring out secure storage. We handle it and inject credentials into every API request.
Call our API, we call Salesforce Marketing Cloud Engagement
Truto’s Proxy API is a 1-to-1 mapping of the Salesforce Marketing Cloud Engagement API. You call us, we call Salesforce Marketing Cloud Engagement, and pass the response back in the same cycle.
Unified response format
Every response follows a single format across all integrations. We translate Salesforce Marketing Cloud Engagement’s pagination into unified cursor-based pagination. Data is always in the result attribute.
FAQs
Common questions about Salesforce Marketing Cloud Engagement on Truto
Authentication, rate limits, data freshness, and everything else you need to know before you integrate.
How does authentication to Salesforce Marketing Cloud Engagement work?
SFMC uses OAuth 2.0 via server-to-server or web app flows tied to an Installed Package in the customer's tenant. Truto handles the OAuth handshake, tenant subdomain discovery, and automatic access token refresh so your end users just click connect.
Can we write to custom Data Extensions created by our users?
Yes. You can list available Data Extensions, inspect their fields, and perform bulk row upserts, inserts, or clears against any Data Extension the connected user has access to — including custom ones they define in their account.
How do we trigger a Journey from an external event?
Use the journey event endpoint to post a contact key and payload matching a Journey's API Event entry source. The contact is injected into the running journey immediately, which is the recommended pattern over polling or manual list sends.
What's the difference between transactional and commercial sends via the API?
Transactional messaging uses pre-defined email, SMS, push, and OTT definitions optimized for high-priority 1:1 sends (OTPs, receipts). Commercial sends go through journeys, triggered sends, or list sends. Truto exposes both so you can pick the right routing per use case.
Are there rate limits we should design around?
SFMC enforces per-tenant limits that vary by endpoint (transactional messaging, Data Extension writes, and journey events each have separate quotas). Truto normalizes retries and surfaces rate limit metadata so you can back off gracefully; for very high throughput, bulk upsert endpoints are preferred over per-row calls.
Can we upload images and HTML into the customer's Content Builder?
Yes. You can create asset categories (folders) and then create assets of various types — images, HTML emails, text blocks, templates — which become immediately available in the customer's Content Builder for marketers to use in campaigns.
How fresh is the data we read back from SFMC?
Reads against Data Extensions, contacts, journeys, assets, and automations are live against the SFMC REST APIs, so responses reflect the current state. Long-running operations like bulk ingest or journey publishes return async status endpoints that you can poll for completion.
Salesforce Marketing Cloud Engagement
Get Salesforce Marketing Cloud Engagement integrated into your app
Our team understands what it takes to make a Salesforce Marketing Cloud Engagement integration successful. A short, crisp 30 minute call with folks who understand the problem.