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
  • Development vs. Production Credentials
  • System-specific Connector Requirements

Was this helpful?

  1. ETL

Data Connectors

Glyue ETL uses Data Connectors to manage access to external systems, such as SFTP servers and CRMs like HubSpot and Creatio. The requirements for each data connector differs based on the specific system, but the basics are outlined further down on this page.

A data connector only manages access credentials and does not specify the exact records being accessed or modified. The exact records are instead specified on the workflow's configuration when the connector is selected. This allows the same connector to be used across multiple workflows — it can grant access to different files for different workflows from the same SFTP server, or write to different objects in a HubSpot instance, for example.

Some data connectors may be "source only" or "destination only".

Development vs. Production Credentials

A connector actually contains two sets of credentials — one for development purposes, and another for production uses. While Glyue ETL does not enforce what type of system you enter credentials for, it is strongly recommended that you adhere to best practices and only enter SDLC-appropriate credentials.

A data connector only requires that one set of credentials is populated. However, missing credentials for one system will disable certain features, detailed below:

  • Features that require Production credentials

    • Setting a schedule for a workflow

Scheduled workflows always run using production credentials.

  • Features that require Development credentials

    • Running a Draft workflow

System-specific Connector Requirements

SFTP Servers

Field
Meaning
Example

Hostname

The URL of the SFTP server

sftp.sandboxbanking.com

Port

The exposed port of the SFTP server. Defaults to 22

22

Username

The username of the account to be used to access the SFTP server

Varies

Authentication Method

How the account should authenticate with the SFTP server. Is either a password, or an authentication certificate.

Password or Private Key (Certificate)

Authentication Credentials

Depending on the authentication method, either the password or the certificate.

Varies

HubSpot

Glyue ETL's HubSpot connector leverages browser-based OAuth, meaning connection only requires logging into your HubSpot account from Glyue ETL.

The Date Format field specifies the date format sent to HubSpot, as HubSpot requires a consistent date format across all date values. In most cases, the default value is appropriate and does not need to be changed.

Oracle SQL

PreviousGlyue ETL OverviewNextWorkflows

Last updated 13 days ago

Was this helpful?