Search

Inbound Trigger Integrations

An inbound trigger integration allows an external event to initiate an action or workflow within Functionize. This mechanism ensures that Functionize can automatically respond to incoming data, requests, or events from external sources—removing the need for manual intervention and enabling seamless CI/CD and DevOps workflows.

Key Components

  1. Inbound Trigger
    • The external signal or event that starts the process.
    • Examples:
      • Webhook call
      • API request
      • GitHub commit
      • Jenkins job completion
      • PagerDuty alert
      • Email or SMS receipt
  2. Integration
    • The connection that links Functionize with the external source.
    • Ensures data exchange and allows actions to be triggered based on predefined conditions.
  3. Action or Workflow
    • The process Functionize executes when the trigger is received.
    • Examples:
      • Run an orchestration
      • Update test data
      • Send notifications
      • Trigger dependent workflows

Supported Inbound Trigger Sources

Functionize currently supports inbound trigger integrations with:

  • GitHub
  • CircleCI
  • Heroku
  • Jenkins
  • Travis CI
  • PagerDuty
  • AWS CodePipeline
  • Jira
  • Spinnaker.io
  • Azure DevOps

Setting Up an Inbound Trigger Integration

The configuration process is similar across all supported sources. The only step that differs is the source selection.

Step 1: Navigate to Integrations

  • Log in to Functionize.
  • Open the Team tab (top navigation).
  • Click Integrations.

Step 2: Select the Source

  • From the list of inbound trigger sources, select the one you want to configure (e.g., GitHub, Jenkins, Jira).

Step 3: Map to an Orchestration

  • From the dropdown, select the orchestration you want to trigger when the inbound event occurs.

Step 4: Follow On-Screen Instructions

  • Each integration may have unique authentication or setup requirements (e.g., API tokens, webhooks, project selection).
  • Complete the setup as directed.

Example Use Cases

  • CI/CD Pipeline Integration – Trigger a Functionize orchestration automatically when a Jenkins job or CircleCI build completes.
  • Version Control Events – Run regression tests automatically when a GitHub commit or pull request is merged.
  • Release Management – Automatically validate critical workflows when a deployment is promoted to an environment in tools like Spinnaker.io.
  • Incident Response – Trigger a smoke test orchestration when PagerDuty raises a production alert.
  • Agile Workflow – Run relevant test suites when a Jira issue transitions to a specific state (e.g., “Ready for Testing”).

Best Practice: Always link inbound triggers to orchestrations that are scoped and stable (e.g., smoke tests, release validation suites). This ensures that automatic executions provide fast, actionable feedback without overloading the system with unnecessary test runs.