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
  • Main Toolbar
  • Filters
  • Column
  • Filter
  • SQL Filter
  • Comments
  • Tags
  • Find and Replace
  • Integration Configuration Wizard

Was this helpful?

  1. Reference

Integration Builder Page

PreviousHow to use the VaultNextIntegration Anatomy

Last updated 8 months ago

Was this helpful?

Main Toolbar

Buttons on the Integration Builder Toolbar enables users to add, duplicate and clear changes within the Builder. The special tool, deep clone creates a full copy of the entire Builder Row selected, and all of the children associated with it.


Filters

Column

The column filter handles the display status of the Build Page. By default, all columns are shown but each column can be toggled to be hidden.

Filter

The filter feature highlights matched Builder Rows based on the entered values. It will search in real-time and provide the number of results returned within the button.

SQL Filter

This performs the back-half of a SQL filter for the table. This allows users to search with higher specificity than the traditional text based filter.

Example Filters

FROM * SELECT

Comments

Comments are the main source of communication when jointly working within the Integration Builder. Comments can be created by anyone who has read-access to the integration.

Tags

Each section of the Integration Builder has the ability to add a tag to Builder rows. This provides a way to identify specific pieces of an integration and how they relate. It is particularly helpful when used in combination with Bookmarks.

Find and Replace

The Find and Replace toolbox offers a powerful way to quickly search for and update text within the cells on the build page. It will only search through visible cells.

  1. The text to find.

  2. The replacement text, if replacing.

  3. Number of matches, by cell. Multiple instances of the text in one cell counts as one.

  4. Move forward/backward through the matches. Enter and shift-Enter can also be used to move forward and backward respectively.

  5. Replace the currently highlighted instance

  6. Replace all found instances. If (11) Replace within Selection is enabled, will only replace the matches within the selected cells.

  7. When enabled, hides all rows that do not have a match.

  8. When enabled, looks for an exact case (case sensitive) match.

  9. When enabled, only counts whole words as matches (e.g. "banker" will not match "bank").

  10. When enabled, interprets the "find" text as a regular expression.

  11. When enabled, Replace All will only replace matches within the selected cells.


Integration Configuration Wizard

To create a new Integration, a wizard will take you through the required and optional configuration fields.

Step 1 — Configure Integration

  1. Name of the integration

  2. Description for the integration

  3. Whether services outside of Glyue can trigger the integration

  4. Whether the integration should run asynchronously

  5. Send a detailed breakdown of every integration run alongside the Email Success / Failure messages (if enabled).

  6. The list of emails to receive a notification when the integration finishes successfully.

    1. Multiple emails should be separated by a comma, e.g. david@sandboxbanking.com, sarah@sandboxbanking.com

  7. The list of emails to receive a notification when the integration fails.

    1. Multiple emails should be separated by a comma

    1. Note storing the payloads for those runs are controlled by a separate setting (9)

  8. Whether or not Glyue should store the contents of the payloads of every run of this integration, and if so, for how long.

    1. Payloads will not be stored if the general run history storage (8) is not enabled

    1. Integrations are developed against a specific Integration Engine version, so if unsure, consult Sandbox support before changing this setting.

Step 2 —Systems (adapters)

  1. Clears all changes on the page.

  2. Saves changes to adapter bindings. When setting up a new Integration, any Systems added will need to be saved before you can CONTINUE to the next step

  3. The system Glyue will be connecting to

  4. The configuration to use for the selected system

    1. If no configuration exists, you can create one using the Add New Adapter option. This will open a popup with fields specific to the system you selected.

    2. At a basic level, the adapter configuration contains the credentials for Glyue to communicate with the system.

  5. Adds additional systems, if the Integration requires multiple.

Step 3 — Permissions

Whether or not Glyue should , and if so, for how long.

, to preserve compatibility with platform functions as the platform evolves.

, which allow an Integration to be triggered by user-defined URL paths.

This page is used to set Read, Write, Execute, and Debug permissions for each user on the new integration. A description of each permission can be found at .

Integration engine version
Webservice endpoints
store the records of every run of this integration
First page of the Integration Configure Wizard – "Integration Config"
Second page of the Integration Configure Wizard – "Systems"
Third page of the Integration Configure Wizard – "Permissions"
Integration Permissions