Trigger Lingk Events through a Recipe

#   _____           _              _____        __      
#  |  __ \         (_)            |_   _|      / _|     
#  | |__) |___  ___ _ _ __   ___    | |  _ __ | |_ ___  
#  |  _  // _ \/ __| | '_ \ / _ \   | | | '_ \|  _/ _ \ 
#  | | \ \  __/ (__| | |_) |  __/  _| |_| | | | || (_) |
#  |_|  \_\___|\___|_| .__/ \___| |_____|_| |_|_| \___/ 
#                    | |                                
#                    |_|

# Project Name - TRIGGER LINGK EVENTS THROUGH A RECIPE

# Recipe URL - https://app.lingk.io/a/10932/tf/17814

# Description - # This recipe writes an event payload to a Lingk event (through the REST API) that can trigger other recipes or publish the data to webhooks for Zapier and other apps.
                # To use this recipe, create an object in the Lingk app under Events, subscribe it to a recipe or webhook, update the object name in the recipe, and click Run!

# Industry - Higher Ed
# Business Process - Graduate Reporting

# Systems - Lingk
# Connectors - Lingk
# Data Flows - Single Direction
# Connection Type - S3 Bucket to API

# Lingk Objects
#1. Events

# Add Recipe notes / Change log information here!

#    _____                            _                 
#   / ____|                          | |                
#  | |     ___  _ __  _ __   ___  ___| |_ ___  _ __ ___ 
#  | |    / _ \| '_ \| '_ \ / _ \/ __| __/ _ \| '__/ __|
#  | |___| (_) | | | | | | |  __/ (__| || (_) | |  \__ \
#   \_____\___/|_| |_|_| |_|\___|\___|\__\___/|_|  |___/
#

# CONNECTORS specify what data will be pulled into the in-memory database during processing

connectors:

# Configure Lingk credentials in your Environment before running this recipe
  # Lingk Setup - https://help.lingk.io/en/articles/88-lingk-rest-api-connector-reference

- 
    name: signalWriter
    type: lingkWriter
    properties: 
      apiEndpoint: https://www.lingkapis.com/v1/@self/events  
      # authentication automatically aligned with the workspace
      # can be overridden - see lingkWriter documentation for details

#    _____ _        _                            _       
#   / ____| |      | |                          | |      
#  | (___ | |_ __ _| |_ ___ _ __ ___   ___ _ __ | |_ ___ 
#   \___ \| __/ _` | __/ _ \ '_ ` _ \ / _ \ '_ \| __/ __|
#   ____) | || (_| | ||  __/ | | | | |  __/ | | | |_\__ \
#  |_____/ \__\__,_|\__\___|_| |_| |_|\___|_| |_|\__|___/

# STATEMENTS specify how the data should be processed while in memory

statements:

#******************************************************************** D I S C L A I M E R ***********************************************************************************************
#                                                                                                                                                                                       * 
# Note that in an effort to keep recipes optimized for DPH (Data Processing Hours), print statements should be commented out after development has concluded for a recipe.              *
# For more information on DPH optimization, please visit the following help article - https://help.lingk.io/en/articles/212-minimizing-data-processing-hours-on-the-lingk-platform      *
#                                                                                                                                                                                       * 
#******************************************************************** D I S C L A I M E R ***********************************************************************************************

# Note: verb can be anything and doesn't currently impact subscriptions

#Creates a struct with the following field names and values.
- statement: |
      (signal) => select 
              named_struct('verb', "create",
                          'objectType', "eduuni.flat-file-signals.invalidrecord",
                          'eventObject', struct("recordId","1")
                     ) as signalData
#- statement: print signal
- statement: (signal) => select signalData.* from signal  
#- statement: print signal

##### Start Insert #####
- statement: insert signal into signalWriter
##### End Insert #####

# Add more statements to convert, join, aggregrate, transform, and integrate your data