1. Using the Rapid Adapter Builder with Oracle Integration 3
  2. Work with the Adapter Definition Document
  3. Update Trigger Definitions
  4. Learn About Trigger Definitions
  5. Introduction to Trigger Definitions
  6. What is a Trigger Contract

What is a Trigger Contract

A trigger receives a message in the form of an event from an external application or a service, and if required, allows the integration to respond.

A trigger consists of the following two contracts:

  • Raw inbound message

    The message is sent by an external application or a service using a HTTP post, and contains:

    • headers
    • query parameters
    • body

  • Trigger request

    The trigger request appears in the integration mapper.

The Rapid Adapter Builder platform supports design of both contracts and the ability to map one form into the other.

The structure of the inbound message and request contracts may or may not be the same. For example, a simple pass-through of the data may expose the headers and body to the integration developer which may not be a requirement. To hide the header from the integration designer, the adapter developer can choose to combine the fields and provide a virtual message from the webhook.