Would someone be able provide an example of what an AWS Cloudformation AWS::GLUE::WORKFLOW template would look like?

Here's an example of a workflow with one crawler and a job to be run after the crawler finishes.

It is defined through tagging the triggers with the WorkflowName.

I believe there can be only one SCHEDULED or ON_DEMAND trigger to start the workflow. All the other triggers in the workflow need to be CONDITIONAL on the jobs / crawlers. That's probably how CloudFormation knows how to build the DAG.

Also see how the workflow parameters are defined as a json in the DefaultRunProperties.

---
AWSTemplateFormatVersion: '2010-09-09'

Parameters:
  BaseBucket:
    Description: Bucket used by my workflow jobs
    Type: String

Resources:
  MyWorkflow:
    Type: AWS::Glue::Workflow
    Properties: 
      DefaultRunProperties:
        {
          "workflowParameter1": "Foo",
          "workflowParameter2": "Bar",
          "bucket": { "Fn::Sub": "${BaseBucket}" }
        }
      Description: Workflow for orchestrating my jobs
      Name: MyWorkflowName

  WorkflowCrawler:
    Type: AWS::Glue::Crawler
    Properties:
      Name: MyCrawler
      Role: MyCrawlerRole
      Description: A crawler to run as the first step in the workflow
      DatabaseName: MyDatabase
      Targets:
        S3Targets:
          - Path: !Sub "s3://${BaseBucket}/"

  WorkflowJob:
    Type: AWS::Glue::Job
    Properties:
      Description: Glue job to run after the crawler
      Name: MyWorkflowJob
      Role: MyJobRole
      Command:
        Name: pythonshell
        PythonVersion: 3
        ScriptLocation: !Sub "s3://${BaseBucket}/my_workflow_job_script.py"

  WorkflowStartTrigger:
    Type: AWS::Glue::Trigger
    Properties:
      Name: StartTrigger
      Type: ON_DEMAND
      Description: Trigger for starting the workflow
      Actions:
        - CrawlerName: !Ref WorkflowCrawler
      WorkflowName: !Ref MyWorkflow

  WorkflowJobTrigger:
    Type: AWS::Glue::Trigger
    Properties:
      Name: CrawlerSuccessfulTrigger
      Type: CONDITIONAL
      StartOnCreation: True
      Description: Trigger to start the glue job
      Actions:
        - JobName: !Ref WorkflowJob
      Predicate:
        Conditions:
          - LogicalOperator: EQUALS
            CrawlerName: !Ref WorkflowCrawler
            CrawlState: SUCCEEDED
      WorkflowName: !Ref MyWorkflow

Here is an example of a Glue workflow using triggers, crawlers and a job to convert JSON to Parquet:

JSONtoParquetWorkflow:
  Type: AWS::Glue::Workflow
  Properties: 
    Name: json-to-parquet-workflow
    Description: Workflow for orchestrating JSON to Parquet conversion
RawJSONCrawlerTrigger:
  Type: AWS::Glue::Trigger
  Properties:
    WorkflowName: !Ref JSONtoParquetWorkflow
    Name: raw-json-crawler-trigger
    Description: Start crawler for raw JSON data
    Type: ON_DEMAND
    Actions:
      - CrawlerName: !Ref RawJSONCrawler
JSONToParquetETLJobTrigger:
  Type: AWS::Glue::Trigger
  Properties:
    WorkflowName: !Ref JSONtoParquetWorkflow
    Name: json-to-parquet-etl-trigger
    Description: Start JSON to Parquet ETL job
    Type: CONDITIONAL
    StartOnCreation: True
    Predicate:
      Conditions:
        - LogicalOperator: EQUALS
          CrawlerName: !Ref RawJSONCrawler
          CrawlState: SUCCEEDED
    Actions:
      - JobName: !Ref JSONToParquetETLJob
RawParquetCrawlerTrigger:
  Type: AWS::Glue::Trigger
  Properties:
    WorkflowName: !Ref JSONtoParquetWorkflow
    Name: raw-parquet-crawler-trigger
    Description: Start crawler for raw Parquet data
    Type: CONDITIONAL
    StartOnCreation: True
    Predicate:
      Conditions:
        - LogicalOperator: EQUALS
          JobName: !Ref JSONToParquetETLJob
          State: SUCCEEDED
    Actions:
      - CrawlerName: !Ref RawParquetCrawler

There is no simple example to find, therefore I created an example AWS Glue Workflow: Getting started which is using AWS Cloudformation template. This example is very easy but explained with diagrams.