Connect AI agents to Salesforce Marketing Cloud

Validate an email address's syntax and deliverability using Marketing Cloud's Address Verification API. Choose one or more validators: SyntaxValidator checks for basic structural validity (e.g. presence of '@' and a domain with a '.'), MXValidator checks the domain has a valid DNS MX record, and ListDetectiveValidator checks the address's username or domain against a known bad-address filtering list. This is a read-only check -- it does not modify any Marketing Cloud data. Returns a validation result indicating whether the address passed each requested validator. Example: email 'help@example.com' with all three validators.

Retrieve a single approval item by its unique ID from Salesforce Marketing Cloud's Approvals v2 REST API. The approval item must belong to (be visible to) the current user's approval context. The response includes the approval's name, description, workflow state (e.g. draft, submitted, reviewed, approved), workflow type, deadline, comment counts, and the workflow item's current state and available transitions based on the current user's roles.

List the roles defined for a given Approvals v2 item and the users assigned to each role, via GET /hub/v1/approvals-v2/{id}/roles on Salesforce Marketing Cloud's Approvals REST API. Use this alongside Get Approval Item to see who can act on (review or approve) a specific approval item, and in what capacity. Confidence note: existence of this route was confirmed only via a search-indexed documentation page title; the exact shape of the returned roles/assignments has not been independently verified, so treat the returned fields as best-effort until confirmed against a live response.

List approval items in Salesforce Marketing Cloud that belong to the current user's approval workflow context, using the Approvals v2 REST API. Results can be filtered by workflow state, workflow type, object type, and other attributes, and are paginated. Use this to see what content (emails, journeys, assets, etc.) is pending, in review, or already approved. Each item in the response includes its approval ID, name, workflow state, workflow type, deadline, and comment counts.

Retrieve the Approvals v2 configuration/settings that apply to the current user, via GET /hub/v1/approvals-v2/settings on Salesforce Marketing Cloud's Approvals REST API. Use this alongside List Approval Items and Get Approval Item to understand how approvals are configured (for example, notification or workflow-related settings) before creating or acting on approval items. Confidence note: existence of this route was confirmed only via a search-indexed documentation page title; the exact shape of the returned settings object has not been independently verified, and no query or request-body parameters are documented for it, so this tool takes no input beyond authentication. Treat the response fields as best-effort until confirmed against a live call.

Retrieve a single Content Builder category (folder) by its numeric ID, using GET /asset/v1/content/categories/{id}. This returns just that one folder's id, name, parentId, and categoryType, rather than the full list returned by List Content Categories. Confirmed via two independently indexed official Salesforce documentation pages both titled 'Get Category by ID' -- developer.salesforce.com's current JS-rendered docs platform returns 404 to direct automated fetches of this deep-linked reference page, so the exact response shape was not read first-hand in this session; it is inferred from the equivalent List Content Categories response and the sibling Get Content Asset tool.

List Content Builder categories (folders) owned by or shared with your Marketing Cloud account (MID), using the Asset REST API. Supports pagination ($page/$pagesize), sorting ($orderBy), simple filtering ($filter), and requesting categories shared from other business units (scope=Shared). Each returned category includes its id, name, parentId, and categoryType. Use this to discover valid category IDs before creating or moving assets/folders.

Get the compiled output of one channel view of a Content Builder asset (for example the html, text, subjectline or preheader view of an email). Returns the view's compiled content as the API returns it; the output can be large for rich emails. Use this to read the final rendered content of a single view. Use salesforcemarketingcloud_asset_get to read the asset's full metadata and every view definition at once, and salesforcemarketingcloud_asset_salutations_get_by_id for only an email's header and footer. Requires the documents_and_images_read scope and the numeric asset ID, which you can find with salesforcemarketingcloud_asset_list or salesforcemarketingcloud_asset_query.

Retrieve a single Content Builder asset by its numeric asset ID using the Salesforce Marketing Cloud Asset REST API. Returns the asset's full metadata and content, including name, customerKey, description, assetType (id/name/displayName), category, tags, views (e.g. html/text/subjectline/preheader for emails), content, data, and file properties (for images/documents). Use this to inspect an existing email, template, content block, image, or other Content Builder asset before updating or reusing it. Example asset id: 20331.

Best-effort tool: retrieve the raw file bytes of a Content Builder asset (the actual image, document, or other binary payload) rather than its JSON metadata, using GET /asset/v1/content/assets/{id}/file. This is distinct from the Get Content Asset tool, which returns the asset's JSON object (name, category, views, etc.) but not the underlying file content. This exact sub-path was not confirmed against an official Salesforce documentation page in this session -- developer.salesforce.com's JS-rendered docs platform 404s to automated fetches and no exact matching official page title was found by search -- so it is corroborated only by three independent secondary sources (ampscript.xyz, ssjsdocs.xyz/salesforcefan.com, and a LinkedIn SFMC REST API walkthrough) that all cite this identical path and GET-binary behavior. Verify against a live tenant or Postman collection before relying on this in production; only use it for assets you already know contain a file (e.g. image or document asset types).

List and paginate Content Builder assets (emails, templates, blocks, images, documents, and other content items) using the Asset REST API's GET /asset/v1/content/assets resource. Supports simple filtering with the $filter query syntax (e.g. Name like 'welcome' or assetType.name eq htmlemail), sorting with $orderBy (property plus asc/desc, e.g. 'id desc'), limiting returned properties with $fields, and pagination via $page/$pageSize. For complex AND/OR filter logic or filtering by nested subproperties, use the dedicated asset query tool instead.

Advanced search for Content Builder assets using the Asset REST API's POST /asset/v1/content/assets/query resource, for filter logic that the simple GET list endpoint can't express (AND/OR combinations, or filtering by nested subproperties). Provide a query object using SFMC's asset query grammar: either a simple form {"property": "assetType.id", "simpleOperator": "IN", "value": ["20","21"]}, or a compound form {"leftOperand": {...}, "logicalOperator": "AND", "rightOperand": {...}} for combining conditions. Optionally add sort (array of {property, direction}) and fields (array of asset properties to return, e.g. thumbnail, category, content, data) to shape the response, plus page/page_size for pagination.

Get the default header and footer (salutation) configured for the Marketing Cloud account. Returns an object with the HTML header, HTML footer, text header and text footer as separate string fields, passed through as the API returns them. Use this to read the account-wide defaults. Use salesforcemarketingcloud_asset_salutations_get_by_id for the header and footer of one specific email asset. Requires the documents_and_images_read scope; takes no inputs.

Get the header and footer (salutation) of a specific email asset in Content Builder. Returns an object with the HTML header, HTML footer, text header and text footer as separate string fields, passed through as the API returns them. Behavior for assets that are not emails is not documented. Use this to read the header and footer of one email by asset ID. Use salesforcemarketingcloud_asset_salutations_get for the account-wide default header and footer, and salesforcemarketingcloud_asset_get for the email's content and metadata. Requires the documents_and_images_read scope and the numeric asset ID of an email, which you can find with salesforcemarketingcloud_asset_list or salesforcemarketingcloud_asset_query.

List the Content Builder asset types supported by Salesforce Marketing Cloud, using the Asset REST API. Each entry includes the numeric id, name (e.g. htmlemail, template, htmlblock, jpg), and displayName of an asset type. Use this to look up the correct asset_type_id when creating a new asset with the Create Content Asset tool, instead of hardcoding type IDs.

Retrieve logged Audit Trail audit events for this Salesforce Marketing Cloud account and its child business units, using GET /data/v1/audit/auditEvents. Audit events record administrative/configuration changes such as user and role updates, security settings changes, and other account-object modifications (logins are audited separately at the enterprise level via the sibling GET /data/v1/audit/securityEvents endpoint). Each item in the response includes an id, createdDate, memberId, enterpriseId, the employee who performed the action (id, employeeName, userName), the objectType affected (id, name, e.g. 'MemberEmployee', 'SecuritySettings'), the operation performed (id, name, e.g. 'Update'), the affected object (id, name), and a transactionId. Results are paginated and sortable. Requires the account's Installed Package to have the Tracking Events Read (tracking_events_read) scope. Confirmed against Salesforce's official 'Salesforce Marketing Cloud APIs' Postman collection (folder: REST > Audit > Get Audit Events / Get Security Events); a fully public Salesforce Developers reference page for this exact operation could not be independently reloaded at authoring time. The page-size query parameter is sent as the lower-cased '$pagesize' (not '$pageSize'), matching the exact casing used in that collection's example request for the sibling Security Events endpoint in the same /data/v1/audit/ family — the full set of supported query parameters beyond page/$pagesize/orderBy (e.g. a possible $filter) is still not guaranteed and should be confirmed in testing.

Get information about the Salesforce Marketing Cloud account and user associated with the currently authenticated access token, using GET /v2/userinfo. Unlike every other tool in this connector, this endpoint is served from the tenant's AUTH subdomain (https://{{domain}}.auth.marketingcloudapis.com) rather than the REST subdomain (.rest.marketingcloudapis.com) — no path or query parameters are needed, since the access token itself (sent as the Bearer credential) identifies both the account and the user. The response includes user details (e.g. id, email, locale, timezone) and organization/account details (e.g. enterprise ID, member ID/MID, stack key, region), along with the account's REST and SOAP base instance URLs and the OAuth scopes granted to the current token. Use this to verify which account/MID a token is scoped to, confirm granted scopes before calling a scope-gated endpoint, or discover the account's own REST/SOAP base URLs at runtime.

Retrieve an automation's (Automation Studio program's) full definition and current status from Salesforce Marketing Cloud via GET /automation/v1/automations/{id}. Requires the automation's ObjectID (a GUID), as returned by the Create Automation or List Automations tools. Returns fields such as name, key, description, status (e.g. Building, Ready, Running, Paused, Stopped, Scheduled, AwaitingTrigger), categoryId, the ordered steps array (each step's activities), the startSource (schedule or file-drop trigger configuration), and an automationLegacyId — a separate numeric identifier needed by the legacy-namespaced status and pause tools (Get Automation Status, Pause Automation). Example id: 8f14e45f-ceea-467e-bd3a-45b3f4b3e21f.

List automations (Automation Studio programs) in the Salesforce Marketing Cloud account via GET /automation/v1/automations, the collection form of the same Automation REST API used by the Get Automation, Create Automation, and Update Automation tools (which operate on /automation/v1/automations/{id}). Returns each automation's id, key, name, description, and status (e.g. Building, Ready, Running, Paused, Stopped, Scheduled, AwaitingTrigger). Supports optional pagination. Note: Salesforce's rendered API reference for this Automation Studio resource is a JavaScript-driven page that could not be fully inspected during authoring; the item-level GET/POST/PATCH on this same /automation/v1/automations resource are confirmed working via production tooling, and this list form follows the same collection+item REST convention used elsewhere in this API (e.g. GET /interaction/v1/interactions). Verify during testing and adjust the pagination parameter names if the API rejects them.

Get extended run/status details for an automation (Automation Studio program) in Salesforce Marketing Cloud via GET /legacy/v1/beta/bulk/automations/automation/definition/{automationLegacyId} — confirmed via production SFMC tooling as the source of richer runtime status than the main Get Automation tool provides. Requires the automation's numeric automationLegacyId (NOT the GUID ObjectID used by Get/Start/Delete Automation) — find it in the automationLegacyId field of the Create Automation or Get Automation response. Returns fields including automationType, status (e.g. Building, Ready, Running, Paused, Stopped, Scheduled, AwaitingTrigger, Skipped, Initialized, Error), createdBy/createdDate, lastSavedBy/lastSaveDate, lastPausedBy/lastPausedDate, the scheduleObject (id, description, iCalRecur, startDate, timeZone — its id is the scheduleLegacyId needed by the Pause Automation tool), and the processes array describing each step's workers/activities. Poll this after Start Automation to watch status move from Running back to Ready/Scheduled. Example automationLegacyId: 4821.

Check the status of a Trigger API request that was submitted to start a file-drop automation. Returns the request's current state as one of Processing, Queued, Triggered, NoAutomationFound, ErrorMultipleAutomationsFound, Skipped, Deduplicated or Error. Read the state from the response body. A 404 error means the request ID does not exist. Use this right after salesforcemarketingcloud_automation_trigger_start to find out whether the request actually fired an automation; it only reads and never starts anything. Use salesforcemarketingcloud_automation_get or salesforcemarketingcloud_automation_status_get to inspect the automation itself once it has been triggered. Prerequisites: the request ID returned by salesforcemarketingcloud_automation_trigger_start, and an Installed Package with the automations_read scope. Salesforce documents this endpoint as Beta.

Check the status and progress of a bulk ingest job created via the Create Bulk Ingest Job tool, as step 4 of Salesforce Marketing Cloud's Bulk Data Ingest workflow. Salesforce's public documentation mentions monitoring job progress and reviewing completed-job summaries (row counts, error details) only in prose - the exact path is not confirmed from a fetchable reference/OpenAPI source in this session. The path used here (GET /data/v1/bulk/ingest/{bulkApiDefinitionId}) is inferred by analogy with the create-job endpoint and Salesforce's general Bulk API 2.0 convention of GET-ing a job resource by its ID to retrieve its current state. Poll this after calling the Complete Bulk Ingest Job tool until the job reaches a terminal state before assuming the import has finished. Do not rely on this tool in production before smoke-testing it against a real Marketing Cloud sandbox and correcting the path_template if the API responds with a 404 or an unexpected shape.

Retrieve a single asset association of a campaign from Marketing Cloud's Hub Campaigns API. Returns the association record linking that asset to the campaign. Use this to inspect one known link; use campaign_assets_list to see every asset on a campaign, campaign_asset_add to link a new one, and campaign_get for the campaign itself. Requires the campaign_read scope (the Campaigns > Access permission), a campaign id from campaign_list, and an asset id taken from campaign_assets_list or campaign_asset_add.

List the Content Builder assets currently associated with a Salesforce Marketing Cloud campaign via the Hub API. Returns each linked asset's id and association metadata. Accepts optional page and pageSize query parameters to page through results. Note: a live test found this Hub API endpoint did not honor pageSize to shrink the result count below the account's default page size (results stayed at 50 regardless of the value sent) -- use page to page through the full result set and don't rely on pageSize to limit how many assets come back.

Retrieve a single Salesforce Marketing Cloud campaign by its id via the Hub API. Returns the campaign's id, name, description, campaignCode, color (hex), favorite flag, createdDate, and modifiedDate. Use campaign_list to find a campaign's id if you don't already have it.

List campaigns defined in Salesforce Marketing Cloud via the Hub API (Content Builder Campaigns feature used to group and tag related Content Builder assets). Returns a paginated collection of campaign objects (id, name, description, campaignCode, color, favorite, createdDate, modifiedDate). Accepts optional page and pageSize query parameters to page through results; leave both blank to fetch the API's default first page. Note: a live test found this Hub API endpoint did not honor pageSize to shrink the result count below the account's default page size (results stayed at 50 regardless of the value sent) -- use page to page through the full result set and don't rely on pageSize to limit how many campaigns come back.

Look up the Contact Key(s) associated with one or more email addresses, via POST /contacts/v1/addresses/email/search. Note: Marketing Cloud does not expose a plain 'list all addresses' endpoint; the real, documented way to resolve contact/address identity from channel addresses is this email-to-contact-key search. Returns, for each email address supplied, the matching contact key(s) and the date each was created.

Retrieve a single attribute group of a contact data schema in Contact Builder, identified by its GUID, its key, or its name. Returns the attribute group with its ID, key, name, parent schema ID, whether it is system defined, the owning application ID and key, template ID, fully qualified name, group type, and links to the related schema and attribute set definitions. Use this when you already know which attribute group you want, for example key:com.exacttarget.mobilepush.ETMobilePush. Use salesforcemarketingcloud_contact_attribute_groups_list to enumerate every attribute group of a schema, and salesforcemarketingcloud_contact_attribute_set_get to read an attribute set definition. Requires the list_and_subscribers_read scope and the ID of the contact data schema, which you can find with salesforcemarketingcloud_contact_schemas_list.

List attribute groups in Contact Builder via GET /contacts/v1/schemas/{schemaId}/attributeGroups. Attribute groups organize related attribute sets (e.g. 'ExactTarget MobilePush'). Marketing Cloud schemas are tenant-specific; find your account's schema id first by calling GET /contacts/v1/schema (the Get Schemas Collection endpoint) and using the 'id' of the schema with schemaType 'Contacts'. Note: a live test against this endpoint found that it may return the same full set of attribute groups for the account regardless of which valid schema_id is supplied -- despite schema_id appearing in the path, treat this endpoint as 'list this account's attribute groups' rather than a reliable per-schema filter, and verify against your own tenant before assuming scoped results.

Retrieve the attribute value data rows of a specified Contact Builder attribute set by name, via GET /contacts/v1/attributeSets/name:{name}. The literal text 'name:' is part of the URL path itself, immediately followed by the attribute set's name (e.g. a call for the 'Email Addresses' attribute set hits /contacts/v1/attributeSets/name:Email Addresses). This is expected to return the contact-level data rows stored under that attribute set, similar in spirit to the by-id attribute set definition lookup but keyed by name and returning data instead of the definition. This endpoint was located via a Salesforce documentation search-index page title rather than a fully loaded reference page, so its exact response shape and any supported query filters have not been independently verified -- only the name path parameter is modeled here as a result.

Retrieve a single Contact Builder attribute set definition by its UUID, via GET /contacts/v1/attributeSetDefinitions/{id}. An attribute set definition describes a data extension or system attribute group (e.g. Email Addresses, MobilePush Demographics) that can be attached to a contact, and is expected to return the same kind of item found in the List Contact Attribute Set Definitions tool's results -- id, key, name, whether it is sendable, and its attribute/field list -- just narrowed to the one definition. This by-id endpoint was located via a Salesforce documentation search-index page title rather than a fully loaded reference page, so its exact response shape has not been independently re-verified; use the List Contact Attribute Set Definitions tool first to find the id you want, then call this to fetch just that one definition.

List all attribute set definitions available in the account's Contact Builder data model, via GET /contacts/v1/attributeSetDefinitions (note: the real Marketing Cloud path is 'attributeSetDefinitions', not 'attributeSets'). Each attribute set definition represents a data extension or system attribute group (e.g. 'Email Addresses', 'MobilePush Demographics') that can be attached to a contact, and includes its id, key, name, whether it is sendable, and its attribute/field list. Use this to discover valid attribute set names and field names before calling Create/Update Contact.

Count the contacts in the account, either all of them or only those that match a single attribute filter. Returns the number of matching contacts together with the request and response message IDs, the time the response was generated, and any result messages; a failed call also carries an error flag and error messages. It does not return the contacts themselves. Use this when you only need a number. It is a read-only lookup even though it is sent as a POST. Use salesforcemarketingcloud_contact_search to retrieve the matching contacts and their addresses for one attribute, and salesforcemarketingcloud_contact_addresses_list to resolve contact keys from email addresses. Only one filter condition is supported, and the only supported comparison is Equal. Requires the audiences_read scope (the Contacts > Audiences > Read > View All Contacts permission).

Retrieve the relationship details of one custom object field that is registered in the contacts model. Returns the requested custom object field ID and, for each relationship, the parent attribute set and the contact attribute the field corresponds to (each with its definition ID, name and key) and the attribute groups the field belongs to, plus the request and response message IDs and any result messages. Use this to see where one field of a custom object (data extension) is used in Contact Builder. Use salesforcemarketingcloud_contact_custom_object_info_get to ask whether a whole custom object is used in the contact model, and salesforcemarketingcloud_contact_attribute_group_get to read one of the attribute groups it returns. Requires the list_and_subscribers_read scope and the ID (GUID) of a custom object field; a missing or invalid ID is rejected with a 400 error.

Check whether a custom object (data extension) is used in the account's contact model, via GET /contacts/v1/customObject/{id}/isUsedInContacts. Existence of this endpoint is confirmed only via a Salesforce documentation search-index page title -- the exact response shape was not independently verified, so treat the returned payload as best-effort and inspect it at runtime rather than assuming a specific structure. Use this before deleting or restructuring a custom object, to check whether the account's contact model depends on it.

List asynchronous contact delete operations that have been submitted for this account, via GET /contacts/v1/contacts/deleteOperations. Each item is expected to represent one delete request batch (with an operation identifier and a status you can look up with the Get Contact Delete Status tool), letting you audit or monitor bulk contact-deletion activity without knowing an individual operation ID in advance. This endpoint was located via a Salesforce documentation search-index page title rather than a fully loaded reference page, so its exact response shape is not independently confirmed. Optional page and page_size fields are included on a best-effort basis, following the $page/$pageSize pagination convention confirmed on the sibling /contacts/v1/attributeSetDefinitions endpoint in the same Contacts API family -- they have not been confirmed specifically for this operation and can be left blank if the API ignores or rejects them.

Retrieve the delete options registered for contact deletion in Salesforce Marketing Cloud, optionally narrowed by list type, delete operation type, or application (a read-only lookup). Returns an items array with one entry per adapter (adapter ID and key, plus the application it belongs to), each holding the options that adapter offers with their key, display name, description, input type, data type, and default value. Use this to discover which delete options exist for each application; leave every filter blank to get all registered options. Use salesforcemarketingcloud_contact_delete to submit deletions and salesforcemarketingcloud_contact_delete_settings_update to change delete configuration. Requires the list_and_subscribers_write scope.

Get details of contact delete requests submitted over a date range, via GET /contacts/v1/contacts/analytics/deleterequests. This is expected to list the individual delete requests made in that window (e.g. who/when/how many contacts, and each request's status), which is useful for auditing bulk contact-deletion activity over time. The endpoint's existence and purpose were confirmed via a Salesforce documentation search-index page title rather than a fully loaded reference page; the start_date/end_date fields are sent as 'startDate'/'endDate' on a best-effort basis, since the exact query parameter names were not independently verified.

Get a status-count summary of contact delete requests submitted over a date range, via GET /contacts/v1/contacts/analytics/deleterequests/summary. This is expected to return aggregate counts of delete requests grouped by status (e.g. how many completed, are in progress, or failed) for the given window, complementing the Get Contact Delete Request Details tool's per-request listing with a rolled-up view. The endpoint's existence and purpose were confirmed via a Salesforce documentation search-index page title rather than a fully loaded reference page; the start_date/end_date fields are sent as 'startDate'/'endDate' on a best-effort basis, since the exact query parameter names were not independently verified.

Get the status of an asynchronous contact delete operation, via GET /contacts/v1/contacts/actions/delete/status. Because this path has no {id} segment, the operation identifier must be supplied as a query parameter; the operation_id field here is sent as 'operationId' on a best-effort basis (the exact query parameter name and casing were not independently confirmed, only the endpoint's existence and purpose -- get an operation ID from a previous contact-delete request or from the List Contact Delete Operations tool). Use this to poll whether a bulk or single contact deletion has completed, is still running, or failed.

Get consent/subscription preferences for a single contact by their numeric Contact ID, via GET /contacts/v1/contacts/id:{contactId}/Preferences. Existence of this endpoint is confirmed only via a Salesforce documentation search-index page title -- the exact response shape was not independently verified, so treat the returned payload as best-effort and inspect it at runtime rather than assuming specific fields. If you only have the contact's Subscriber/Contact Key instead of its numeric ID, use the by-key variant of this tool instead.

Get consent/subscription preferences for a single contact by their Contact Key (Subscriber Key), via GET /contacts/v1/contacts/key:{contactKey}/Preferences. Existence of this endpoint is confirmed only via a Salesforce documentation search-index page title -- the exact response shape was not independently verified, so treat the returned payload as best-effort and inspect it at runtime rather than assuming specific fields. If you only have the contact's numeric Contact ID instead of its key, use the by-id variant of this tool instead.

Look up tracking-consent preferences (whether each contact has opted out of tracking) for a batch of contacts identified either by contact key or by numeric contact ID; this is a read-only lookup sent as a POST and it changes nothing. Returns the matching contacts, each with its contact ID and opt-out flag, plus the number of rows returned, the request and service message IDs, and any result messages. Use this to read preferences for many contacts in one call (Salesforce recommends batching for performance). Use salesforcemarketingcloud_contact_preferences_get_by_id or salesforcemarketingcloud_contact_preferences_get_by_key for a single contact, and salesforcemarketingcloud_contact_preferences_add to change preferences. Requires the list_and_subscribers_read scope (IMH Contacts > Access, which Salesforce's scope table calls Contacts_access).

Get the status of an asynchronous contact restrict operation, via GET /contacts/v1/contacts/actions/restrict/status. Because this path has no {id} segment, the operation identifier must be supplied as a query parameter; by analogy with this connector's confirmed Get Contact Delete Status tool (the equivalent GET /contacts/v1/contacts/actions/delete/status endpoint, which takes an 'operationId' query parameter), operation_id here is sent as 'operationId' on a best-effort basis -- the exact query parameter name and casing for this specific endpoint were not independently confirmed, only its existence and general purpose. Use this to poll whether a bulk contact restrict (suppress-from-sends) operation has completed, is still running, or failed.

List all contact data schemas defined in the account, via GET /contacts/v1/schema (the Get Schemas Collection endpoint). This account-wide call takes no parameters. Existence is confirmed both via a Salesforce documentation search-index page title and because this connector's List Contact Attribute Groups tool already documents calling this same endpoint to obtain a schema id -- the exact response shape was not independently verified beyond that, so treat the returned payload as best-effort. Use the 'id' of the schema with schemaType 'Contacts' as input to schema-scoped tools like List Contact Attribute Groups.

Search for contacts and their associated addresses in Salesforce Marketing Cloud by a single filterable attribute. Uses the Contacts/Addresses REST search endpoint: POST /contacts/v1/addresses/search/{attributeName}. Choose the attribute to filter on (ContactKey, LastModfiedDate, Source, Channel, Status, or AudienceID [note: 'LastModfiedDate' is spelled exactly this way, without the second 'i', in Salesforce's own API] ) and provide the value to match; currently only the 'Is' comparison operator is supported. Returns matching addresses with their contactID/contactKey and channel-specific value sets (e.g. email or mobile number details).

Retrieve just the field/column definitions of a Data Extension's schema from Salesforce Marketing Cloud's Custom Object REST API: GET /data/v1/customobjects/{id}/fields. This is meant as a narrower sub-resource of the full Get Data Extension response (which already returns a fields array alongside the data extension's other metadata) -- use it when you only need the column list. IMPORTANT (confirmed by live testing against a real Marketing Cloud connection): despite this operation appearing in the Custom Objects API reference as a sibling of the create/update/delete/get-by-id operations, the path parameter only works when you pass the Data Extension's internal ObjectID (a GUID, e.g. 51195004-bc92-ef11-a5d1-5cba2c191058) -- the same GUID returned as 'id' by List Data Extensions or Get Data Extension. Passing the customer/external key instead (e.g. 'Customer_Master_DE'), with or without spaces, and even with a 'key:' prefix, was confirmed live to fail with HTTP 400 'Id is invalid' -- the exact same failure the sibling Get Data Extension tool produces for the same external key, which only succeeds once given the GUID. If this returns a 404 or 400 'Id is invalid', use Get Data Extension with the GUID instead and read its fields array.

Retrieve a Data Extension's schema (fields and properties) from Salesforce Marketing Cloud using the Custom Object REST API, looked up by its customer key (external key). Returns the Data Extension's metadata (name, customer key, description, category, sendable configuration such as isSendable/sendableCustomObjectField/sendableSubscriberField) and its full fields array, where each field includes name, data type, length, ordinal position, and constraints such as isPrimaryKey and isNullable. Use this to inspect a Data Extension's structure before reading or writing rows to it. Example key: Customer_Master_DE.

Check the status and row-count summary of a one-time Data Extension import job in Salesforce Marketing Cloud (queued by the Start Data Extension Import tool), using GET /data/v1/async/import/{id}/summary. Pass the id returned when the import was started. The response reports the job's overall progress/outcome plus row counts (e.g. total, successful, and errored rows) once the job reaches a terminal state. Poll this endpoint until the job's status is terminal (complete or errored) before assuming the import has finished, then use the Get Data Extension Import Validation Summary and Get Data Extension Import Validation Result tools to inspect the specifics of any rejected rows. as with the Start Data Extension Import tool, Salesforce's official reference page for this resource (developer.salesforce.com/docs/marketing/marketing-cloud/references/mc-import_job_api) is a client-rendered page that returned a 403/empty shell on every fetch attempt at authoring time -- the same bot-protection behavior already documented on this connector's File Transfer Location tools. The path itself (an id-scoped .../summary GET returning row counts) is corroborated by an independent third-party technical reconstruction of this Spring '24 SFMC REST API family, but the exact response field names were not directly confirmed against the primary source -- verify the live response shape before depending on a specific field name downstream.

Get row-level validation details for a one-time Data Extension import job in Salesforce Marketing Cloud, using GET /data/v1/async/import/{id}/validationresult. Pass the id returned when the import was started (Start Data Extension Import tool). This returns the specific records that failed validation and, per publicly documented behavior of this endpoint, names the problematic field(s) on each -- use it after Get Data Extension Import Validation Summary has told you rows failed, when you need to know exactly which rows and fields caused the failures (for example, to fix and re-import them). Typically called after Get Data Extension Import Status shows the job reached a terminal state and reported errored rows. Salesforce's official reference page for this resource (developer.salesforce.com/docs/marketing/marketing-cloud/references/mc-import_job_api) is a client-rendered page that returned a 403/empty shell on every fetch attempt at authoring time -- the same bot-protection behavior already documented on this connector's File Transfer Location tools. This exact path and its 'per-record, per-field detail' behavior are corroborated by independent third-party summaries of this Spring '24 SFMC REST API family, but the precise response field names (e.g. row number, field name, error message) were not directly confirmed against the primary source -- verify the live response shape before depending on a specific field name downstream.

Get the validation summary for a one-time Data Extension import job in Salesforce Marketing Cloud, using GET /data/v1/async/import/{id}/validationsummary. Pass the id returned when the import was started (Start Data Extension Import tool). This returns a high-level rollup of how many rows in the source file passed vs. failed validation and, per publicly documented behavior of this endpoint, groups failures by category (for example, rows missing a required field) -- it does not list every individual failing row or which specific fields on which rows were the problem; use the Get Data Extension Import Validation Result tool for that row-level detail. Typically called after Get Data Extension Import Status shows the job reached a terminal state and reported errored rows. Salesforce's official reference page for this resource (developer.salesforce.com/docs/marketing/marketing-cloud/references/mc-import_job_api) is a client-rendered page that returned a 403/empty shell on every fetch attempt at authoring time -- the same bot-protection behavior already documented on this connector's File Transfer Location tools. This exact path and its 'grouped counts, not row-level detail' behavior are corroborated by independent third-party summaries of this Spring '24 SFMC REST API family, but the precise response field names were not directly confirmed against the primary source -- verify the live response shape before depending on a specific field name downstream.

Search/list data extensions (custom objects) in the account via GET /data/v1/customobjects, the collection form of the Custom Object REST API used by the Get Data Extension tool (GET /data/v1/customobjects/{key}). Returns each matching data extension's external key, name, and schema metadata. IMPORTANT: this endpoint is a search, not an unfiltered listing — Salesforce requires a non-empty '$search' query parameter on every call (confirmed live: omitting it fails with HTTP 400 'errorcode 10005: $search is a required parameter'), and per Salesforce's own Marketing Cloud Engagement MCP server documentation, that search term must be real text — wildcards such as '*' or '%' are rejected, so there is no way to request 'all data extensions' in a single call. Pass a substring of the data extension's name to search for; supports optional pagination. Note: Salesforce's rendered documentation for this collection-level GET was not directly accessible during authoring (consistent with the rest of this connector's build notes); the $search requirement and its constraints were confirmed via a live 400 response plus Salesforce's official MCE MCP server blog post, and the single-item GET by key on this same resource family is separately confirmed working. Verify pagination parameter names during testing and adjust if the API rejects them.

Retrieve the detailed, row-level results of a completed asynchronous Data Extension row job (insert/upsert/delete) in Salesforce Marketing Cloud, using GET /data/v1/async/{requestId}/results. This is distinct from the Get Async Row Job Status tool (GET /data/v1/async/{requestId}/status), which only reports overall job state (requestStatus, resultStatus, hasErrors) -- this endpoint returns the outcome of each individual row in the batch, so you can tell exactly which rows succeeded and which failed, with a status and error detail per row. Pass the same requestId returned when the row job was queued (async insert/upsert/delete tools), and call the Get Async Row Job Status tool first, fetching results only once that shows the job reached a terminal state. Results are paginated. request_id MUST be a well-formed GUID copied verbatim from a prior async row job -- as with the async row status tool, passing an arbitrary or malformed string is not guaranteed to be rejected cleanly and may return an ungraceful server error instead of a clean 400. Salesforce's official reference page for this resource (developer.salesforce.com/docs/marketing/marketing-cloud/references/mc-data_extension_rows_async) is a client-rendered page that returned a 403/empty shell on every fetch attempt at authoring time -- the same bot-protection behavior already documented on this connector's File Transfer Location tools. The path itself is corroborated by the page's own indexed sub-section title ('Get Results of Asynchronous Request'); the response shape used here (requestId, page, pageSize, count, and an items array of per-row {status, errorCode, message} objects) and the page/pageSize request parameters below come from an independent third-party technical reconstruction, not the primary source -- verify the live request/response shape before depending on a specific field or parameter name, and omit page/pageSize entirely if the API does not honor them as expected.

Check the status and result of an asynchronous Data Extension row job (created by the asynchronous row insert/upsert/delete tools) in Salesforce Marketing Cloud, using the requestId returned when the job was queued. The response includes a nested status object with fields such as requestStatus (e.g. 'InProgress', 'Complete', 'Error'), resultStatus (e.g. 'OK' or an error indicator), hasErrors, callDateTime, and completionDateTime. Poll this endpoint until requestStatus reaches a terminal state before assuming the row write has finished. request_id MUST be a well-formed GUID copied verbatim from the requestId a prior async row job (insert/upsert/delete) returned when it was queued — passing an arbitrary or malformed string is not rejected with a clean 400 but instead causes Salesforce to return an ungraceful HTTP 500. Example requestId: 3fa85f64-5717-4562-b3fc-2c963f66afa6.

Retrieve a single row from a Data Extension in Salesforce Marketing Cloud using the Custom Object Data REST API, looked up by the Data Extension's customer key (external key) plus the row's primary key value(s). If the Data Extension has a single primary key field, pass just its value (e.g. "user@example.com"). If it has a composite (multi-column) primary key, pass comma-separated Field:Value pairs (e.g. "Email:user@example.com,Country:US"). The response splits the row into a 'keys' object (the primary key field(s) and their values) and a 'values' object (every other field and its value). Example key: Customer_Master_DE.

Retrieve rows of data from a Data Extension in Salesforce Marketing Cloud using the Custom Object Data REST API, looked up by the Data Extension's customer key (external key). Each returned row is split into a 'keys' object (the primary key field(s) and their values) and a 'values' object (every other field and its value). Supports an OData-style $filter expression to narrow results (e.g. "Status eq 'Active'"), and $page/$pageSize for pagination (up to 2500 rows per page). Filtering, sorting, and paging beyond the first page are only fully supported for sendable Data Extensions — requests against non-sendable Data Extensions can return a maximum of 200 rows. Example key: Customer_Master_DE.

List the domain verification/authentication records configured for this Salesforce Marketing Cloud account, using GET /messaging/v1/domainverification. Domain Verification is a new resource category for this connector: it tracks the DNS-based authentication status of sending domains, separate from the existing seed list and address validation tools. Each item in the response includes the domain name, its status (e.g. 'Verify' for pending, 'Verified' for complete), domainType (e.g. SenderDomain, TrackingDomain), and isSendable (whether Marketing Cloud will currently send from that domain). Supports pagination with $page/$pageSize, sorting with $orderBy (a field name plus 'asc' or 'desc'), and simple narrowing with $filter (e.g. "Status in ('Verify')" to see only domains still pending verification).

Get the delivery record for a single recipient of a message-definition (triggered send) send in Salesforce Marketing Cloud, via the Messaging API's deliveryRecords sub-resource (GET /messaging/v1/messageDefinitionSends/{key}/deliveryRecords/{RecipientSendId}). Use this after calling the triggered-send/message-definition send endpoint to check whether that recipient's message was delivered, is still queued, or errored. On success the response includes status ('Sent', 'Queued', or 'Error'), deliveryTime, id, messageId, and the recipient's to.address/to.id/to.key; an 'Error' status also includes a messageErrors array describing what went wrong. Example send definition key: key:Welcome_TriggeredSend. Example recipient send id: 8f14e45f-ceea-467e-b789-4b2f7e0b1a12.

Retrieve details of a single registered Event Notification Service (ENS) callback by its ID, using GET /platform/v1/ens-callbacks/{callbackId}. The response includes the callback's name, URL, maximum batch size, and its verification status (e.g. verified) with a status reason. Use this to check whether a callback is verified and ready to be used in a subscription.

List every Event Notification Service (ENS) callback registered on this Marketing Cloud account, using GET /platform/v1/ens-callbacks (confirmed via Salesforce's official 'Get All Callbacks' reference page). The connector can already create a callback (Create Event Notification Callback) and fetch one by ID (Get Event Notification Callback), but had no way to discover which callback IDs already exist -- this tool closes that gap. Returns an array of callback objects, each with callbackId (UUID), callbackName, url, maxBatchSize, and its verification status/statusReason (e.g. whether it's verified and ready to use in a subscription). No query parameters are documented for this endpoint -- it returns the full list in one call, with no pagination or filtering options confirmed.

Retrieve a single Event Notification Service (ENS) subscription by its subscription ID, using GET /platform/v1/ens-subscriptions/{subscriptionId}. Returns the subscription's current configuration, including the owning callback ID and name, the subscribed event category types (e.g. TransactionalSendEvents.EmailSent), any scoping filters, and its status (active or paused) with a status reason if paused. Use this to inspect a subscription's settings before updating or deleting it.

List all Event Notification Service (ENS) subscriptions registered for a specific callback in Salesforce Marketing Cloud, using GET /platform/v1/ens-subscriptions-by-cb/{callbackId}. ENS subscriptions are scoped to the callback that owns them (there is no single endpoint that lists subscriptions across all callbacks), so provide the callback's ID to see which event types it's currently subscribed to. Each returned subscription includes its subscription ID, name, event category types, filters, and status.

Retrieve one Automation Studio File Transfer activity by its id. Returns the activity's name, customer key, description, file name pattern, the id of the file transfer location it uses, its upload flag, its compression, encryption and PGP settings, its file age and import frequency limits, its id, and its created and modified dates. Use this to inspect a single activity, or to read the file transfer location id from an existing activity when you need to reuse it in salesforcemarketingcloud_file_transfer_activity_create. Use salesforcemarketingcloud_file_transfer_activity_list when you do not yet know the id. Requires the automations_read scope and the activity's GUID id from salesforcemarketingcloud_file_transfer_activity_list or salesforcemarketingcloud_file_transfer_activity_create.

List Automation Studio File Transfer activities in the Marketing Cloud account, optionally filtered by name and paged. Returns a paged envelope with the total count, the page number, the page size and an items array. Each item identifies one activity, including its name, customer key and activity id; the list may return fewer fields than the get tool (for example the file transfer location id may only appear in the get response), so call salesforcemarketingcloud_file_transfer_activity_get for the full definition. Use this to browse activities or to find an activity id before calling salesforcemarketingcloud_file_transfer_activity_get, salesforcemarketingcloud_file_transfer_activity_start or salesforcemarketingcloud_file_transfer_activity_delete. These are the activities themselves, not the FTP/SFTP connection profiles they point to (use salesforcemarketingcloud_file_transfer_location_list for those) and not whole automations (use salesforcemarketingcloud_automation_list). Requires the automations_read scope.

Retrieve a single external file transfer location by its Customer Key from Salesforce Marketing Cloud, using GET /data/v1/filetransferlocation/{key}. Returns the location's saved connection profile (name, description, connection type such as External SFTP/FTP/FTPS, Amazon S3, Azure Blob Storage, Google Cloud Storage, Enhanced FTP, or Safehouse) as referenced by Automation Studio's File Transfer, Import, and Data Extract activities. Sensitive fields such as passwords or keys are not returned in the response. Use List File Transfer Locations first to find a location's Customer Key. NOTE (2026-08-24 fix): this tool previously called GET /automation/v1/filelocations/{id}, which returned a generic 404 on every live call -- that base path/resource name was simply wrong. The correct resource lives under /data/v1/filetransferlocation/{key} instead, confirmed via Salesforce's own actively-maintained open-source DevOps tooling (Accenture/sfmc-devtools), which uses this exact path against real tenants; the official reference page for this resource (linked above) could not be independently fetched at authoring time (consistent hard 404 from Salesforce's own doc site, verified across dozens of fetch techniques over multiple sibling reference pages that DID load fine), so this path should still be smoke-tested against a real tenant.

List the external file transfer locations configured in this Salesforce Marketing Cloud account, using GET /data/v1/filetransferlocations. A file transfer location is a saved connection profile (External FTP/SFTP/FTPS, Enhanced FTP, Safehouse, Amazon S3, Azure Blob Storage, or Google Cloud Storage) that Automation Studio's File Transfer, Import, and Data Extract activities reference to move files in or out of Marketing Cloud. NOTE (2026-08-24 fix): this tool previously called GET /automation/v1/filelocations, which returned an identical generic 404 on every live call, including with zero parameters -- that base path/resource name was simply wrong. /automation/v1/ is the legacy Automation Studio surface, which only exposes a read-only, non-updatable subset of older FTP-type locations under /automation/v1/ftplocations (no create/update/validate); the current, full-featured File Transfer Locations resource lives under the data platform base path instead, confirmed via Salesforce's own actively-maintained open-source DevOps tooling (Accenture/sfmc-devtools) which retrieves via GET /data/v1/filetransferlocations and GET /data/v1/filetransferlocation/{key} against real tenants -- the official reference page for this resource (linked above) could not be independently fetched at authoring time (consistent hard 404 from Salesforce's own doc site, verified across dozens of fetch techniques over multiple sibling reference pages that DID load fine), so this path should still be smoke-tested against a real tenant. This endpoint returns every location in a single response (no server-side pagination -- there is no $page/$pageSize support), so the page/page_size parameters previously exposed here have been removed as non-functional. Use this to find a location's Customer Key before retrieving, updating, or referencing it in an automation.

Validate connectivity for an existing external file transfer location in Salesforce Marketing Cloud, by its Customer Key, using POST /data/v1/filetransferlocation/{key}/validate. This attempts to connect to the saved location (External FTP/SFTP/FTPS, Amazon S3, Azure Blob Storage, Google Cloud Storage, Enhanced FTP, or Safehouse) using its stored host/credentials and reports whether the connection succeeds, mirroring the 'Validate' action available on the File Locations setup screen before saving a location. This is a read-only connectivity check -- it does not modify the saved location's configuration. Use List/Get File Transfer Locations first to find a location's Customer Key. NOTE (2026-08-24 fix): this tool previously called POST /automation/v1/filelocations/{id}/validate, which returned a generic 404 on every live call -- that base path/resource name was simply wrong (same root cause confirmed across List/Get/Validate: /automation/v1/filelocations does not exist as a resource). The corrected base path here, POST /data/v1/filetransferlocation/{key}/validate, is a best-evidence reconstruction: the /data/v1/filetransferlocation(s) base and {key}-scoped singular path are confirmed via Salesforce's own actively-maintained open-source DevOps tooling (Accenture/sfmc-devtools), which uses that exact base for GET/POST/PATCH/DELETE against real tenants, but that tooling has no need for a live connectivity check and does not implement Validate, so the trailing '/validate' action-segment placement (vs. e.g. a query-param or collection-level variant) is inferred by convention from other SFMC REST families (id-scoped action suffixes), not independently confirmed. 'Validate a file transfer location' is a confirmed real operation -- it appears as its own entry under the 'File Transfer Locations' category in Salesforce's live Marketing Cloud Engagement REST API reference navigation (its href is exactly /docs/marketing/marketing-cloud/references/mc-file_transfer_locations, scraped directly from that nav), and independently as an indexed reference page titled 'Validate a file transfer location | File Transfer Locations | ... | Salesforce Developers' -- but the exact HTTP method/path and response shape still could not be directly loaded at authoring time (the reference page returns a genuine 404 from Salesforce's own doc site on every fetch attempt, across dozens of techniques, even though sibling reference pages in the same family loaded fine -- this looks like a live bug/dead link on Salesforce's own site, not a bot-protection issue). Smoke-test this path against a real tenant before relying on it.

Retrieve the paginated audit log history for a journey by its GUID id, using the Interaction REST API. Corrected endpoint: GET /interaction/v1/interactions/{id}/audit/{action} (the action segment is required in the path, not a separate 'auditLog' resource). Filter by action type (create, modify, publish, unpublish, delete, or all), optionally scope to a single versionNumber, and paginate with page/page_size. The response includes Page, PageSize, Count, and an Items array where each entry describes the action taken, a timestamp, the acting user, and status details such as publishStatus or ContactsEjected. WARNING: do not combine version_number with most_recent_version_only=true in the same call. Unlike List Journeys (which returns a clear validation error for the equivalent conflicting-filter combination), this audit-log endpoint fails that combination with an opaque generic error (HTTP error code 30000, "Oops we've encountered an error") that gives no indication the two filters are mutually exclusive. Set at most one of the two.

Retrieve the paginated audit log history for a journey by its external key, using the Interaction REST API: GET /interaction/v1/interactions/key:{key}/audit/{action}. This is the key-based counterpart to the Get Journey Audit Log tool (which takes the journey's GUID id) -- use this one when you only know the journey's customer key, not its ObjectID. Filter by action type (create, modify, publish, unpublish, delete, or all), optionally scope to a single versionNumber, and paginate with page/page_size. The response includes Page, PageSize, Count, and an Items array where each entry describes the action taken, a timestamp, the acting user, and status details such as publishStatus or ContactsEjected. Confidence note: existence of this route was confirmed via a search-indexed documentation page title; the response shape is assumed to match the id-based version (which is independently confirmed and documented), and the key: prefix syntax mirrors the same convention documented for Get Event Definition, but the key-based form of this specific audit endpoint has not been independently re-verified beyond that. WARNING: do not combine version_number with most_recent_version_only=true in the same call -- on the id-based version this combination fails with an opaque generic error (HTTP error code 30000, "Oops we've encountered an error") rather than a clear validation message, and the same is expected to apply here. Set at most one of the two.

Check the status of a previously submitted Remove Contact From Journey request in Salesforce Marketing Cloud, using POST /interaction/v1/interactions/contactexit/status. This closes the polling gap the Remove Contact From Journey tool's own description points to: that tool submits an exit request asynchronously (HTTP 202) and directs callers to this status endpoint to confirm completion. Confirmed via Salesforce's official documentation ('Get the Status of Removing a Contact from a Journey'): the request body is an array of lookups (up to 50), each identified by ContactKey and DefinitionKey (and optionally the same Versions array used on the original exit request), and the API responds 200 with, per contact, a status array describing the outcome for each targeted journey version — fields include version, message (e.g. 'Exit process Completed', 'Exit request Ignored - Duplicate Request', or 'Exit request Cancelled - Contact not in this Interaction'), and definitionInstanceId when applicable. This tool checks the status for one contact per invocation, mirroring Remove Contact From Journey's single-contact design. Pass exactly the same contact_key, definition_key, and versions you used on the original exit request.

List the journeys, and the journey versions, that each of up to 50 contact keys is found in. Returns a results object holding the memberships found, each with the contact key, the journey's definition key and the journey version number, and the list of contact keys that were not found in any journey. Use this to see which journeys a contact was found in, for example before removing it with salesforcemarketingcloud_journey_contact_exit (check the outcome with salesforcemarketingcloud_journey_contact_exit_status_get). It is a read-only lookup even though it is sent as a POST. Use salesforcemarketingcloud_journey_list, which can filter by external key, to look up a journey from the definition key returned here. Requires the journeys_read scope (the Journey Builder > General > Access, View permission; the official reference also lists the Journey Builder | Automation and Interaction Studio | Access permissions) and the contact keys to look up.

List contacts currently sitting in a given activity type and status (e.g. waiting, completed, errored) within one specific version of a journey in Salesforce Marketing Cloud Journey Builder, via GET /interaction/v1/journeys/{id}/versions/{version}/summary/contacts/{type}/{status}. This exact path could not be confirmed: a full enumeration of Salesforce's officially published Interaction REST API reference navigation (every entry under Journeys and Events, from Insert Journey through Get Journey History Download Estimate) contains no 'journeys' resource and no 'summary/contacts' sub-path -- only the singular 'interactions' resource is documented, alongside the narrower goalstatistics/{id} and waitstatistics/{id} endpoints, which return aggregate counts rather than contact lists and don't accept a type/status pair. This tool's shape is a best-effort reconstruction of the endpoint pattern requested for this connector, matching the general capability Journey Builder's UI exposes (its Activity view lets you drill into an activity and see which contacts are Waiting, Completed, or Errored there) -- but the resource name, the accepted values for type and status, and the response shape are all unconfirmed. id is assumed to be the journey's GUID (as used by every other Get/Pause/Resume/Stop Journey tool in this connector) and version its numeric published version number; type and status are passed through verbatim as free-text path segments -- try a specific activity's type or key (as seen in the activities returned by Get Journey with extras=activities) for type, and values like waiting, completed, or errored for status, but treat both as guesses, not confirmed enums, until verified against a real tenant. Smoke-test against a real tenant before relying on it in production.

Check the status of a previously submitted batch contact-entry request in Salesforce Marketing Cloud, using GET /interaction/v1/async/events/status. This closes the polling gap that Enter Contacts Into Journey (Batch)'s own description points to: that tool queues up to 100 contacts asynchronously and returns a requestId to poll here. Confirmed via Salesforce's official documentation ('Get Status of Async Journey Insertion Request'): the endpoint accepts requestId, contactKey, eventInstanceId, eventDefinitionKey, and/or type as query parameters, and requires at least one of them to be supplied — a request with none of the five is rejected. request_id (the value returned by the batch-entry call) is normally the most useful single filter, since it scopes results to exactly the batch you just submitted. The response is paginated: {page, pageSize, count, items[]}, where each item has eventCategoryType (observed values include Processed and Queued; an Error category is also expected for failed entries), a timestamp, eventDefinitionKey, requestId, and an info object with contactKey and eventInstanceId. Poll until every contact in your batch shows a terminal eventCategoryType.

Fetch the Journey API discovery document, a summary list of the methods of the Journey Builder REST service (GET /interaction/v1/rest). Returns a methods object keyed by operation name; each entry gives the operation's path relative to /interaction/v1/, its HTTP method, a short description and a parameters object that is empty for nearly every operation. The list is not exhaustive: it omits operations such as pause, resume, contact exit, audit log and validation. Use it only to see which operations the document catalogues. It describes the API, not your data, so to list or read journeys use salesforcemarketingcloud_journey_list or salesforcemarketingcloud_journey_get, and to list event definitions use salesforcemarketingcloud_journey_event_definition_list; it carries no request or response shapes. Takes no input and no other tool must run first. Salesforce lists no required permission for this call; if it is rejected as unauthorized, grant the API integration the Automation | Interactions | Read scope.

Retrieve a single event definition by ID or key from Salesforce Marketing Cloud Journey Builder (GET /interaction/v1/eventDefinitions/{id}). Returns the event definition's metadata (name, type, mode, eventDefinitionKey, dataExtensionId, schema, createdDate) used by journey entry sources and the Fire Journey Event tool.

Retrieve a single Journey Builder event definition by its eventDefinitionKey instead of its GUID id, via GET /interaction/v1/eventDefinitions/key:{key} on Salesforce Marketing Cloud's Interaction REST API. This is a convenience wrapper around the same underlying route as the Get Event Definition tool: the official getEventDefinition.html documentation page states verbatim that the id path segment also accepts the form key:{key} to look an event definition up by its key, and the official discovery document lists this key: form as a distinct route. This tool builds that key: prefix for you, so you only need to supply the bare key rather than remembering to type key: yourself. Returns the same event definition metadata as Get Event Definition -- name, type, mode, eventDefinitionKey, dataExtensionId, schema, and createdDate -- used by journey entry sources and the Fire Journey Event tool.

Retrieve a paginated collection of event definitions from Salesforce Marketing Cloud Journey Builder (GET /interaction/v1/eventDefinitions). Event definitions describe events that can be used as journey entry sources or fired to move contacts through journeys. Optionally filter by name and page through results.

Retrieve how many times an entry event (event definition) has fired in Salesforce Marketing Cloud Journey Builder (GET /interaction/v1/triggerstats/{eventDefinitionID}). Useful for confirming an API Event or other entry source is actually receiving/firing events for the journeys listening on it. this path and its one-line description ('Retrieve trigger statistics') are confirmed to exist in Salesforce's own REST discovery document for the Interaction API, but Salesforce does not publish a full parameter/response reference page for it -- no request/response schema and no confirmation of optional query parameters. The id parameter is modeled here, by analogy with the documented Get Event Definition endpoint (GET /interaction/v1/eventDefinitions/{id}), as accepting either the event definition's GUID or a key:{key} reference to its eventDefinitionKey; this key: support is NOT independently confirmed for triggerstats specifically. Verify against a sandbox account before relying on it in production.

Retrieve a journey (interaction) by its ID from Salesforce Marketing Cloud Journey Builder using the Interaction REST API (GET /interaction/v1/interactions/{id}). Returns the journey's metadata (name, key, description, status, version, workflowApiVersion, createdDate, modifiedDate) plus its triggers, goals, and activities. Pass a version number to retrieve a specific version, or omit it to retrieve the latest version. Use the extras parameter to include additional data such as activity details or stats.

Retrieve goal-completion statistics for a journey in Salesforce Marketing Cloud Journey Builder (GET /interaction/v1/goalstatistics/{id}). Returns metrics describing how many contacts have met the journey's configured goal. LIVE-CONFIRMED (2026-08-24): requires the journey's bare GUID plus a versionNumber query parameter -- a live call with only the GUID returned "A valid version number is required". The key:{key} external-key form is confirmed NOT supported for this endpoint -- a live call with it returned "Must provide a valid Interaction ID" (a different, more fundamental rejection than a not-found), unlike the Get Journey/Get Event Definition endpoints this tool was originally modeled after. Use journey_get or journey_list to find the journey's current versionNumber.

Download journey history, the activity-level event rows for contacts moving through Journey Builder journeys, as CSV or TSV text for a bounded time window with optional journey, activity, contact, and status filters. Returns the raw delimited text with a header row (not JSON); the default columns are transaction time, contact key, status, journey id and name, and activity id, name and type. Each request is limited to 1 GB, history is kept for 30 days, and a failed download cannot be resumed. Use this to pull the event rows themselves. Call salesforcemarketingcloud_journey_history_download_estimate_get first to check the row count and size, and salesforcemarketingcloud_journey_history_download_freshness_get to see how far history trails live events. Keep the window small (about an hour) and filter to one journey where possible; the reference does not mark start and end as required, but this tool requires them so a response stays a manageable size. Prerequisites: the journey GUIDs to filter on (look them up with salesforcemarketingcloud_journey_list). Salesforce does not document a specific scope for this endpoint.

Estimate how many rows and how many bytes a journey history download would produce for a set of filters, without downloading any data. It sends a POST but only returns an estimate. Returns a JSON object with rowCount (approximate number of rows), downloadSize (estimated uncompressed size in bytes) and compressedSize (estimated compressed size in bytes). Use this before salesforcemarketingcloud_journey_history_download with the same time window and filters (tags is available only on this estimate tool); if compressedSize exceeds 1 GB, narrow the time window or filters first. Use salesforcemarketingcloud_journey_history_download_freshness_get instead to learn how far history trails live journey events. Prerequisites: the journey GUIDs to filter on if you want a single journey (look them up with salesforcemarketingcloud_journey_list). Salesforce does not document a specific scope for this endpoint.

Get how many seconds journey history events currently trail behind the actual events happening in journeys. Returns a JSON object with a single field secondsBehind, the number of seconds history trails live events; for example 1200 means history is 20 minutes behind, so a contact who exited a journey 10 minutes ago shows only a partial path. Use this before reading history with salesforcemarketingcloud_journey_history_download to know whether recent activity has landed yet, and use salesforcemarketingcloud_journey_history_download_estimate_get instead to size a download. Prerequisites: none; it takes no parameters. Salesforce does not document a specific scope for this endpoint.

Search/list journeys (Journey Builder interactions) in Salesforce Marketing Cloud via GET /interaction/v1/interactions, the collection form of the Interaction REST API used by the Get Journey tool. Requires the Automation | Journeys | Read scope. Supports filtering by status, a text search across name/description, external key, journey ID (returns all versions of that journey), tag, and definitionType, plus pagination and sorting. By default only the most recent version of each journey is returned. Use extras to include activity details, outcomes, or stats alongside each journey's base metadata. Each result includes id, key, name, description, status, version, createdDate, and modifiedDate. Example nameOrDescription search: "onboarding".

Check the status of an asynchronous journey publish request in Salesforce Marketing Cloud (GET /interaction/v1/interactions/publishStatus/{id}). Pass the statusId returned by the Publish Journey tool. Returns one of PublishInProcess, PublishCompleted, or Error, along with an errors array describing any publishing problems.

Search execution trace events to debug a specific contact's path through a Salesforce Marketing Cloud journey -- e.g. to find out why a contact didn't receive an email, where they exited, or which activities they hit (POST /interaction/v1/interactions/traceevents/search). Salesforce's own REST discovery document for the Interaction API confirms a path with this description exists ('Search for trace events stored in ElasticSearch') but publishes no request/response schema, so the request body shape here (interactionId, versionNumber, contactKey, activityId, startDate/endDate, page, pageSize) is inferred rather than documented. A live test against a real, valid journey returned a 404 regardless of body content, suggesting the journey ID may belong in the path (as with sibling endpoints like journey_pause) rather than the body, or that the field names differ from what's modeled here -- treat this tool as needing further verification before relying on it in production.

Check the status of an asynchronous journey validation request in Salesforce Marketing Cloud (GET /interaction/v1/interactions/validateStatus/{id}). Pass the statusId returned by the Validate Journey tool. By analogy with the confirmed, identically-patterned Get Journey Publish Status endpoint, the response is expected to include a status such as ValidateInProcess, ValidateCompleted, or Error, plus an errors array describing any validation problems. Salesforce's public REST discovery document and reference pages for the Interaction API do not currently list validateAsync/validateStatus at all (unlike publishAsync/publishStatus, which are fully documented). This tool is built by direct analogy to that documented publish-status pair; verify the actual status/field names against a sandbox account before relying on them in production.

Retrieve counts of contacts currently sitting in Wait activities (Wait By Duration, Wait Until, Wait Until API Event, etc.) for a journey in Salesforce Marketing Cloud Journey Builder (GET /interaction/v1/waitstatistics/{id}). Useful for seeing how many contacts are currently paused at each wait step. this path and its one-line description ('Retrieve wait activity counts for a journey') are confirmed to exist in Salesforce's own REST discovery document for the Interaction API, but Salesforce does not publish a full parameter/response reference page for it -- no request/response schema and no confirmation of optional query parameters. The id parameter is modeled here, by analogy with the documented Get Journey and Get Event Definition endpoints in this same Interaction API, as accepting either the journey's GUID or a key:{key} external-key reference; this key: support is NOT independently confirmed for waitstatistics specifically. Verify against a sandbox account before relying on it in production.

Retrieve a single tag definition by its numeric tag ID from Salesforce Marketing Cloud's Nested Tags REST API (GET /hub/v1/nestedtags/{tagId}). The response includes the tag's ID, name, description, parent tag ID (if nested), last modified date, and -- depending on the depth parameter -- its nested/child tags. Use this to inspect a specific tag before updating or deleting it, or to look up its current nested children.

Retrieve one registered Facebook Messenger page or LINE channel by platform and OTT property id. Returns the platform name and that registration's non-secret attributes, such as application, page or channel ids and names, endpoint URL, and the active, transactional and test-channel flags. The documented response contains no secret fields such as the application secret or access tokens. Use this to check a single registration, for example to confirm it is active before sending; use salesforcemarketingcloud_ott_chat_registration_list to browse all registrations for a platform and salesforcemarketingcloud_ott_chat_registration_create to add or change one. The documented examples use the Messenger page id or the LINE channel id as the property id. Requires the Provisioning > OTT Channels > Read permission on the installed package (the Chat Messaging API uses installed-package permissions only).

List the Facebook Messenger pages or LINE channels registered for one OTT platform in the Chat Messaging API, one page of results at a time. Returns count, page, pageSize, pagination links (self, previous, next) and an items array; each item holds the platform name and its non-secret attributes such as page or channel ids and names, endpoint URL, and the active, transactional and test-channel flags. The documented response contains no secret fields such as the application secret or access tokens. Use this to browse registrations or find the page or channel id to use as the sender in salesforcemarketingcloud_ott_chat_message_send; use salesforcemarketingcloud_ott_chat_registration_get for one known registration. Start at page 1 and increase it until no items come back. In the documented example the link hrefs are relative and omit the /ott prefix, so request the next page by passing page + 1 instead of following them. Requires the Provisioning > OTT Channels > Read permission on the installed package (the Chat Messaging API uses installed-package permissions only).

Retrieve the original request and the status event history of a Messenger or LINE message submitted through the Chat Messaging API. Returns requestBody (the stored send request, including messageKey, ottRequestId, sender, recipient, message and validity period) and a status array of events (Created, Queued, Sent, or Error) with their timestamps. The documented event types are Created, Queued, Sent and Error; no delivered or read events are documented. Use this after salesforcemarketingcloud_ott_chat_message_send to see whether a message was queued, sent or errored. Look it up with either the message key you supplied or the ottRequestId from the send response. Requires the Channels > OTT > Read permission on the installed package (the Chat Messaging API uses installed-package permissions only).

Resolve the base URL for a specific Marketing Cloud internal service or application by its symbolic name, using the Marketing Cloud Platform API's Endpoint resource (GET /platform/v1/endpoints/{name}). This is a low-level discovery call occasionally needed when integrating with Marketing Cloud sub-systems that publish their base URI dynamically per account/tenant rather than at a fixed, well-known host. Returns the resolved endpoint URL for the requested name. Valid names are account/tenant-specific and not a fixed, universal set (a live test against a real tenant confirmed a previously-documented-here example name, 'content_odata', is not valid on every account and returns "No endpoint exists for key 'content_odata'"), so don't assume any single name works everywhere. To discover the exact names valid for your account, call GET /platform/v1/endpoints (no name suffix), which returns every endpoint key configured for the tenant.

List every symbolic platform endpoint key configured for this Salesforce Marketing Cloud tenant, along with each key's resolved base URL, using the Marketing Cloud Platform API's Endpoint resource (GET /platform/v1/endpoints, no name suffix). Valid endpoint names are account/tenant-specific and not a fixed, universal set across all Marketing Cloud accounts -- the Get Platform Endpoint tool's own documentation flags this discoverability gap (a previously-documented example name, 'content_odata', was confirmed invalid on a live tenant). Call this tool first to see the exact endpoint keys and resolved URLs valid for your account, then pass one of the returned names to the Get Platform Endpoint tool if you need to resolve it again on demand.

List all custom key values associated with a MobilePush app. Returns the app's custom key values as JSON; read the returned structure rather than assuming a fixed shape. Use to review every custom key on an app before changing anything. Use salesforcemarketingcloud_push_app_get for the app's own details, salesforcemarketingcloud_push_app_custom_key_delete to remove a single key, and salesforcemarketingcloud_push_app_custom_key_delete_all to remove every key. Requires the push_read scope (Mobile Push > General > Access user permission) and the id of an existing MobilePush app.

Retrieve a single MobilePush app (application) associated with the Marketing Cloud account by its id. Returns the app's details as JSON; read the returned fields rather than assuming a fixed shape. Invalid input returns a 400 error with error details. Use to look up one specific app. Use salesforcemarketingcloud_push_app_custom_key_list to see the custom key values stored on that app instead of the app itself. Requires the push_read scope (Mobile Push > General > Access user permission) and the id of an existing MobilePush app.

Get the status of a MobilePush list (audience) refresh, identified by the list id and the refresh token. Returns the refresh details for that list and token as a JSON object (documented fields: tokenId and publishDate). Use this after salesforcemarketingcloud_push_audience_refresh, which only starts the refresh, to check the refresh result. For SMS lists use salesforcemarketingcloud_sms_audience_refresh_status_get instead. Requires the push_read scope (Mobile Push > General > Access user permission) and the tokenId returned by salesforcemarketingcloud_push_audience_refresh.

Retrieve a single MobilePush location (a geofence or a beacon) by its id. Returns the stored definition of that location as a JSON object; the response fields are not specified here, so read what comes back rather than assuming a fixed shape. Use this to inspect one location whose id you already know, for example before changing it with salesforcemarketingcloud_push_location_update. Use salesforcemarketingcloud_push_location_create to define a new one. Requires the push_read scope (Mobile Push > General > Access user permission) and the id of an existing location, for example one returned when it was created with salesforcemarketingcloud_push_location_create.

Get the delivery status of a MobilePush message that was sent to all users of an app (messageApp), identified by the message id and the send token. Returns the delivery status for that specific send as a JSON object; the documented example contains the message name, a count and a createDate, but read what comes back rather than assuming a fixed structure. Use this for sends made through the messageApp send request; use salesforcemarketingcloud_push_message_tag_delivery_get for sends made to tagged users, salesforcemarketingcloud_push_message_list_delivery_get for sends made to lists, and salesforcemarketingcloud_push_message_contact_delivery_get for sends made to contacts. Requires the push_read scope (Mobile Push > General > Access user permission) and the send token returned by the messageApp send request (POST /push/v1/messageApp/{messageId}/send).

Get the delivery status of a MobilePush message that was sent to specific contacts or devices, identified by the message id and the send token. Returns the delivery status for that specific send as a JSON object with messageId, message.id, status, count, createDate, scheduledDate and triggeredSendStatus. Use this for sends made through the messageContact send request (Send Message to Mobile Devices); use salesforcemarketingcloud_push_message_list_delivery_get for sends made to lists, salesforcemarketingcloud_push_message_app_delivery_get for sends made to all app users, and salesforcemarketingcloud_push_message_tag_delivery_get for sends made to tagged users. Requires the push_read scope (Mobile Push > General > Access user permission) and the token returned by the messageContact send request (POST /push/v1/messageContact/{messageId}/send); the caller must supply that token from the earlier send response.

Get the delivery status of a previous send job for a push message in Salesforce Marketing Cloud MobilePush, via GET /push/v1/message/{id}/deliveries. Returns a paginated collection of delivery records for the push message, showing per-send-job status information (e.g. queued/sent/failed counts and timestamps) for each time this message has been sent. Use this to check the outcome of a send triggered with the Send Push Message tool.

Retrieve a single push message template from Salesforce Marketing Cloud MobilePush by its id, via GET /push/v1/message/{id}. Returns the message's full definition (name, keyword, message content/alert, sound, targeting configuration, and status). Use the List Push Messages tool to find a message's id if you don't already have it.

Retrieve and sort push message templates configured in Salesforce Marketing Cloud MobilePush, via GET /push/v1/message. Push messages are the message templates created with the Create Push Message tool for sending to a subscriber list, audience inclusion list, or data extension. Supports paging ($page/$pageSize) and an $orderBy expression to sort results (e.g. by name or lastUpdated). Use this to find an existing push message's id before getting its details, updating it, sending it, or checking its delivery status.

Get the delivery status of a MobilePush message that was sent to lists, identified by the message id and the send token. Returns the delivery status for that specific send as a JSON object with messageId, message.id, status, count (the number of contacts the send attempted to reach, not including those who opted out), createDate and completeDate. Use this for sends made through the messageList send request; use salesforcemarketingcloud_push_message_contact_delivery_get for sends made to specific contacts or devices, salesforcemarketingcloud_push_message_app_delivery_get for sends made to all app users, and salesforcemarketingcloud_push_message_tag_delivery_get for sends made to tagged users. Requires the push_read scope (Mobile Push > General > Access user permission) and the token returned by the messageList send request (POST /push/v1/messageList/{messageId}/send); the caller must supply that token from the earlier send response.

Get the delivery status of a MobilePush message that was sent to tagged users (messageTag), identified by the message id and the send token. Returns the delivery status for that specific send as a JSON object; the documented example contains the message name, a count and a createDate, but read what comes back rather than assuming a fixed structure. Use this to check a tag send made with salesforcemarketingcloud_push_message_send_to_tag; use salesforcemarketingcloud_push_message_app_delivery_get for sends made to all app users, salesforcemarketingcloud_push_message_list_delivery_get for sends made to lists, and salesforcemarketingcloud_push_message_contact_delivery_get for sends made to contacts. Requires the push_read scope (Mobile Push > General > Access user permission) and the send token returned by salesforcemarketingcloud_push_message_send_to_tag.

List the SSJS (Server-Side JavaScript) script activities in Automation Studio, optionally filtered, trimmed to chosen fields and paged. Returns a page of results with the total count, the page number, the page size and an items list; each item carries the activity's ID (ssjsActivityId), name, key, status, category, created and modified dates and the full script source, so responses can be large. Use this to find a script activity and its ID before calling salesforcemarketingcloud_script_activity_start. Pass fields to request only chosen properties (for example to leave out the script source), and filter to look up one activity by name. Use salesforcemarketingcloud_automation_list to browse automations rather than script activities. Prerequisites: an Installed Package with the automations_read scope.

Retrieve logged Security Events for this Salesforce Marketing Cloud account and its child business units, using GET /data/v1/audit/securityEvents. Security Events record enterprise-level login/authentication activity (e.g. successful and failed sign-in attempts), as distinct from the sibling GET /data/v1/audit/auditEvents endpoint, which records administrative/configuration changes such as user and role updates. Each item in the response includes an id, createdDate, memberId, enterpriseId, the employee involved (id, employeeName, userName), the event/objectType (e.g. a login-related type), the operation performed, source details such as the originating IP address, and a transactionId — exact field names should be confirmed against a live response, since a fully public Salesforce Developers reference page for this exact operation could not be independently reloaded at authoring time. Results are paginated and sortable. Requires the account's Installed Package to have the Tracking Events Read (tracking_events_read) scope. Confirmed against Salesforce's official 'Salesforce Marketing Cloud APIs' Postman collection (folder: REST > Audit > Get Audit Events / Get Security Events) — the same collection the sibling audit_events_list tool in this connector was verified against. The page-size query parameter is sent as the lower-cased '$pagesize' (not '$pageSize'), matching the exact casing confirmed in that collection's example request for this endpoint; the full set of supported query parameters beyond $page/$pagesize/$orderBy (e.g. a possible $filter) is still not guaranteed and should be confirmed in testing.

List the HTTP security headers currently applied to the business unit's SAP-branded view and click domains. Returns one entry per page type (view or click), each holding the id and name of every header applied to that domain, plus a requestId. Header values are not included. Use this to check the current state before changing it, or to confirm the result after salesforcemarketingcloud_security_header_update or salesforcemarketingcloud_security_header_delete, which return HTTP 202 (Accepted). Use salesforcemarketingcloud_security_header_available_list instead to see every header that could be applied and its default value. Prerequisites: the integration user needs the Security > HTTP Headers > View user permission; the docs name no API scope for this endpoint, but the connector's http_headers_view scope corresponds to that permission.

List every HTTP security header that Marketing Cloud lets you apply to SAP-branded view and click domains, together with each header's default value. Returns the full catalog of nine headers, each with its numeric id, header name and default value, plus a requestId. Image and CloudPage domains are not covered by this API. Use this to look up valid header ids and exact names before changing anything. Use salesforcemarketingcloud_security_header_applied_list instead to see which headers a business unit currently has applied, which is a different and usually smaller set. Prerequisites: the integration user needs the Security > HTTP Headers > View user permission; the docs name no API scope for this endpoint, but the connector's http_headers_view scope corresponds to that permission. Take the ids and names returned here and pass them unchanged to salesforcemarketingcloud_security_header_update.

Read the account-level auto-seed settings for the business unit (MID) behind the access token: which seed list is applied automatically, its threshold, and whether auto-seed is enabled. Returns the auto-seed list's GUID and name, the auto-seed threshold and the enabled flag; the body is an empty object when the MID has no seed-list account entry, and a 400 means no active auto-seed-list mapping exists for the MID. Use this to see how automatic seeding is configured for the account. Use salesforcemarketingcloud_seed_list_get or salesforcemarketingcloud_seed_list_list instead to read the seed lists themselves and their email addresses; they do not return these account settings. Use salesforcemarketingcloud_seed_list_account_update to change these settings. Prerequisites: requires the email_read scope (Email > Content > Email > View permission); the seed-list APIs return 403 when that permission is missing, and the MID may also need to be activated for seed lists as a partner app.

Retrieve a single seed list by its GUID from Salesforce Marketing Cloud using the Email Seed List REST API. A seed list is a set of monitored inbox addresses (seeds) used for inbox-placement and deliverability testing of email sends. The response includes the seed list's id, name, description, and its array of seed email addresses. The seed list must belong to the same MID/Partner AppID used for authentication, or the request returns a 401/404. Obtain the id from the List Seed Lists tool's response. Example id: 8f14e45f-ceea-467e-9575-3ab4f8f8f8f8.

List the email seed lists configured for this Salesforce Marketing Cloud account, using GET /messaging/v1/email/seed-lists. A seed list is a set of monitored inbox addresses used for inbox rendering and deliverability testing before sending a real campaign. Each item in the response includes the seed list's ID, name, description, and active seed count. An account can have up to 20 seed lists.

Get the status of a previously triggered SMS audience/list refresh, via GET /sms/v1/contacts/refreshList/{id}/status/{tokenId}. The id is the MobileConnect list ID that was refreshed, and tokenId is the value returned by the Refresh SMS Audience tool. Salesforce's own example response returns tokenId and publishDate, confirming the refresh completed and when the list was republished; the existing Refresh SMS Audience tool only triggers the refresh, so use this tool to check whether it finished. If the request is invalid, Salesforce returns HTTP 400 with error details. Example id: bzZ0cENGam1FZUtNX0poTDRYZzhlQTo2Mzow, example tokenId: NDo8NDow.

Get the status of a queued SMS contact import job, via GET /sms/v1/contacts/queueImport/{id}/status/{tokenId}. The id is the MobileConnect list ID the import targeted, and tokenId is the value returned by the Queue SMS Contact Import call. Salesforce's own example response returns tokenId, status (e.g. Completed), createdDate, and type. Example id: UEhwdktFWXpFZUs3Z3hRUW45R2dBQTo2Mzow, example tokenId: NzY2MTU6NDI6MA.

Get the status of a SMS ImportSend automation job in Salesforce Marketing Cloud, via GET /sms/v1/automation/importSend/{tokenid}/status. The tokenid is the tokenId returned in the response of the Import Contacts and Send SMS call. Salesforce's own example response returns status (e.g. Complete), lastUpdate, createdTime, startTime, completedTime, lastRunTime, source (the original file/data extension name), and counts of inserted, updated, and invalid records from the import. Example tokenId: NDo8NDow.

Retrieve the overall delivery status of a MobileConnect SMS message sent to a contact, plus the per-recipient tracking history. Requires the message ID and the token ID that were both returned in the response of the original send call (POST /sms/v1/messageContact/{id}/send). Returns a top-level status (New, Queuing, Started, Finished, or Error), the message count, create/complete timestamps, and a tracking array with one entry per recipient containing mobileNumber, statusCode, standardStatusCode, and description. Because carriers can report multiple status codes over time for the same message, infer the final delivery outcome from the tracking entry with the highest-numbered standard status code. Both IDs are opaque encoded strings (not GUIDs) — Salesforce's own docs show values like messageId 'MTA3ODo3ODow', tokenId 'MENqMHZHV2x3a0M1dG1iOHVnam9LZzo3OTow'.

Retrieve the message history for a specific mobile number tied to a MobileConnect SMS send job. Requires the message ID and token ID returned by the original send call (POST /sms/v1/messageContact/{id}/send) plus the recipient's mobile number. Returns the last message(s) sent to that mobile number for the job, including message type, content, and timestamp for each history entry. Use this to inspect exactly what content a specific recipient received. Both IDs are opaque encoded strings (not GUIDs) — Salesforce's own docs show values like messageId 'MTA3ODo3ODow', tokenId 'MENqMHZHV2x3a0M1dG1iOHVnam9LZzo3OTow', mobileNumber 1120816001.

Retrieve the delivery status of a MobileConnect SMS message sent to a contact list, via GET /sms/v1/messageList/{id}/deliveries/{tokenId}. This is the list-send counterpart to the existing per-contact delivery status tool: pass the message list definition ID and the token ID returned by the original Send SMS to List call. Returns a top-level status (New, Queuing, Started, Finished, or Error), a message count, create/complete timestamps, and a tracking array with one entry per recipient (mobile number, carrier status code, and message). Confirmed directly from Salesforce's REST API reference (Get Message List Status), which documents this exact response shape with a 200 response on success and a 400 with an errors array on invalid parameters.

Retrieve the delivery status of a queued mobile-originated (MO) message, via GET /sms/v1/queueMO/deliveries/{tokenId}. Pass the token ID returned by the original Queue Mobile-Originated (MO) Message call. Returns a tracking array with one entry per simulated recipient, each containing the mobile number, carrier status code, and a status message (e.g. 'Carrier Success') -- useful for confirming that a simulated inbound test message was accepted and processed. Confirmed directly from Salesforce's REST API reference (getQueueMODelivery), which documents this exact response shape.

Retrieve the full interaction history of a queued mobile-originated (MO) message, via GET /sms/v1/queueMO/history/{tokenId}. Pass the token ID returned by the original Queue Mobile-Originated (MO) Message call. Returns a message count, create timestamp, overall status, and a history array of individual message/response events (each with a type of MT or MO, the message text, and a timestamp) -- useful for tracing the full back-and-forth an inbound test message triggered, such as keyword auto-replies or double opt-in prompts. Confirmed directly from Salesforce's REST API reference (getQueueMOHistory), which documents this exact response shape.

List all tags (and, optionally, their nested/child tags) owned by the requesting client in Salesforce Marketing Cloud, using the Nested Tags REST API (GET /hub/v1/nestedtags). Each returned tag includes its ID, name, description, parent tag ID (if nested), and last modified date. Use this to discover existing tag names before associating them with objects (e.g. campaigns, journeys, media) via the Create Tag Associations tool. Salesforce's documentation describes the response body as a JSON array of tag objects, but a live test against a real tenant with zero tags configured for its requesting client returned a null body instead of an empty array. Treat a null (or otherwise non-array) response as equivalent to zero tags, not as an error.

Retrieve a Transactional Messaging email send definition from Salesforce Marketing Cloud by its definition key, via GET /messaging/v1/email/definitions/{definitionKey}. Returns the definition's configuration: name, description, classification, the Content Builder email asset it sends (content.customerKey), its subscriptions settings (list, data extension, autoAddSubscriber, updateSubscriber), and send options (trackLinks, cc, bcc). Use this to inspect a transactional email definition's configuration before sending through it or before updating it. Example definition key: order_confirmation_transactional.

Get a paginated list of every Transactional Messaging email send definition in the account, via GET /messaging/v1/email/definitions -- the collection form of the Get Transactional Email Definition tool (GET /messaging/v1/email/definitions/{definitionKey}). Each entry is expected to carry the same kind of configuration as the single-definition get: name, description, classification, the Content Builder email asset it sends, subscription settings, and send options. Use this to enumerate all email send definitions before looking up or updating a specific one by key. Confidence note: this endpoint's existence was confirmed via a Salesforce documentation search-index page title, but its exact response shape and pagination parameter names were not independently verified (no live call was made during authoring). The optional page and page_size inputs below are modeled on the pagination style used elsewhere in this Messaging API family as a best-effort default -- if Salesforce's real parameter names differ, drop or adjust them once you see an actual response.

Get queue metrics for a Transactional Messaging email send definition, via GET /messaging/v1/email/definitions/{definitionKey}/queue. Intended to report how many records are currently waiting to be processed for this definition and how long the oldest unprocessed record has been sitting in the queue, so you can spot an email send definition that is backed up before it causes delivery delays -- the email equivalent of the Get Transactional SMS Definition Queue tool. Confidence note: this endpoint's existence was confirmed via a Salesforce documentation search-index page title; the exact field names in the response were not independently verified (no live call was made during authoring), so treat the returned payload's shape as approximate until you've seen a real response. Example definition key: order_confirmation_transactional.

Get a paginated list of Transactional Messaging email messages that were NOT sent to their recipients, oldest to newest, via GET /messaging/v1/email/messages/?type=notSent. This is the email equivalent of the SMS 'messages not sent' list tool, and the bulk counterpart to the Get Transactional Email Send Status tool (which looks up one message by messageKey) -- use it to sweep for failed sends across a definition instead of checking messages one at a time. Each entry is expected to identify the message and describe why it wasn't sent (an event/category type, a timestamp, and details such as the failing status code and message). Confidence note: this endpoint's existence was confirmed via a Salesforce documentation search-index page title; the exact response shape and pagination parameter names were not independently verified (no live call was made during authoring). The optional page and page_size inputs below are a best-effort guess at pagination based on similar list endpoints in this API family -- adjust them once you've seen a real response.

Get the send status of a transactional email message in Salesforce Marketing Cloud by its messageKey, via GET /messaging/v1/email/messages/{messageKey}. This is the email equivalent of the Get Transactional SMS Send Status tool -- the messageKey is the caller-supplied unique identifier that was provided as the path segment when the message was sent with the Send Transactional Email tool. Expected to return an event/category type (e.g. an equivalent of TransactionalSendEvents.EmailSent, EmailQueued, or EmailNotSent for SMS), a timestamp, and an info object identifying the message and recipient, with a failure code/message included when the send did not succeed. Confidence note: this endpoint's existence was confirmed via a Salesforce documentation search-index page title, by direct analogy to the confirmed SMS status-get endpoint at the same API path shape; the exact response field names were not independently verified (no live call was made during authoring). Example messageKey: order-42981-email-01.

Retrieve an OTT (over-the-top messaging: Facebook Messenger or LINE) send definition from Salesforce Marketing Cloud by its definition key, using the Transactional Messaging - OTT API (GET /messaging/v1/ott/definitions/{definitionKey}). Returns the definition's metadata (name, description, status), its configured message content, and its sending network/account configuration. Use this to inspect an OTT definition before sending or updating it. Example key: OTT_OrderUpdates.

Retrieve a transactional push notification send definition from Salesforce Marketing Cloud by its definition key, using the Transactional Messaging - Push API (GET /messaging/v1/push/definitions/{definitionKey}). Returns the definition's metadata (name, description, status) and its configured notification content and subscription/app targeting. Use this to inspect a push definition's current configuration before sending or updating it. KNOWN SALESFORCE BEHAVIOR: the path and method here are correct and match the identical /messaging/v1/<channel>/definitions/{key} pattern used by the sibling Get Transactional Email/SMS Definition endpoints, but for a nonexistent definition_key this particular Push endpoint has been observed to return a raw HTTP 500 (body like {"errorcode":0,"message":"Internal Server Error"}) instead of the structured not-found error (MCMS_UTM_Runtime_ObjectNotFound-style) that the Email/SMS definition-get endpoints return for the same scenario. Treat a 500 from this call as 'definition_key probably doesn't exist' and re-verify the key (e.g. via the Create/Update response or Marketing Cloud UI) rather than assuming an outage. Example key: PUSH_OrderShipped.

Retrieve a Transactional Messaging SMS send definition from Salesforce Marketing Cloud by its definition key, via GET /messaging/v1/sms/definitions/{definitionKey}. Returns the definition's configuration: name, description, status (active/inactive), message content, subscriptions settings (shortCode, countryCode, keyword, autoAddSubscriber, updateSubscriber), and options (URL shortener settings, regulatory template id). Use this to inspect a transactional SMS definition's configuration before sending through it or before updating it. Example definition key: order_shipped_sms.

Get a paginated list of every Transactional Messaging SMS send definition in the account, via GET /messaging/v1/sms/definitions -- the collection form of the Get Transactional SMS Definition tool (GET /messaging/v1/sms/definitions/{definitionKey}). Each entry is expected to carry the same kind of configuration as the single-definition get: name, description, active/inactive status, message content, and subscription settings. Use this to enumerate all SMS send definitions before looking up or updating a specific one by key. Confidence note: this endpoint's existence was confirmed via a Salesforce documentation search-index page title, but its exact response shape and pagination parameter names were not independently verified (no live call was made during authoring). The optional page and page_size inputs below are modeled on the pagination style used elsewhere in this Messaging API family (e.g. the notSent message list endpoints) as a best-effort default -- if Salesforce's real parameter names differ, drop or adjust them once you see an actual response.

Get queue metrics for a Transactional Messaging SMS send definition, via GET /messaging/v1/sms/definitions/{definitionKey}/queue. Intended to report how many records are currently waiting to be processed for this definition and how long the oldest unprocessed record has been sitting in the queue, so you can spot a send definition that is backed up before it causes delivery delays. Confidence note: this endpoint's existence was confirmed via a Salesforce documentation search-index page title; the exact field names in the response were not independently verified (no live call was made during authoring), so treat the returned payload's shape as approximate until you've seen a real response. Example definition key: order_shipped_sms.

Get a paginated list of Transactional Messaging SMS messages that were NOT sent to their recipients, oldest to newest, via GET /messaging/v1/sms/messages/?type=notSent. This is the bulk/list counterpart to the Get Transactional SMS Send Status tool (which looks up one message by messageKey) -- use it to sweep for failed sends across a definition instead of checking messages one at a time. Each entry is expected to be similar in shape to the single-message status lookup: an eventCategoryType such as TransactionalSendEvents.SMSNotSent, a timestamp, and an info object identifying the message and the failure reason. Confidence note: this endpoint's existence was confirmed via a Salesforce documentation search-index page title; the exact response shape and pagination parameter names were not independently verified (no live call was made during authoring). The optional page and page_size inputs below are a best-effort guess at pagination based on similar list endpoints in this API family -- adjust them once you've seen a real response.

Get the send status of a transactional SMS message in Salesforce Marketing Cloud by its messageKey, via GET /messaging/v1/sms/messages/{messageKey}. The messageKey is the caller-supplied unique identifier that was provided as the path segment when the message was sent with the Send Transactional SMS tool. This route is rate-limited and intended for infrequent, ad-hoc verification (statuses are retrievable for up to 3 days); for real-time tracking at scale, subscribe to transactional send events via the Event Notification Service instead. Returns eventCategoryType (e.g. TransactionalSendEvents.SMSSent, TransactionalSendEvents.SMSQueued, or TransactionalSendEvents.SMSNotSent), a timestamp, and an info object with messageKey, contactKey, and — if not sent — statusCode/statusMessage describing the failure reason. If more than one message was sent with the same messageKey, the status of the most recently sent message is returned. Example messageKey: order-42981-sms-01.

Retrieve active workflow teams from Salesforce Marketing Cloud's Approvals Hub REST API (GET /hub/v1/workflowteams/{objecttype}). Workflow teams are the groups of users that approval items (content pending review, e.g. emails or journeys) can be assigned to. Optionally scope results to a specific workflow object type (e.g. EmailSendDefinition) or leave the default '@all' to return teams for every object type, filter to only the teams the current user belongs to, and include each team's role/user membership in the response. Use this before assigning or reassigning an approval item to a team. Note: Salesforce's own documentation does not describe any restriction or interaction between object_type, assignee, and extra, but live testing observed identical object_type='@all' calls returning a 403 'Insufficient Privileges' in one case and a 400 'No workflow teams foundt type: @all' in another, depending on which other parameters were also supplied — this is undocumented Salesforce-side behavior, not a parameter-combination rule this tool enforces, so treat either error as a sign to retry with a specific object_type or to check the account's Approvals/workflow permissions rather than as a definitive 'no teams exist' result.

Create an approval item and its associated workflow item in Salesforce Marketing Cloud via the Approvals API. Approval items route a Marketing Cloud object (such as an email send, journey, or asset) through a configured approval workflow before it can proceed. Requires the id of an existing workflow item (workflow_item_id) — approval workflows are configured in Marketing Cloud Setup. Fails with 409 if an active approval already exists for the given object, or 400 if required fields are missing or the workflow/team/approver configuration is invalid.

Modify the name, description and deadline of an existing approval item in the Marketing Cloud Approvals v2 API. Returns the updated approval item: its name, description, workflow state, workflow type, deadline, comment counts, and the workflow item's current state with the transitions available to the current user's roles. Use this to rename or re-date an approval; use approval_item_get to read an item first, and workflow_item_transition to move it through its workflow (submit, approve, reject). Name, description and has_deadline are all required on every call, so read the item first and resend the values you want to keep. Requires the approvals_write scope and the id of an existing approval item from approval_items_list or approval_item_create.

• Idempotent

Update an approvals setting in Marketing Cloud's Approvals v2 API; currently only the EnableEmailApprovals setting can be changed. Returns the approvals settings for the current user, as a key and its true/false value. Use this to turn email approvals on or off for the account; use approval_settings_get to read the current settings first. Requires the approvals_write scope (the Approvals permission that allows enabling approvals for any channel).

• Idempotent

Create a new category (folder) in Content Builder under a given parent folder, using the Salesforce Marketing Cloud Asset REST API. Requires a Name and the numeric ParentId of the folder it should be created inside (use the List Content Categories tool to find valid parent IDs, such as your account's root Content Builder folder). Returns the created category, including its newly assigned numeric id.

Rename or move a Content Builder category (folder) in Salesforce Marketing Cloud. This is a full replace of the category record, so provide its current name and parent_id even if you are only changing one of them (e.g. keep name the same while changing parent_id to move the folder, or keep parent_id the same while changing name to rename it).

• Idempotent

Create a new Content Builder asset in Salesforce Marketing Cloud, such as an HTML email, template, content block, or image. Requires a name and an assetType (the numeric type ID, e.g. 208 for htmlemail, 207 for templatebasedemail, 197 for htmlblock, 8 for image). Content is supplied either via the views object (e.g. views.html.content for the HTML body of an email, views.subjectline.content for the subject line), the top-level content string, or a base64-encoded file for binary asset types. Returns the created asset object including its assigned numeric id.

Partially update an existing Content Builder asset in Salesforce Marketing Cloud by its numeric asset ID. Only the fields you provide are changed; omitted fields keep their current values. Use this to rename an asset, move it to a different category, edit its content/views (e.g. an email's HTML body or subject line), or update its tags/description.

• Idempotent

Create a new automation (Automation Studio program) in Salesforce Marketing Cloud via POST /automation/v1/automations. An automation is a saved chain of steps, where each step runs one or more activities (e.g. a Query Activity, Data Extract, File Transfer, or Send) in sequence, kicked off by a schedule or a file-drop trigger. Provide the automation's name and, optionally, its key, description, folder (categoryId), the ordered steps array, and a startSource object describing how it runs. Steps and startSource can be omitted to create an empty automation shell that you configure later in Automation Studio or via the Update Automation tool. Each step object looks like {"stepNumber": 1, "activities": [{"name": "My Query", "objectTypeId": 300, "activityObjectId": "<GUID of an existing Query Activity>", "displayOrder": 1}]} — activityObjectId must reference an activity definition that already exists in Automation Studio (this tool does not create the underlying activities). objectTypeId identifies the kind of activity: common values are 300=Query Activity, 43=Import Activity, 45=File Transfer, 423=Script Activity -- don't reuse 43 for a Query Activity, that id belongs to Import. A startSource of {"typeId": 1, "schedule": {...}} schedules the automation on a recurring basis; {"typeId": 2, "fileDrop": {"folderLocation": "...", "filenamePatternTypeId": 0, "queueFiles": true}} triggers it on a file drop. If no key is provided, Marketing Cloud generates one automatically. The response includes the new automation's ObjectID (GUID, use this as 'id' for the Get/Update/Start/Delete Automation tools) and its automationLegacyId (a separate numeric ID needed by the legacy-namespaced Get Automation Status and Pause Automation tools). Note: the Automation Studio REST API is not part of Salesforce's officially documented API surface, though it is widely used in production integrations; verify request/response shapes during testing.

Pause a scheduled automation (Automation Studio program) in Salesforce Marketing Cloud so it won't run again until reactivated, via POST /legacy/v1/beta/bulk/automations/automation/definition/?action=pauseSchedule — confirmed via production SFMC tooling as the real mechanism behind Automation Studio's 'Pause' button (there is no /automation/v1/automations/{id}/actions/pause endpoint; pausing operates on the automation's schedule in the legacy REST namespace). Requires two numeric legacy identifiers, both found via the Get Automation Status tool: automation_legacy_id (the automation's automationLegacyId) and schedule_legacy_id (the id inside that response's scheduleObject). Pausing only applies to schedule-triggered automations — file-drop and trigger-based automations don't have a schedule to pause. After pausing, the automation's status becomes Paused; use the Get Automation Status tool to confirm, and Automation Studio's UI (or a subsequent schedule update) to resume it. Example automation_legacy_id: 4821, example schedule_legacy_id: 9310.

Manually start an automation (Automation Studio program) immediately in Salesforce Marketing Cloud via POST /automation/v1/automations/{id}/actions/start, bypassing its configured schedule or file-drop trigger. Requires the automation's ObjectID (a GUID), as returned by the Create Automation or List Automations tools; the caller's Installed Package needs the automations_execute scope. The automation must be in a runnable state (e.g. Ready) — starting one that is already Running, Building, or has a configuration error will fail. Each call kicks off one run; calling it again while a run is already in progress starts a separate concurrent run rather than being a no-op. Use the Get Automation or Get Automation Status tool afterward to confirm the run started and to monitor its progress. Note: this action endpoint follows the same /actions/<verb> convention documented for other Automation Studio resources (e.g. Query Activities' /automation/v1/queries/{id}/actions/start) but is not itself part of Salesforce's officially published REST API reference; verify behavior during testing. Example id: 8f14e45f-ceea-467e-bd3a-45b3f4b3e21f.

Start an Automation Studio automation that uses a file-drop Trigger start source, by reporting the file that landed on its file location. Returns a request ID (a GUID) for the trigger request; find it in the response body and pass it to salesforcemarketingcloud_automation_trigger_status_get as request_id. The call only registers the request, so the outcome (Queued, Triggered, NoAutomationFound and so on) is read with the status tool, and duplicate requests can be reported as Deduplicated. Use this after a file arrives on SFTP, Amazon S3 or Azure Blob Storage to fire the automation whose Trigger start source matches that file location and file name. Check the outcome with salesforcemarketingcloud_automation_trigger_status_get using the returned request ID. Use salesforcemarketingcloud_automation_start to run an automation on demand without a file-drop trigger. Prerequisites: an automation whose Trigger start source is configured with a matching file location and file naming pattern, the file location's external key (Customer Key) from salesforcemarketingcloud_file_transfer_location_list, and an Installed Package with the Automation | Automations Execute permission (community guidance for this route also lists Read and Write, so grant Read, Write and Execute if the call is rejected). Salesforce documents the related Check Trigger Status endpoint as Beta, so the Trigger API may need to be enabled for the account.

Update an existing automation's (Automation Studio program's) definition in Salesforce Marketing Cloud via PATCH /automation/v1/automations/{id} (confirmed via production SFMC tooling; PATCH, not PUT). Requires the automation's ObjectID (a GUID). Only the fields you provide are changed; omit a field to leave it as-is. You can rename it, change its description or folder (categoryId), replace its steps (the ordered chain of activities), or replace its startSource (schedule or file-drop trigger configuration) — see the Create Automation tool for the shape of steps and startSource. Replacing steps or startSource typically requires the automation to not be currently running. Example id: 8f14e45f-ceea-467e-bd3a-45b3f4b3e21f.

• Idempotent

Signal that all data has been staged for a bulk ingest job, as step 3 of Salesforce Marketing Cloud's Bulk Data Ingest workflow, triggering Marketing Cloud to validate the staged rows and begin importing them into the target Data Extension. Salesforce's public documentation describes this step ('complete the ingest job') only in prose - the exact path is not confirmed from a fetchable reference/OpenAPI source in this session. The path used here (POST /data/v1/bulk/ingest/{bulkApiDefinitionId}/complete) is inferred by analogy with the create-job endpoint and Salesforce's general Bulk API 2.0 convention of a '.../complete' or job-state-transition sub-resource. Call this once, after all batches have been uploaded with the Stage Bulk Ingest Job Data tool, then poll the Get Bulk Ingest Job Status tool to track validation/import progress and surface any row-level errors. Do not rely on this tool in production before smoke-testing it against a real Marketing Cloud sandbox and correcting the path_template if the API responds with a 404 or an unexpected error.

Create a bulk ingest job definition targeting a Data Extension in Salesforce Marketing Cloud, using the Bulk Data Ingest REST API (POST /data/v1/bulk/ingest, operation createBulkIngestJob). This is step 1 of the four-step Bulk Data Ingest workflow, purpose-built for loading millions of rows without the performance penalty of many small synchronous/async calls: (1) create the job definition here, (2) upload row batches to it with the stage-data tool, (3) finalize with the complete tool to trigger validation and import, (4) poll the status tool for progress/results. Provide destinationCustomerKey (the target Data Extension's customer/external key), updateType (how new vs. existing rows are handled), and optionally jobExpirationHours (how long the job definition stays valid before it must be completed, up to 8 hours). On success, returns a requestId and a bulkApiDefinitionId — the bulkApiDefinitionId is the job identifier required by the stage-data, complete, and status tools. This endpoint/operation is confirmed against an independently-generated OpenAPI specification that matches Salesforce's own documented operation name createBulkIngestJob for this route.

Upload one batch of rows to the staging area of a bulk ingest job created with the Create Bulk Ingest Job tool, as step 2 of Salesforce Marketing Cloud's Bulk Data Ingest workflow. Salesforce's public documentation describes this step ('stage your data') only in prose - the exact path and request-body shape are not confirmed from a fetchable reference/OpenAPI source in this session. The path used here (PUT /data/v1/bulk/ingest/{bulkApiDefinitionId}) is inferred by analogy with the create-job endpoint (POST /data/v1/bulk/ingest) and with Salesforce's general Bulk API 2.0 convention of PUT-ing batches to a job resource identified by its ID. The request body is sent as a bare JSON array of row objects (each object's keys matching the target Data Extension's column names), mirroring how Bulk API 2.0 batch payloads are structured - but whether Marketing Cloud expects a bare array here versus an object wrapper (e.g. {"items": [...]}) is also unconfirmed. Call this repeatedly to upload sequential batches for the same bulkApiDefinitionId, then call the Complete Bulk Ingest Job tool once all batches are staged. Do not rely on this tool in production before smoke-testing it against a real Marketing Cloud sandbox and correcting the path_template/body shape if the API responds with a 404 or a body-shape error.

Associate one or more existing Content Builder assets (emails, templates, images, etc.) or other Marketing Cloud objects (automations, data extensions, landing pages, etc.) with a campaign via the Hub API. The asset(s) must already exist — use the Content Builder Asset API to find numeric ids first. This does not create a new asset; it only links existing ones to the campaign for organization and reporting. Requires a type describing what kind of object the ids refer to (e.g. EMAIL for Content Builder emails, CMS_asset for other Content Builder assets).

Create a new campaign in Salesforce Marketing Cloud via the Hub API (Content Builder Campaigns feature). Campaigns are used to group and tag related Content Builder assets (emails, templates, etc.) for organization and reporting. All five fields (name, description, campaign_code, color, favorite) are required by the API. Returns the created campaign object including its system-assigned id.

Update an existing Salesforce Marketing Cloud campaign identified by id, via the Hub API. This is a full replace of the campaign's editable fields, so supply all current values (not just the ones you're changing) — fetch the campaign first with campaign_get if you need to preserve existing values. Returns the updated campaign object.

• Idempotent

Insert new data rows into a Contact Builder attribute set, addressing the set by its GUID or by its name with a name: prefix; each row is a list of attribute name and value pairs. Returns the operation status, the number of rows affected, a result for each submitted row (whether it was inserted, its position in the request, the stored attribute values with their IDs, and any messages), and the attribute set's ID, key, name and schema ID. Use this to add rows to an attribute set. Use salesforcemarketingcloud_contact_attribute_set_data_update to change rows that already exist and salesforcemarketingcloud_contact_attribute_set_data_search to read an attribute set's data by name. Use salesforcemarketingcloud_contact_update instead to write attribute data for one contact identified by its contact key. Requires the list_and_subscribers_write scope and the attribute set's GUID or exact name, which salesforcemarketingcloud_contact_attribute_sets_list can help you find.

Update existing data rows in a Contact Builder attribute set, addressing the set by its GUID or by its name with a name: prefix; each row is a list of attribute name and value pairs carrying the new values. Returns the operation status, the number of rows affected, a result for each submitted row (whether it was updated, its position in the request, the resulting attribute values with their IDs, and any messages), and the attribute set's ID, key, name and schema ID. Use this to change rows already in an attribute set. Use salesforcemarketingcloud_contact_attribute_set_data_insert to add new rows and salesforcemarketingcloud_contact_attribute_set_data_search to read an attribute set's data by name. Use salesforcemarketingcloud_contact_update instead to change attribute data for one contact identified by its contact key. Requires the list_and_subscribers_read and list_and_subscribers_write scopes, and the attribute set's GUID or exact name, which salesforcemarketingcloud_contact_attribute_sets_list can help you find.

• Idempotent

Create a new contact in Salesforce Marketing Cloud's Contact Builder using the Contacts REST API. A contact is identified by a unique Contact Key and is populated by writing one or more attribute sets (Contact Builder data extensions/attribute groups such as 'Email Addresses', 'Email Demographics', 'MobileConnect', or a custom data extension attribute set) onto it. At least one attribute set is required; to make the contact usable for Email Studio sends you typically must include the 'Email Addresses' attribute set with 'Email Address' and 'HTML Enabled' values. Returns operation status, whether the contact key was newly created, and the resulting numeric contactId.

Update the configuration settings of the Contact Delete framework in Salesforce Marketing Cloud; the only supported setting is SuppressionRestoreUntilDays, the number of days contacts stay suppressed before a contact delete takes effect (documented values: 0 days or 1 day). Returns a confirmation with a rows-affected count, the response timestamp, request and service message IDs, and any result messages. Use this to change how the delete framework is configured; it does not submit deletions. Use salesforcemarketingcloud_contact_delete to submit contact deletions, and salesforcemarketingcloud_contact_delete_options_get to look up the delete options registered for an application. Requires the list_and_subscribers_write scope.

• Idempotent

Establish one or more contacts by Contact Key: returns each contact's internal reference (contactID, contactType, contactStatus) if it already exists, or silently creates a bare contact record for any key that doesn't exist yet. This is the fastest way to get a stable contactID for a Contact Key before writing attribute data with Create/Update Contact. Note: the real Marketing Cloud endpoint for this operation is POST /contacts/v1/establish (not a nested /contacts/actions/ path).

• Idempotent

Create a new population, a type of attribute group, in Contact Builder under the name you supply. Returns the newly created population item, the operation status, and the service message IDs of the request and the response; on failure it returns an error message and an error code. Use this only to add a new population. Use salesforcemarketingcloud_contact_attribute_groups_list or salesforcemarketingcloud_contact_attribute_group_get to check which attribute groups already exist first, so you do not create a duplicate. Requires the list_and_subscribers_write scope (the IMH Contacts > Add user permission).

Record tracking-consent preferences (whether each contact has opted out of tracking) for many contacts at once, with every contact identified by its numeric contact ID. Returns the submitted contact entries together with counts of preferences inserted, updated and deleted, the request and service message IDs, and any result messages. Use this to write preferences for a batch of contacts in one request (Salesforce recommends batching for performance). Pass a one-item list to set a single contact's preference, and use salesforcemarketingcloud_contact_preferences_search, salesforcemarketingcloud_contact_preferences_get_by_id or salesforcemarketingcloud_contact_preferences_get_by_key to read current preferences. Requires the list_and_subscribers_read scope (IMH Contacts > Access, which Salesforce's scope table calls Contacts_access) and the numeric contact ID of every contact, which salesforcemarketingcloud_contact_search can look up.

Restrict processing for contacts in Salesforce Marketing Cloud, identified either by numeric Contact IDs or by Contact Keys. The operation runs asynchronously. Returns an operation ID to track the request, a flag saying whether the operation was initiated, a has-errors flag, and result messages along with request and service message IDs. Use the returned operation ID with salesforcemarketingcloud_contact_restrict_status_get to poll progress, and with salesforcemarketingcloud_contact_restrict_retry if the operation fails. This restricts processing only; use salesforcemarketingcloud_contact_delete to permanently remove contacts. Requires the list_and_subscribers_write scope.

Retry a failed contact restrict operation in Salesforce Marketing Cloud by its operation ID. Returns the operation ID, a flag saying whether the operation restarted, the response timestamp, request and service message IDs, and any result messages. Use this only after a restrict request has failed. Use salesforcemarketingcloud_contact_restrict_status_get to check an operation's outcome (before or after the retry) and salesforcemarketingcloud_contact_restrict to submit a new restrict request rather than retry an old one. Requires the list_and_subscribers_write scope and the operation ID returned by an earlier restrict request.

Update an existing contact's attribute data in Salesforce Marketing Cloud using the Contacts REST API. Identify the contact by its Contact Key and supply one or more attribute sets (Contact Builder data extensions/attribute groups) whose values should be written. Only the attribute sets you include are modified; other data on the contact is left unchanged. Returns operation status and the resulting contactId.

• Idempotent

Create a new data extension (custom object) schema in Salesforce Marketing Cloud via the Custom Object REST API (POST /data/v1/customobjects). Define the data extension's name, folder, optional external key, whether it's usable as a send audience, and its columns (each with a name, type, and which one serves as the primary key). Live-confirmed: the folder ID is required -- a call without it is rejected, despite this field once implying an account default existed. Get a valid folder ID from the categoryId of any existing data extension (returned by Get or List Data Extension) or from Contact Builder / Email Studio's folder view. This only creates the schema/structure; use a separate data-rows tool to insert rows afterward. On success, returns the created data extension's key, name, and fields.

Queue and start a one-time import of data from a file already sitting on a configured File Transfer Location directly into a Data Extension in Salesforce Marketing Cloud, using POST /data/v1/async/import. This lets you trigger a bulk file-based import without first creating a reusable Import Definition/Automation Studio import activity -- the source file, target Data Extension, column-mapping strategy, and file transfer location are all specified inline in a single call. The call returns immediately with an id identifying the queued import job; poll the Get Data Extension Import Status tool (GET /data/v1/async/import/{id}/summary) with that id to check progress and row counts, and use the Get Data Extension Import Validation Summary/Result tools to inspect any rejected rows. Before calling this: the source file must already exist at the given location (upload it there separately -- this tool does not upload file bytes), the File Transfer Location must already exist (see the File Transfer Location tools), and the target Data Extension must already exist (see Create Data Extension). Salesforce's official reference page for this resource (developer.salesforce.com/docs/marketing/marketing-cloud/references/mc-import_job_api) is a client-rendered page that returned a 403/empty shell on every fetch attempt at authoring time -- the same bot-protection behavior already documented on this connector's File Transfer Location tools -- so the exact request body shape below could not be confirmed against the primary source. It is instead a best-effort reconstruction cross-checked across multiple independent third-party technical write-ups describing this Spring '24 Salesforce Marketing Cloud REST API feature (a dedicated SFMC blog post and its author's own translated mirror, corroborated by several independent secondary summaries that separately named the same field names: source.fileInfo.{specifier,contentType,hasMultipleFiles,standardQuotedStrings}, target.{type,key,updateType}, mapping.{fieldMappingType,allowErrors}, transport.key). Smoke-test this call against a real tenant before relying on it in production -- updateType and fieldMappingType's exact accepted values are the most likely point of divergence from your account's behavior, and Overwrite is destructive to the target Data Extension's existing contents if chosen.

Queue an asynchronous INSERT of rows into a Data Extension addressed by its external key; the rows are written in the background rather than before the call returns. Returns a request ID (requestId) for the queued job; the write outcome is not part of this response. Use this to load large batches of new rows. Use salesforcemarketingcloud_data_extension_row_async_upsert when rows may already exist and should be updated, and salesforcemarketingcloud_data_extension_row_insert for small writes that must complete immediately. Poll the returned request ID with salesforcemarketingcloud_data_extension_row_async_status, then read per-row outcomes with salesforcemarketingcloud_data_extension_row_async_results_get. Prefer the upsert tool when rows with the same primary key may already exist. Requires the data_extensions_write scope (polling the status and results needs data_extensions_read) and the external key of an existing Data Extension.

Queue an asynchronous INSERT of rows into a Data Extension addressed by its ID instead of its external key; the rows are written in the background rather than before the call returns. Returns a request ID (requestId) for the queued job; the write outcome is not part of this response. Use this only when you hold the Data Extension's ID and not its external key. Prefer salesforcemarketingcloud_data_extension_row_async_insert, which addresses the Data Extension by external key. Use salesforcemarketingcloud_data_extension_row_async_upsert_by_id when rows may already exist and should be updated. Poll the returned request ID with salesforcemarketingcloud_data_extension_row_async_status, then read per-row outcomes with salesforcemarketingcloud_data_extension_row_async_results_get. Requires the data_extensions_write scope (polling the status and results needs data_extensions_read) and the ID of an existing Data Extension and the ID (GUID) of an existing Data Extension.

Queue an asynchronous job to insert or update (upsert) a large batch of rows into a Data Extension in Salesforce Marketing Cloud, looked up by the Data Extension's customer key (external key). Unlike the synchronous row insert/upsert tools, this is designed for large payloads and returns immediately with a requestId rather than waiting for the write to complete — poll the async row status tool with that requestId to check progress and results. Each row is a flat object of field name to value pairs, including the Data Extension's primary key field(s); rows whose primary key already exists are updated, others are inserted. Example key: Customer_Master_DE.

• Idempotent

Queue an asynchronous UPSERT of rows into a Data Extension addressed by its ID instead of its external key; rows whose primary key exists are updated, the others are inserted, and the work happens in the background. Returns a request ID (requestId) for the queued job; the write outcome is not part of this response. Use this only when you hold the Data Extension's ID and not its external key. Prefer salesforcemarketingcloud_data_extension_row_async_upsert, which addresses the Data Extension by external key. Use salesforcemarketingcloud_data_extension_row_async_insert_by_id for new rows only. Poll the returned request ID with salesforcemarketingcloud_data_extension_row_async_status, then read per-row outcomes with salesforcemarketingcloud_data_extension_row_async_results_get. Requires the data_extensions_write scope (polling the status and results needs data_extensions_read) and the ID of an existing Data Extension and the ID (GUID) of an existing Data Extension.

Atomically increment (or decrement, with a negative amount) a numeric column on a single Data Extension row in Salesforce Marketing Cloud, without a read-then-write round trip. Uses the Data Extension Rows (Synchronous) API's route PUT /hub/v1/dataevents/key:{externalKey}/rows/{primaryKey}:{primaryKeyValue}/column/{column}/increment, confirmed directly on Salesforce's live 'Data Extension Rows (Synchronous)' reference page (the 'Increment Column Value by Using a Data Extension External Key' operation). The row is identified by the Data Extension's external (customer) key plus the name and value of its primary key field; the column to modify is a separate path segment. This tool sends the increment amount in the request body as {"value": <amount>} - that specific body field name follows this route family's typical convention but could not be independently re-confirmed against the live doc content in this session (the page renders its endpoint details via client-side JavaScript that this tool's fetcher cannot execute), so smoke-test the body shape once against a sandbox Data Extension and adjust rest_api_info.body_json_mapping if Marketing Cloud rejects the 'value' key. This only works on a Data Extension with a simple (non-composite) primary key matching primary_key_field/primary_key_value; composite-key Data Extensions are not supported by this route. Example: external_key Customer_Master_DE, primary_key_field SubscriberKey, primary_key_value 12345, column LoginCount, increment_by 1.

Synchronously insert one or more new rows into a Data Extension in Salesforce Marketing Cloud using the Custom Object Data REST API, looked up by the Data Extension's customer key (external key). Each row is provided as an object with a 'keys' sub-object (the Data Extension's primary key field name(s) and value(s)) and a 'values' sub-object (every other field name and value to set). Best suited for small, immediate inserts (a handful to a few hundred rows); for large bulk loads, use the asynchronous row insert/upsert tool instead. Inserting a row whose primary key already exists typically fails — use the upsert tool if the row may already exist. Example key: Customer_Master_DE.

Synchronously insert or update (upsert) one or more rows in a Data Extension in Salesforce Marketing Cloud using the Custom Object Data REST API, looked up by the Data Extension's customer key (external key). Each row is provided as an object with a 'keys' sub-object (the Data Extension's primary key field name(s) and value(s)) and a 'values' sub-object (every other field name and value to set). If a row with the given key(s) already exists it is updated in place; otherwise a new row is created. Best suited for small, immediate upserts (a handful to a few hundred rows); for large bulk loads, use the asynchronous row insert/upsert tool instead. Example key: Customer_Master_DE.

• Idempotent

Update an existing Data Extension's schema in Salesforce Marketing Cloud using the Custom Object REST API (PATCH), looked up by its customer key (external key). Use this to rename the Data Extension, change its description or folder (category), update its sendable configuration (isSendable/sendableCustomObjectField/sendableSubscriberField), or add new fields / modify existing fields. To modify an existing field rather than create a new one, reference it by its exact current field name — adding a field object with a name that doesn't already exist creates a brand-new column instead. Fields cannot be removed via this endpoint. Only the properties you supply are changed; any property left blank keeps its current value. Example key: Customer_Master_DE.

• Idempotent

Queue an asynchronous bulk domain verification check in Salesforce Marketing Cloud, using POST /messaging/v1/domainverification/bulk/insert. Domain Verification is a new resource category for this connector. Supply a notification_email to be notified when the job completes, plus either an explicit addresses array of email addresses to check, or a Data Extension column reference (de_table + de_column) so Marketing Cloud pulls the addresses to check from an existing Data Extension column instead -- provide exactly one of addresses or the de_table/de_column pair, not both. The call returns immediately with HTTP 201 and an async requestId identifying the queued job; the job's outcome is delivered via the notification email rather than in this call's response.

Create a From Address Management record for a sender email address in Salesforce Marketing Cloud and trigger a verification email. Returns HTTP 201 with a plain confirmation string (documented example: 'test@test.com successfully added.') rather than a JSON object of record details. Use this to add a sender address record and start email-based verification. Use salesforcemarketingcloud_domain_verification_register instead for the DNS-based flow, which registers a root domain and returns a verification key to publish as a DNS TXT record, and salesforcemarketingcloud_domain_verification_list to review existing records. Prerequisites: requires the saved_content_read and email_write scopes.

Push one or more registered domains from an Enterprise (parent) account to all of its existing child business units, so that each child business unit receives every domain in the list. Returns a JSON array with one entry per submitted domain, each holding the domain and a result message such as 'Success' or 'Not an Enterprise Account'. Individual failures are reported inside a successful HTTP 200 response, so inspect every entry rather than relying on the status code. Use this to propagate domains already registered in the parent account across all child business units in one call. It has a cross-business-unit side effect and only makes sense from an Enterprise parent account. Use salesforcemarketingcloud_domain_verification_register to register a domain in the first place. Prerequisites: requires the saved_content_read and email_write scopes. The domains must already be registered, and the call must be made with an Enterprise (parent) account token.

Register a new sending domain for verification/authentication in Salesforce Marketing Cloud, using POST /messaging/v1/domainverification/register with body {"domain": "<domain>"}. Domain Verification is a new resource category for this connector, covering the DNS-based sender-domain authentication workflow that complements the existing seed list and address validation tools. On success, Marketing Cloud returns the registered domain along with a verification key/token (formatted like 'SFMC-a1b2c3d4e5f67890') that must be published as a DNS TXT record on that domain; once the DNS record is in place and has propagated, call the Verify Registered Domain tool with the same domain and key to complete verification. The domain is not usable for sending until verification succeeds.

Complete DNS-based verification for a sending domain previously registered with the Register Domain for Verification tool, using POST /messaging/v1/domainverification/verify. Domain Verification is a new resource category for this connector. Submit the domain name and the verification key/token that was returned at registration (formatted like 'SFMC-a1b2c3d4e5f67890'); Marketing Cloud checks DNS for a TXT record on that domain matching the key and, if found, marks the domain verified (updating its status and isSendable flag, visible via the List Domain Verification Records tool). Run this only after the TXT record has been published and has had time to propagate -- calling it too early, or with a key that doesn't match the domain, returns a failure rather than retrying automatically.

Send a transactional/triggered email using a pre-configured Email Studio triggered-send definition (a TriggeredSendDefinition built around an existing email asset), via the Marketing Cloud Messaging REST API. Requires the triggered send definition's identifier (its ObjectID GUID or its external/customer key), the recipient's email address, and a SubscriberKey that uniquely identifies the recipient in Marketing Cloud. Optionally pass contact_attributes for personalization (must match the fields the definition's data extension expects) and override the From address/name. Defaults to asynchronous processing; check delivery status separately via the Email Delivery Details endpoint.

Create an OAuth2 authentication scheme that the Event Notification Service (ENS) uses to obtain a bearer token from your own authorization server before pushing events to a callback, using either the client_credentials or the password grant. Returns an array with one object holding the generated authId, authType, grantType and authUrl (plus scope when you supply one); the client id, client secret, username and password are never echoed back. Use it before an ENS callback that must authenticate; keep the returned authId, because the update tool needs it. Use salesforcemarketingcloud_event_notification_authentication_update to change an existing scheme. salesforcemarketingcloud_event_notification_callback_create does not currently expose an authId input, so this tool does not attach the scheme to a callback. Prerequisites: your authorization server's token URL must be public HTTPS and already return a token for the credentials you supply. The Marketing Cloud permissions table lists no scope for this route; it is documented only in the ENS OAuth2 guide.

Update an existing Event Notification Service (ENS) OAuth2 authentication scheme, identified by its authId, with a new grant type, credentials and token URL. Returns an array with one object holding the updated authId, authType, grantType and authUrl; the client id, client secret, username and password are never echoed back. Callbacks that use the scheme can take a few minutes to pick up the change. Use it to rotate a client secret or password or to point ENS at a new token URL. Use salesforcemarketingcloud_event_notification_authentication_create to make a new scheme instead. Prerequisites: the authId returned when the scheme was created, because no list or get route is documented for authentication schemes. Re-send the full credential set for the grant type, since partial updates are not documented, and make sure the token URL already returns a token. The documented update payload has no scope field, and the Marketing Cloud permissions table lists no scope for this route.

• Idempotent

Register a new callback (webhook) URL with Salesforce Marketing Cloud's Event Notification Service (ENS), using POST /platform/v1/ens-callbacks. Your endpoint must already be online and reachable: as soon as you create the callback, ENS immediately posts verification details to it and expects an HTTP 200 OK response within 30 seconds, or the request fails with 400 Bad Request. Once created and verified, the callback's ID can be used to create subscriptions (see Create Event Notification Subscription) that route specific event types to this URL. The response includes a generated callback_id and a signature_key used to verify the authenticity of incoming webhook payloads.

Regenerate the signature key for a registered Event Notification Service (ENS) callback in Salesforce Marketing Cloud, using PUT /platform/v1/ens-regenerate. The callback's previous signature key is immediately deactivated, so any webhook receiver validating incoming payloads must be updated with the new key before this is called, or signature verification will start failing. Confirmed via the official Salesforce documentation page for Regenerate Signature Key: the response includes the callback's name, ID, HTTPS URL, and the newly generated signature key.

Update an existing registered Event Notification Service (ENS) callback in Salesforce Marketing Cloud, using PUT /platform/v1/ens-callbacks. Like ENS subscriptions, callbacks are updated by PUTting an array containing the full replacement callback object to the collection endpoint (there is no /{id} path variant for update) -- identify which callback to update via callback_id, and supply the callback's full name again even if it isn't changing. You can also adjust the maximum batch size used when posting notification batches to this callback's URL. Confirmed via the official Salesforce documentation page for Update Callback; the API returns 200, 201, or 304 depending on whether the update was applied.

• Idempotent

Manually complete two-step verification of an Event Notification Service (ENS) callback in Salesforce Marketing Cloud, using POST /platform/v1/ens-verify (confirmed via Salesforce's official 'Verify Callback' reference page). When a callback is created (Create Event Notification Callback), ENS immediately issues an HTTPS POST to its URL carrying a callback ID and a unique, single-use verification key, and normally expects that callback's own webhook receiver to echo the verification key straight back within 4 hours to auto-complete verification. If the receiver can't respond programmatically -- e.g. it's a manual endpoint, or the payload was captured out-of-band -- use this tool to submit the same callback_id and verification_key yourself and complete verification manually. Returns HTTP 200 on success. Verification must be completed within 4 hours of the callback's creation or it expires and the callback registration fails.

Subscribe a previously registered and verified callback to one or more Event Notification Service (ENS) event types in Salesforce Marketing Cloud, using POST /platform/v1/ens-subscriptions. A subscription determines which event categories (e.g. TransactionalSendEvents.EmailSent) are delivered to a given callback URL, and can optionally be scoped further with filter criteria such as a specific definitionKey. The callback referenced by callback_id must already exist and be verified (see Create Event Notification Callback). You can create up to 200 subscriptions per callback, and a new subscription can take up to two minutes to become active.

Update an existing Event Notification Service (ENS) subscription in Salesforce Marketing Cloud, using PUT /platform/v1/ens-subscriptions. Unlike most REST resources, ENS subscriptions are updated by PUTting an array containing the full replacement subscription object to the collection endpoint (there is no /{id} path variant for update) — identify which subscription to update via subscription_id inside the request body. Use this to change the subscribed event_category_types, adjust scoping filters, rename the subscription, or pause/resume it. To pause an active subscription set status to 'paused', and to resume a paused subscription set status to 'active'; a status_reason should be supplied whenever status is changed. A new subscription can take up to two minutes to become fully active after an update.

• Idempotent

Create an Automation Studio File Transfer activity that moves, unzips or decrypts a file between Marketing Cloud Safehouse and a file transfer location. Returns the API's response for the created activity, which is expected to include its id (GUID); the exact response shape is not confirmed. Use this to define a new transfer step. It only defines the activity and does not run it: call salesforcemarketingcloud_file_transfer_activity_start to run it once, or add it to an automation with salesforcemarketingcloud_automation_create. Which fields are mandatory is not confirmed in Salesforce's reference; in practice supply at least a name, a customer key, a file spec and a file transfer location id, plus is_upload=true when pushing a file out or is_compressed=true on an unzip step. Use salesforcemarketingcloud_file_transfer_location_list to find a location id. Requires the automations_read and automations_write scopes and an existing file transfer location whose GUID you pass as the location id.

Queue an Automation Studio File Transfer activity to run one time, on demand. Returns the API's acknowledgement that the run was queued; comparable start routes return the plain text OK, and the exact response for this route could not be confirmed. The run is asynchronous, so a success response means the run was queued, not that the file has finished transferring. Use this to run a single transfer right away, for example after creating the activity with salesforcemarketingcloud_file_transfer_activity_create. To run a whole automation that contains the activity, use salesforcemarketingcloud_automation_start instead. Not idempotent: every call queues another run. Requires the automations_read and automations_execute scopes and the activity's GUID id from salesforcemarketingcloud_file_transfer_activity_list or salesforcemarketingcloud_file_transfer_activity_create.

Create a new external file transfer location in Salesforce Marketing Cloud, using POST /automation/v1/filelocations. A file transfer location is a saved connection profile (FTP, SFTP, Enhanced FTP, or similar external server) that Automation Studio's File Transfer, Import, and Data Extract activities reference to move files in or out of Marketing Cloud, instead of embedding raw server credentials in every activity. Username and password are required for password-authenticated FTP/SFTP/Enhanced FTP servers; some connection types (e.g. key-based SFTP, or internal Enhanced FTP/Safehouse storage) may not need them. NOTE: the exact set of fields accepted by this endpoint could not be independently verified against live API documentation at authoring time (the Salesforce docs page for this resource is a JavaScript-rendered reference that could not be fetched) — field names are a best-effort reconstruction from the Marketing Cloud 'File Locations' setup screen and should be validated in testing.

Update an existing external file transfer location in Salesforce Marketing Cloud, using PATCH /automation/v1/filelocations/{id}. Only the fields you supply are changed; leave a field blank to keep its current value. Use this to rotate credentials, change the host/port/directory, or rename a location referenced by Automation Studio's File Transfer, Import, and Data Extract activities. NOTE: the exact set of fields accepted by this endpoint could not be independently verified against live API documentation at authoring time (the Salesforce docs page for this resource is a JavaScript-rendered reference that could not be fetched) — field names are a best-effort reconstruction from the Marketing Cloud 'File Locations' setup screen and should be validated in testing.

• Idempotent

Remove a single contact from a running journey (or from specific versions of it), using the Interaction REST API's contact-exit endpoint (POST /interaction/v1/interactions/contactexit). Identify the contact by contact_key and the journey by its external definition_key (the customer key shared across all versions of the journey, not its GUID). Optionally restrict the exit to specific version numbers via versions; if omitted, the contact exits from every version they are currently in. The request is processed asynchronously (HTTP 202 Accepted); use the corresponding 'get exit status' endpoint to confirm completion. The underlying API also supports removing up to 50 contacts in a single call, but this tool submits one contact per invocation for predictable results.

Asynchronously insert a batch of up to 100 contacts into a Journey Builder journey using the Batch Event API. Supply the eventDefinitionKey (the API Event entry source key configured on the journey, found in Journey Builder's Entry Source > API Event details panel — not the journey's own key) and an array of members, each identified by a contactKey and optional personalization data. The request is queued and processed asynchronously; the response returns a requestId used to poll the status endpoint, plus a count of contacts accepted and any per-contact errors. Corrected endpoint: POST /interaction/v1/async/events (the older synchronous single-contact endpoint is /interaction/v1/events; a distinct experimental bulk endpoint also exists but is unsupported).

Create (insert) a new journey definition in Salesforce Marketing Cloud Journey Builder using the Interaction REST API (POST /interaction/v1/interactions). Provide the journey's name and, optionally, its triggers (entry sources such as an API Event or Contact Data Entry), goals, and activities (the ordered sequence of steps such as emails, wait activities, and decision splits) as JSON arrays following the Journey Specification. Fields such as id, createdDate, modifiedDate, status, and definitionId are assigned by Journey Builder and must never be supplied. If no key is provided, Marketing Cloud generates one automatically. The journey is created in Draft status and must be published separately (see the Publish Journey tool) before it goes live.

Create an event definition in Salesforce Marketing Cloud Journey Builder (POST /interaction/v1/eventDefinitions). An event definition names and describes the schema of an event that can be used as a journey entry source (trigger) or waypoint, and is referenced by its eventDefinitionKey when firing events via the Fire Journey Event tool. Provide either a dataExtensionId (pointing at an existing data extension whose schema defines the event's data fields) or a schema object describing the fields directly — one of the two is required. The type field determines the kind of event; use Event (the generic/default type) for events fired programmatically via the REST API — Salesforce's docs do not define an 'APIEvent' type value despite the eventDefinitionKey naming convention (e.g. 'APIEvent-Welcome').

Update an existing event definition by ID in Salesforce Marketing Cloud Journey Builder (PUT /interaction/v1/eventDefinitions/{id}). Once an event definition is created, only a limited set of properties can be updated (name, description, icon, visibility, and its underlying data extension); its type and eventDefinitionKey cannot be changed. Only include the fields you want to change.

• Idempotent

Fire an event to enter a contact into any journeys in Salesforce Marketing Cloud that are listening for it (POST /interaction/v1/events). Provide the contact's ContactKey (typically the subscriber key or email address), the EventDefinitionKey of the event definition to fire (created via the Create Event Definition tool), and any additional data fields the event definition's schema requires. On success, returns an eventInstanceId. The contact must have an Active status, and the EventDefinitionKey must not contain periods.