This pipeline is named poap-extended-1. It pulls data from two subgraph_entity sources, does not perform any transformations, and stores the result into two separate PostgreSQL sinks.

cross-chain-pipeline.yaml
name: poap-extended-1
apiVersion: 3
sources:
  hashflow_cross_chain.pool_created:
    type: subgraph_entity
    name: pool_created
    subgraphs:
      - name: polymarket
        version: 1.0.0
      - name: hashflow
        version: 1.0.0
  hashflow_cross_chain.update_router_permissions:
    type: subgraph_entity
    name: update_router_permissions
    subgraphs:
      - name: polymarket
        version: 1.0.0
      - name: hashflow
        version: 1.0.0
transforms: {}
sinks:
  pool_created_sink:
    type: postgres
    from: hashflow_cross_chain.pool_created
    table: test_pool_created
    schema: public
    secret_name: API_POSTGRES_CREDENTIALS
  update_router_permissions_sink:
    type: postgres
    from: hashflow_cross_chain.update_router_permissions
    table: test_update_router_permissions
    schema: public
    secret_name: API_POSTGRES_CREDENTIALS

You can run the above example by copying the file into a local yaml file and running the following Goldsky CLI command:

goldsky pipeline apply <path_to_configuration> --status ACTIVE

Was this page helpful?

Sync subgraph to PostgresNative Transfers