Omni CHannel element Integration

In Campaign Designer, Omni Channel elements use an integration with Kettle so that any actions, commands or processing that Kettle is capable of can be triggered by this element in the campaign flow.

The Omni Channel element is essentially a skinned File Output element for the most popular channels, including Twitter, Facebook and Salesforce. These are displayed to the user and recorded in Campaign History as the [ChannelType] column.

The Omni Channel element uses an integration with Kettle so that any actions, commands or processing that Kettle is capable of can be triggered by the Omni Channel element. The basic process is that the file portion of the Tactic creates a file in the FTPOutputStagingDirectory and the Campaign processor calls the pre-configured Kettle job to run against that file.

• Integrations between Campaign Manager and Kettle
  • External Integrations Pack
  • Terminology Used in Integrations
  • File Tactic Integration
  • Omni Tactic Integration
  • Omni Channel element integration
  • Profile Rule Export Tool Integration
  • Injecting a Custom Transformation Into an Output Tactic
  • Data Input and Integration Points
  • Creating a Kettle script
  • Using a Kettle Job in Campaign Manager
  • Example code