Connection Types Invoke and Trigger

Connection Types Invoke and Trigger

In Oracle Integration Cloud (OIC), the terms "trigger" and "invoke" refer to how integrations are initiated and how they interact with external systems. Here’s a clear comparison of the two:

Mnemonic means a special word used to help a person remember something

• Trigger = “How it starts”

• Invoke = “Who it talks to”

🔹 Trigger in OIC Definition:

A trigger is the entry point of an integration. It defines how an integration is started—usually by an event or incoming request from an external system or application.

Common Trigger Types:

• HTTP Trigger / REST Adapter – An HTTP request initiates the integration.

• SOAP Adapter – A SOAP request triggers the integration.

• Scheduled Trigger – Integration is triggered based on a time schedule (e.g., every hour).

• Event-based Triggers – For example, receiving a file, or a message on a queue.

Example Use Case:

A REST API call from an external system (like Salesforce) triggers an integration in OIC to process data and store it in Oracle ERP.

🔹 Invoke in OIC Definition:

An invoke is used to call an external system or service from within an integration flow. It's an outbound call to perform some action or retrieve data.

Common Invoke Examples:

• Calling a REST API of another system.

• Sending data to a database.

• Invoking a SOAP web service.

• Pushing data to Oracle SaaS or on-premise systems.

Example Use Case:

An integration fetches employee data from Oracle HCM using an HCM adapter invoke after being triggered by a scheduled job.

Feature	Trigger	Invoke
Purpose	Starts an integration	Calls an external system or service
Direction	Inbound (into OIC)	Outbound (from OIC to another system)
Adapter Type	Trigger-type Adapters	Invoke-type Adapters
Examples	REST trigger, File trigger, Schedule	REST invoke, SOAP invoke, DB invoke
When Used	At the start of an integration	Within an integration (after trigger)