Glyue User Docs
  • What is Glyue?
  • Tutorials
    • Start Here
    • Building a Single-Step Integration
      • 1. Creating the Integration
      • 2. Calling the External System
      • 3. Running the Integration
      • 4. Crafting the Output
    • Building a Multi-System Integration
      • 1. Connecting to the Core
      • 2. Field Mapping
      • 3. Running the Integration
    • Building an Event-Driven Integration
      • 1. Setting up the Mock CRM
      • 2. Receiving Inbound Requests
      • 3. Triggering the Integration from the CRM
    • Building an Email Integration
      • 1. Create and Configure the Integration
      • 2. Input Validation
      • 3. Get Story IDs from Hacker News
      • 4. Get Story Content
      • 5. Sending the Email
      • 6. Wrapping Up
      • 7. Extra credit
        • extra_credit.json
    • Building a RESTful CRUD Web Service
      • 1. Integration Setup
      • 2. Vault Setup
      • 3. Create Web Service Endpoints
      • 4. Execute Web Service Endpoints with Vault Methods
      • 5. Vault Code Examples and Explanation
    • Building a Retrieval API against FIS CodeConnect
      • 1. Integration Setup
      • 2. Service Request Setup
      • 3. Field Mapping Setup
      • 4. Integration and Service Request Hook Setup
      • 5. Testing the Integration
      • 6. Common Errors
    • What is Pre-Mapping?
      • Before you start
      • Bookmarks
      • Source and Targets
      • Field Mapping Status
      • Field Mapping Comments
      • Summary
  • How-To Guides
    • How to Run an Integration from Glyue
    • How to Invite New Users
    • How to Create a Value Mapping Set
    • How to Build and Deploy a Custom Frontend
    • How to Migrate an Integration
    • How to Set Up Single Sign On (SSO)
      • Glyue Setup
      • JumpCloud Setup
      • Azure Setup
      • Okta Setup
      • Glyue SAML Config Reference
    • How to Install the Glyue App for Zoom Contact Center
    • How to use the Vault
  • Reference
    • Integration Builder Page
    • Integration Anatomy
    • Integration Components
      • Integration
      • Service Request
      • Field Mapping
      • Value Mapping Set
      • Value Mapping
      • Validation Rule
      • Mask
      • Integration Config
      • Integration Engine Versions
    • Integration Lifecycle
    • Special Functions
      • add_run_label
      • callint
      • debug
      • end
      • get_namespace
      • humanize
      • import_helper
      • keep
      • list_files
      • map_value
      • open_glyuefile
      • open_vault
      • Data Manipulation Utilities
      • calladapter
    • Special Variables
      • __adapter_config__
      • input
      • parentint
      • retvalue
      • run_history_id
      • Iterables
        • fitem/fidx
        • sritem/sridx
        • vritem/vridx/vrmsg
    • Adapters
      • Generic HTTP Adapter
      • Email SMTP Adapter
    • Web Service Endpoints
    • Vault Reference
  • Glyue Platform Reference
    • Banking Core Connectivity Guide
    • Authentication
    • Permissions
      • Service Accounts
      • Organizations
    • Frontends
    • Idempotency Layer
    • Integration Scheduler
    • Governance Reports
    • Arbitrary Integration Request Content Support
    • Admin Components
    • Logging
  • ETL
    • Glyue ETL Overview
    • Data Connectors
    • Workflows
    • Run History
    • Scheduler
Powered by GitBook
On this page
  • integration
  • email_on_success
  • email_on_success_to_addresses
  • email_on_failure
  • email_on_failure_to_addresses
  • email_digests
  • store_run_history
  • store_run_history_for_x_days
  • store_payload_in_run_history
  • store_payloads_in_run_history_for_x_days
  • engine_version

Was this helpful?

  1. Reference
  2. Integration Components

Integration Config

integration

relationship - required

Integration the config is bound to.

email_on_success

boolean - required

Determine wheter to send an email summary upon a successful integration run.

email_on_success_to_addresses

string - comma separated

Email addresses to receive summaries on successful integration completion.

email_on_failure

boolean - required

Determine wheter to send an email summary upon an integration failure.

email_on_failure_to_addresses

string - comma separated

Email addresses to receive summaries on integration failures.

email_digests

boolean - required

Enables a more detailed breakdown of the Integration Run for both the email_on_success and email_on_failure features.

store_run_history

boolean - required

Enables persistence of run histories for integrations. With this flag disabled the Integration Run History will not track run events.

store_run_history_for_x_days

integer

Number of days to keep Run Histories. After this date the runs are deleted permanently. Defaults to 730 days.

store_payload_in_run_history

boolean - required

Enables persistence of run history payloads for Integration Run Steps. The store_run_history must be enabled for this to be enabled.

store_payloads_in_run_history_for_x_days

integer

Number of days to persist Integration Run History Items. After this date run history payloads are deleted permanently. Defaults to 14 days.

engine_version

Engine version used when running this integration.

engine_version = "1.1.0"
PreviousMaskNextIntegration Engine Versions

Last updated 3 months ago

Was this helpful?