linein-automation

Active Puppeteer Sessions auto-refresh 3s

No active puppeteer sessions
Submit a mock job from the Test tab to see it here.

Recent jobs

CreatedStatusModule/ActionSessionProgressDuration
CreatedStatusModuleAction SessionProgressDurationJob ID
Session KeyDomainUpdated Last usedCookiesFailuresLock
Job —
Session —
Module/Action —
—
waiting…
Browser view
browser view pending
Log stream 

        

      


      

        Raw RTDB snapshot
        
—

      

    


    
    

      

        列出 linein-egg MongoDB 中所有 LIFF 與對應 Lineaccount，多選後批次登入
        developers.line.biz 並 PUT
        /api/v1/channel/{login_channel_id}/webAppConfiguration/callbackUrls。
        login_channel_id 從 liffid 前綴解析，同一 channel 會去重只打一次。
        每個 Lineaccount 會共用一個 Puppeteer session（Redis 鎖序列化），不同帳號依 Concurrency 並行。
      


      

        

          
          
          
        

        

          
          
          

            
            
            
            
          

          
—

        

      


      

        

          

            
            LIFF ID
            alias
            Login Channel ID
            provider
            Account
            pwd
            type
          

          
        

      


      

        Batch runs
        
      

      
      

        

          CreatedStatusConcurrencyProviders
          ChannelsSucceededFailedBatch ID
        

        
      

    


    
    

      

        Submits a mock job that exercises the full pipeline (session lock →
        Chrome launch → screenshots → Firestore/RTDB writes → webhook) without
        contacting LINE or any bank. Use this to validate plumbing or to
        trigger a controlled failure case.
      

      

        
        
        
        
        
        
        
        
        
        

          
          
        

      


      

        Quick presets:
        
        
        
        
        
      


      

        Bank Crawler — real run
        POST /api/crawler/crawl · talks to the real bank site
      

      

        Submits an actual bank crawl using the BaseCrawler + per-bank class in
        src/modules/bank-crawler/. Leave the credential fields at
        {default} (or blank) and the backend will inject values from
        secret/bank-credentials.json — no typing needed.
        Session cookies are cached in Firestore (bankcrawler:<bank>:<account>)
        and reused on next run unless you tick Fresh session.
        A ● next to a bank means defaults are
        configured for it; ● means you'll have to
        type credentials manually.