For example, A Salesforce subscription might associate incoming data with an Event that updates internal variables and sends a text to notify the user of the update. This would appear in the Journey Builder as something like the following:
App API and Subscription Events provide the ability to perform asynchronous actions on specific Journeys associated input from external systems.
App APIs and Subscriptions are configured in the Connection Builder. App APIs are nested under the Web Links section, Subscriptions are nested under the Subscriptions sections. Integrations might need to first be configured in the Console or Configuration Builder before becoming available; see Connecting to External Systems for more details.
Once an App API or Subscription Event has been added, the associated Action Chain can be built out in the Journey Builder by examining the relevant Event and opening the Actions tab in the Inspector.
Data that is captured from the incoming API call or Subscription can be handed over to the Event. Information passed as input can be accessed within the associated Action Chain by referencing:
For example, if a variable designated
name is passed as input, then to access its value within the downstream Action Chain, you would need to call on:
Updated about 15 hours ago