An inbound trigger integration is a process in which an external event or trigger initiates an action or workflow within a system or application. It’s a mechanism for automatically responding to incoming data, signals, or requests from external sources.
Key Components
- Inbound Trigger: The event or signal that initiates the integration. Examples include receiving an email, SMS, webhook, API call, sensor data, or user interaction on a website or application.
- Integration: The mechanism or technology used to connect different systems or applications. This allows for the exchange of data and the triggering of actions based on predefined rules or conditions.
- Action or Workflow: Once the inbound trigger is received, the integration system executes a predefined action or workflow. This could involve updating data in a database, sending a notification, triggering a business process, or other tasks in response to the trigger.
Current Inbound Trigger Integrations
- GitHub
- Circle CI
- Heroku
- Jenkins
- Travis CI
- Pagerduty
- AWS CodePipeline
- Jira
- Spinnaker.io
- Azure DevOps
Setting Up Inbound Trigger Integrations
The basic process of configuring an Inbound Trigger Integration is the same for all sources. The only the step that changes is when selecting the source.
- Navigate to Integration:
- Open the Team tab at the top of the page.
- Click on Integration where inbound triggers are available.
- Select [SOURCE]:
- Click on the Source you'd like to configure.
- Select the Orchestration from the dropdown list.
- Follow Instructions:
- Follow the further instructions available on the screen.