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
  • Workflow Connections
  • Transformations
  • Python Transformations

Was this helpful?

  1. ETL

Workflows

PreviousData ConnectorsNextRun History

Last updated 1 month ago

Was this helpful?

A workflow is primary organization unit within Glyue ETL. A workflow comprises:

  • A source data connection

  • A destination data connection

  • A set of transformations

Workflow Connections

When configuring a workflow, you must select the specific record(s) being read from the source connection as well as the specific record(s) being written to / modified on the destination connection.

For example, in an SFTP --> HubSpot workflow, you must select the file on the SFTP server to read from, and the HubSpot object to write to.

Transformations

Workflows exist to perform transformations on data from the source system, then write that data into the destination system. A transformation consists of:

  • A source field

  • A destination field

  • A transformation type

  • If requirement, additional details on the transformation type

Records from the source system are transformed sequentially, and all transformations are applied to a given record. If a transformation encounters an error, Glyue ETL will note the error and continue with the remaining transformations and records.

Glyue ETL supports the following transformation types:

Transformation Type
Purpose
Parameters

One-to-One

Passes the value from the source directly, without modification

None

Boolean

Converts values into boolean (true/false) values recognized by the destination

A list of values that should evalute to true (all other values will evaluate to false )

Date

Specify the date formats.

The format the source date is in, and the desired output format for the date

Python

Custom logic and processing. Can combine values from multiple source columns.

Value Mapping

Maps from one set of predefined values to another.

The Value Mapping Set to be applied.

Python Transformations

A Python transformation can access any column(s) from a row. The record_value dictionary contains the row's values. Specific values can be accessed by name, e.g. record_value['my_column']

If your transformation spans more than one line or does not evaluate to a value, you must specify the value to be used by assigning to the retvalue variable. For example,

if record_value["count"] > 1:
   retvalue = record_value["product_name"] + "s"
else:
   retvalue = record_value["product_name"]

Python code to be executed. See for more details

Python Transformations
Selecting source and destination connections for a workflow
Example transformations