Stop Coding from Scratch: Let AI Agents Handle Google Apps Script Integration and Development for You
Turning Waste into Treasure with AI — Using Claude Design & Claude Code to Build Your Personal Desktop Dashboard as an Example.
Finished Product Demo
Turn an iPhone 8 Plus that has been sitting unused in a drawer for years into a personal desktop Dashboard Deck, fully customized and completely free.
Introduction
TL;DR If you only care about how to use AI to build your personal desktop Dashboard, please skip this section.
I started using Google Apps Script around 2021 to develop small tools for automating and optimizing workflows. Back then, AI and RPA automation were rarely discussed. The goal was simply to improve team collaboration efficiency or enhance personal comfort. All scripts were hand-coded line by line (which now seems like an old-fashioned way of programming). But the hardest part wasn’t the coding itself; it was whether and how to integrate with other services, and how to think outside the box for integration.
Previous Projects
-
Goal — When the public-facing email inbox receives a message, forward it to the Slack work channel.
Technically, Google Apps Script does not have an event triggered when Gmail receives an email, so we use a different approach with a scheduled trigger running every minute (or longer): check unread emails ➡️ read content ➡️ strip HTML and forward to Slack ➡️ mark as read.
If you only want to target specific emails (by sender or subject), set up a Label Filter in Gmail, then change the check from unread emails to unread emails with that Label to achieve this.
ref: 「 Using Google Apps Script to Forward Gmail Messages to Slack 」 -
Goal — Automatically query GA traffic/Crash-free rate and send it to the Slack work channel.
Google Apps Script already has built-in AnalyticsData / AdSense Libraries. You just need to import and set the parameters to use them directly, making integration almost painless.
If the app wants to query crash issue details or the Top 10, you just need an extra step: Firebase to BigQuery, then import the BigQuery Library in Google Apps Script and run SQL queries to achieve this.
ref: 「 Crashlytics + Google Analytics Auto Query App Crash-Free Users Rate 」、「 Crashlytics + Big Query Build More Real-Time Convenient Crash Tracking Tool 」 -
Goal — Automatically consolidate operational data into Google Sheet.
Following the previous approach, a Web App was created so the entire operational data could be clearly displayed on the team’s TV wall; the technical issue at that time was that some data was internal, inaccessible from the external network. Fortunately, the solution was to switch to an internal scheduled task that sends data daily to the Google Apps Script Web App, which then processes and writes it back to Google Sheet.
ref:「 Using Google Apps Script to Automate Daily Data Reports with RPA 」 -
Goal — Build a Simple App Packaging Platform Using Existing Resources
The background was that the app packaging service moved to GitHub Actions, but non-engineering teams also needed app packaging, which was previously handled manually. A service was needed within the company team to connect to GitHub Actions for packaging.
Using Google Apps Script Web App as the platform, access was restricted to organization accounts only. Users filled in packaging info on a form, which triggered GitHub Actions (via GitHub API) and sent packaging notifications to Slack.
The packaged app was uploaded to Firebase App Distribution. However, Google Apps Script has no built-in library, but after some research, it can be done directly with googleapis, and it was smoothly integrated in the end.
ref: “Using Google Apps Script Web App to Connect GitHub Actions and Build a Free, Easy Packaging Tool Platform”
There are also some smaller cases not listed here. In short, the point is “there are always more solutions than problems.” Actually writing the code is the easiest part; the real challenge is overcoming various obstacles to integrate everything together.
Technical Limitations
The premise of “there are more solutions than difficulties” is that it must be technically feasible and reasonable; in other words, “if the direction is wrong, effort is in vain.” We may not need to actually write code, but we must know when to “choose” to use Google Apps Script to develop small tools.
-
User-Agent Cannot Be Customized: For security and abuse prevention reasons, Google Apps Script User-Agent cannot be specified by the user. (However, other header fields can be set.)
Impact: Some rare APIs require data in the User-Agent, or target websites/APIs block the Google Apps Script User-Agent. Both cases are hard limits and cannot be bypassed.
Workaround: If you really need to use it, you can proxy through a Cloudflare Worker. -
Maximum Execution Time 6 Minutes: Each run can last up to 6 minutes. For large or numerous tasks, it is recommended to split them into segments.
Additionally, there is a total quota limit, such as Triggers running up to 90 minutes per day. (However, this seems to be a soft limit; many of my scripts exceed this limit without being blocked.) -
Single execution mainly uses synchronous blocking: You cannot dispatch multiple threads to run tasks concurrently within a single execution; if tasks are time-consuming or require extensive parallel processing, it is recommended to split them into multiple executions and use scheduled triggers.
-
Cold Start: A common issue with Faas services is that when a task hasn’t been triggered for a long time, it goes to sleep, causing a longer wait time when triggered again.
This problem, combined with the requirement for synchronous (blocking) execution, means that if deployed as a Webhook for other services to call, it can easily be judged as a failed request, leading to repeated requests, repeated receptions, and repeated executions.
For example, Slack strictly requires the Webhook server to respond within 3 seconds, and this issue has often been encountered in past experience. -
Web App API will redirect: For security reasons, the Content service response will redirect to a one-time
script.googleusercontent.comURL; HTTP clients need to support following redirects.
Some webhook services will fail if they do not automatically follow 302 redirects (e.g., Jira Webhook). -
Web App HTML: The webpage header includes an anti-abuse notice. True RWD is not achievable (the page is actually an iframe inside Google’s framework). The URL is ugly and cannot be customized. Full-screen PWA pages are not possible.
- Service Limits: There are some usage limits for services, but under normal use, you usually won’t hit them. However, if you need high-frequency checks or real-time responses, it’s easy to reach those limits.
https://developers.google.com/apps-script/guides/services/quotas?hl=zh-tw
Advantages and Features
After understanding the limitations, let’s look at the advantages and features.
The biggest advantage is the seamless integration with Google’s native services. The Web App access can be set to the script owner, organization members, signed-in Google accounts, or anyone, without the need to handle complex OAuth flows yourself—just one click to set up, one click to complete, and one click to start running:
Built-in Services:
Can be used without referencing in GAS services.
-
DocumentApp → Google Docs
-
SpreadsheetApp → Google Sheets
-
SlidesApp → Google Slides
-
FormApp → Google Forms
-
GmailApp → Gmail
-
CalendarApp → Google Calendar
-
DriveApp → Google Drive
-
SitesApp → Google Sites
-
Maps → Maps / Distance / Routes
-
Translate → Translation
Advanced Services: Must be enabled in the GAS services to use.
-
Sheets API
-
Drive API
-
Calendar API
-
Gmail API
-
Analytics API / Analytics Data API
-
BigQuery API
-
Adsense API
-
YouTube Data API
-
Tasks API
-
Googleapis (Other/GCP)
Tools / System Services:
-
UrlFetchApp → Calling External APIs
-
PropertiesService → Key-Value Storage
-
CacheService → Cache
-
LockService → Concurrency Control Prevention
-
Utilities → Date / Hash / Base64
-
Logger → Log Output
-
HtmlService → Build Web UI, support Ajax asynchronous content updates
-
ContentService → Creating an API endpoint
-
Trigger → Scheduled Automatic Execution
Basically, everything needed for development is already available. In practice, you just need to connect and combine these services to achieve process automation, for example:
-
Automatically Query GA Traffic/Crash-free Rate and Send to Slack Work Channel:
Use Analytics Data API to fetch data, PropertiesService to store Slack Bot Token, and UrlFetchApp to call Slack Send Message API. -
Automatically aggregate operational data into Google Sheet and data Dashboard Web:
Trigger scheduled execution of functions, use LockService to ensure only I run it, fetch data with Analytics Data API, get external service data via UrlFetchApp, write to Google Sheet with SpreadsheetApp, output Web App interface using HtmlService, output JSON data with ContentService plus data caching via CacheService.
Differences from FAAS like Cloud Function / Lambda
Google Apps Script can be seen as a FAAS scripting tool centered around Google services. It has more limitations but is currently completely free and seamlessly integrates with Google services; other FAAS services usually require payment, though some offer free tiers, and integrating with Google services involves formal IAM or OAuth processes that are more complex and cumbersome.
Unsuitable Scenarios
-
Not part of the Google ecosystem, such as wanting to connect with Microsoft Office or OneNote…
-
Hybrid local and cloud setup is more suitable for n8n or AI Agent.
-
Complex calculations or large data processing may not complete within the 6-minute maximum execution time per run.
-
Large-scale web scraping or ticket-snatching programs are out of the question. Google Apps Script is easily blocked or stopped by Cloudflare’s anti-scraping measures.
Suitable Scenarios
For personal or team workflow integration, I have many scripts managing my daily routines. For example, I get daily notifications of zhgchg.li website traffic overview, GitHub Repo Issues, and even update the current stock prices in a Google Sheet. For teams, the app release process can integrate with Google Calendar to check events and trigger the corresponding CI/CD process (calling GitHub Actions), then send messages to the team Slack channel and forward app review failure emails to Slack.
The above is a human perspective review of my experiences developing Google Apps Script over the years. Next, I will share my recent experience using AI Agents to develop GAS from scratch — a personal desktop Dashboard Deck — along with practical examples.
Let AI Agent Handle Google Apps Script Integration and Development for You Directly
Recently, I started trying to develop Google Apps Script directly from scratch using AI, combined with the basic knowledge above (even without it, AI proficiency is very high); the completion and accuracy are almost 100%, marking the end of the era of “AI coding from zero.”
Practical — Turning Waste into Treasure with AI — Build Your Personal Desktop Dashboard Using Claude Design & Claude Code
Problem
I have an old iPhone 8 Plus (iOS 16.7) that I replaced and left unused in a drawer. I thought I could turn it into a desktop dashboard to display real-time information I want to see.
Infrastructure
To enable an AI Agent to help you develop Google Apps Script, we need to complete some basic infrastructure.
Even if you’re not developing with AI, it’s highly recommended to use Clasp when working on medium to large scripts. The Web Editor can sometimes crash or accidentally overwrite new code with old code when multiple tabs are open. Clasp makes writing and managing source code more convenient and secure.
Other use cases: Upload Google Apps Script projects to Git Repo for version control (excluding
.clasprc.jsonand.clasp.json), add CI to automatically run Jest JS unit tests, use Clasp Token for CD to pull the latest code, and use .claspignore to exclude files that should not be uploaded to the Google Apps Script project.
-
Node.js >= 20.0.0 ( If you haven’t installed the Node.js environment, please install it first )
-
npm i @google/clasp -g
-
Run
clasp loginto sign in and generate an authorization token ( choose the Google Apps Script corresponding account ) -
Save clasprc (Clasp Token) to Keychain to allow AI Agent secure access
security add-generic-password \
-U \
-s "com.google.clasp" \
-a "$USER" \
-w "$(cat ~/.clasprc.json)"
If you want to copy the Clasp Token to put into CI/CD Secrets for running tasks, you can use cat ~/.clasprc.json \\| base64 \\| pbcopy (remember to add base64 encode). When using it, run echo "$CLASPRC" \\| base64 --decode > ~/.clasprc.json && chmod 600 ~/.clasprc.json.
- Create Project Directory
You must create a project directory and then enter it.
- Create a Google Apps Script Project in the directory (using clasp)
clasp create
Will directly use the folder name as the project name.
The current project is empty, containing only the appsscript.json configuration file.
My Design
If you want to save tokens, you can directly git clone my GAS Web App to reuse my design and the developed GAS code.
Designing Dashboard with Claude Design or Design Agent Skill
Method 1 — Claude Design
In the previous article “Jekyll Blog Custom Theme Design｜Quickly Create a Unique Style with Claude Design + Claude Code,” the same steps were introduced: adjust the design until satisfied, then export the Project and unzip it into the project’s ./Design directory.
Method 2 — Design Agent Skill
Use a third-party Design Skill to complete the design. My prompt is roughly as follows:
/huashu-design
Design a web dashboard that can be viewed in landscape mode on an iPhone 8 Plus, and save the design results in the ./Design directory
- It will be deployed later as a Google Apps Script Web App
- The top area fixedly displays the date, weekday, and a flipping clock
- The bottom tabs switch periodically and show a timed progress bar
- The bottom tabs include:
-- Weather conditions
-- Calendar: current events or upcoming events of the day, showing remaining events
-- Countdown/Count-up days
I use Model: Opus 4.7 (1M context) / Effort: Medium
⏺ I first grasped the context: iPhone 8 Plus landscape = 736×414 CSS px, the content data structure (weather / calendar / countdown) is clearly defined in CLAUDE.md.
You haven't specified the style yet, so as your "design direction consultant," I'll give you 3 distinctly different style options. Please choose one (or mix and match, e.g., "font from A + colors from C"), then I'll create the full hi-fi design.
---
🅐 Option 1 · Massimo Vignelli Style Swiss Grid (Information Architecture)
▎ Vignelli’s grid aesthetics for NYC subway — Helvetica + strict columns + red, black, white. The information itself is decoration, no illustrations, icons, or gradients.
- Fonts: Neue Haas Grotesk / Inter Tight (display) + IBM Plex Mono (clock/numbers)
- Colors: pure white background #FAFAFA · pure black ink #0A0A0A · single vermilion accent #E63946 (used for progress bar and current tab)
- Layout: 12-column baseline grid, all elements aligned; flip clock with black background, white large text + thin horizontal separators; tabs are square color blocks
- Keywords: rational / restrained / print-like / information density / timeless
- Suitable for: you want a dashboard that won’t go out of style, like a high-quality newspaper front page
---
🅑 Option 2 · Dieter Rams × Braun Industrial Instruments (Minimalist Industrial)
▎ Rams’ aesthetics for Braun ET66 calculator and audio systems — light beige-gray background + rounded hardware panels + single orange accent +
▎ tactile physical buttons. Each section looks like an independent instrument panel.
- Fonts: Söhne / Inter (labels) + JetBrains Mono (clock styled as LCD seven-segment)
- Colors: warm beige-gray #E5E1DA · deep charcoal #2B2B2B · Braun orange #E85D2C accent · flip clock LCD yellow-green #A8B547 vintage LCD style
- Layout: each card has subtle inner shadow and 1px hairline border for a recessed physical instrument feel; tab switching looks like button press
- Keywords: industrial design / tactile / 1970s Braun / calm / engineer aesthetics
- Suitable for: you like hardware feel and want comfort for long viewing
---
🅒 Option 3 · Teenage Engineering OP-1 / Terminal (Sporty Poetics)
▎ TE’s OP-1 synth panel and vintage OLED terminal aesthetics — dark charcoal background + OLED teal glow + mono fonts + fine grid background. Flip clock is a large OLED
▎ flip display, progress bar resembles sequencer step lights.
- Fonts: JetBrains Mono / IBM Plex Mono (all) + Berkeley Mono (display large text)
- Colors: background #0E0F0D · main text #E8E5DA off-white · OLED teal #9DEF8F accent · warning orange #FFB454
- Layout: very faint 8px dot grid background; flip clock large text occupies 1/3 width with subtle scanlines; tab progress bar uses LED stepping; weather uses ASCII-style icons
- Keywords: OLED / cyberdeck / analog synth / hacker chic / hacker culture
- Suitable for: you want it to feel like a “device” on your desk, not just a “webpage”
---
Please tell me which one you choose (or which elements to mix), then I’ll proceed with the full hi-fi design into ./Design/. You can also say “none fit, show me more,” and I’ll suggest another style.
You can choose your preferred style or tell the AI the style you want, for example, “paper texture style, off-white rice paper + red seal stamp aesthetics.”
Waiting for AI to complete the design… AI might use Playwright to take a screenshot for verification after finishing. If you want to save tokens and verify the result yourself, you can add that instruction to the prompt.
Click the .html file directly in the directory to view the design result:
Adjust until satisfied before moving on to the next development step.
Create the Countdown Data Source Google Sheet:
Finally, create a countdown data source Google Sheet. In the future, just add data to this Sheet when needed.
title,date,repeat
Birthday,1994-07-18,yes
Japan Trip,2026-12-12,
repeat=yes: Annual recurring event
Note the Sheet Id: the red-highlighted part in the URL above / Gid: 0 (the first Sheet).
Register for the Central Weather Bureau API Key:
-
Register/Login: https://opendata.cwa.gov.tw/userLogin
-
Obtain Authorization Code
Developing and Implementing the Dashboard with Claude Code
First, Init Claude Code Memory Markdown:
/init
⏺ Created CLAUDE.md, focusing on the current state of this repo:
- Project stage: Early GAS project, currently only has appsscript.json / .clasp.json / Design/Paper Dashboard.html, no .gs code yet.
- File purpose: manifest settings (V8, America/New_York, Stackdriver), clasp-bound scriptId, and a React+CDN visual prototype (without google.script.run).
- Common commands: mainly clasp (push / pull / open / logs / deploy), no lint or test runner yet.
- Notes before push: skipSubdirectories: false will upload Design/Paper Dashboard.html; manifest lacks oauthScopes declaration; timezone setting location.
- Scope: Strictly use only this repo’s content, no reference to other projects (following your memory rules)
Execute the plan and schedule development tasks:
/plan
Implement the Dashboard web page features and design from ./Design, deploy to Google Apps Script Web App.
- Use the Central Weather Bureau API from the Ministry of Transportation and Communications for weather https://opendata.cwa.gov.tw/api/v1/rest/datastore/F-C0032-00
- Display the weather for Taipei City, show all available fields
- During development, you can generate a Token yourself and deploy the Web App to trigger necessary methods and test; be sure to remove this open access after development is complete
- Deploy the Web App so everyone can access it, but protect it with a custom Token; first-time users can enter the Token or pass it via URL
- Default calendar to read: primary
- Countdown days read from the Google Sheet I gave you, with title, date, repeat; if repeat is yes, it means an annual recurring countdown, also show how many years and months have passed (rounded down)
- API Key, Google Sheet ID/GID, etc. all stored in PropertiesService settings
- Use clasp push & deploy for me, clasprc login token stored in keychain security add-generic-password \ -U \ -s "com.google.clasp" \ -a "$USER"
- If manual steps are needed from me, please tell me each step in Traditional Chinese
- "oauthScopes": [ "https://www.googleapis.com/auth/script.external_request", "https://www.googleapis.com/auth/calendar", "https://www.googleapis.com/auth/spreadsheets", "https://www.googleapis.com/auth/script.scriptapp" ]
- Double-check if the google.script.run integration call format is correct
- The live GAS Web App HTML is rendered inside an iframe wrapper.
- Files like ./Design that do not need to be uploaded to Google Apps Script should be added to .claspignore
-
Web Apps have four access levels: anyone, only yourself, only signed-in users, and signed-in users within the organization.
-
The design in the above example is simple: everyone can access it but must enter the correct random Token to view the data. The weather can be changed to your own location, and multiple locations are also supported.
-
The calendar defaults to handling only the primary calendar. If you have other calendars, you can get the Calendar ID from Calendar Settings and Sharing -> Integrate calendar -> Calendar ID.
-
Added a lazy development section here, directly asking AI to deploy and test the Web App entry so it can develop, test, and fix simultaneously, then notify me when it’s done
If there are any issues with the plan, ask the AI; if not, you can start implementation!
Making coffee while waiting for AI development…
AI Agent Question:
Action needed from you (one-time):
1. Open the editor: https://script.google.com/d/1KEWgIql-gqTNI_Tv_w2-5t7VE_R0eBtjAtd3iqLqabYLOnzJZ8Ga8N4s/edit
2. Top-right "Deploy" → "Manage deployments"
3. Delete both existing deployments (the bare @HEAD and dev v1 — the pencil-icon edit doesn't let you change access type)
4. Then "New deployment" → Type: Web app → Execute as: Me (your account) → Who has access: Anyone → Deploy
5. Grant OAuth on the consent screen (calendar.readonly, spreadsheets.readonly, external_request)
6. Copy the new web app URL (looks like https://script.google.com/macros/s/AKfycb.../exec) and paste it here
Also paste:
- CWA API Key (Central Weather Bureau Open Data Authorization)
- Countdown Sheet ID (the long part in the Sheet URL between /d/ and /edit)
- Sheet GID (the number after gid= in the URL — defaults to 0 for the first tab)
Once I have the URL + secrets, I'll seed Properties via the dev endpoint, mint the access token, verify each handler, and wire you in.
(1.) The first run still requires our authorization; afterward, the AI Agent can run on its own. Go to the Script Editor URL:
Randomly select a file with functions, then choose a function to debug:
- Authorization is only required during the first run or when new permissions are added
If AI keeps saying there is a permission issue, but no authorization window appears during execution, you can first go to the project settings and check “Show ‘appsscript.json’ manifest file in the editor.” Then return to the editor, edit
appsscript.json, change the oauthScopes content, run once, and then change it back and run again. This should trigger the authorization process.
Only 1. needs to be handled by yourself; others can be done by AI:
1. OK, please deploy it for me directly
CWA API Key: CWA-XXXX-XXXX-XXXX-XXXX-XXXX
Countdown Sheet ID: XXXX / GID: 0
Assist AI in Setting Up Google Apps Script..
⏺ Scope is updated and pushed but the deployer's OAuth grant needs to be re-authorized for the new scope. The web app runs under your account — newly added
scopes require you to re-grant.
Please do this once:
1. Open the editor: https://script.google.com/d/1KEWgIql-gqTNI_Tv_w2-5t7VE_R0eBtjAtd3iqLqabYLOnzJZ8Ga8N4s/edit
2. From the function dropdown at the top, pick setupConfig (or any function)
3. Click Run — Google will pop an "Authorization required" dialog
4. Allow → grants the upgraded auth/spreadsheets scope
5. Tell me when done and I'll re-test the countdown handler
Although we have agreed with the AI, it may still get stuck in some places and need manual help, such as the message above; we just simply follow its steps to click and run the function once, then tell it OK, just like helping out. (If the method it mentioned doesn’t appear, just refresh the page)
AI Development Complete, Acceptance!
If any issues are found, you can ask the AI to fix them again.
Build Your Personal Desktop Dashboard with AI — Results
Desktop Version
iPhone Mobile Version
GAS Web App cannot achieve full-screen PWA with hidden address bar. For a 100% experience, please refer to the advanced content.
Final Code
Follow-up Tasks
-
[required] Tell the AI: Remove all development-stage interfaces/endpoints after development is complete
-
[optional] Google Apps Script Project -> Project Settings -> Script Properties ->
ACCESS_TOKEN-> regenerate a random string, and replace the?token=in the URL with this string
On macOS, you can generate a random string with this command:openssl rand -hex 32 -
[optional] Regenerate the Central Weather Bureau API Key and enter it into Google Apps Script Project -> Project Settings -> Script Properties ->
CWA_API_KEY
⚠️ According to Claude Code warning: All tokens exposed in the conversation content may be leaked and should be considered compromised. For development convenience, tokens are entered directly first. After verification, they need to be regenerated and replaced.
If you are familiar with GAS, you can also set up the script properties yourself at the beginning and then instruct the AI to use them directly.
Extension
If this article sparks your creativity, consider integrating other data sources to display, such as connecting to Yahoo Finance to get real-time stock prices of your watched stocks, or linking AnalyticsData / AdSense to monitor your website traffic and ad performance.
Advanced
Because GAS Web App cannot achieve true RWD or full-screen PWA (hiding the address bar), I use the GAS Web App as an API service that only returns JSON data, and implement the frontend separately with GitHub Pages, deploying it as an official website; this way, a complete user experience can be achieved.
iOS Full-Screen PWA Web Setup -> Open URL in Safari -> Share -> Add to Home Screen
This approach is a bit more complex. You can tell the AI during the /plan stage:
- GAS Web App only serves as the backend, outputting JSON for frontend use
- Frontend uses GitHub Pages for design, presentation, and deployment, handling all development and deployment tasks
- A custom random string token protects communication between frontend and backend
Summary
This concludes the introduction to using AI Agents directly for Google Apps Script development. Recently, I have also been using AI to refactor medium to large GAS projects I developed before, with great results. I can even ask it to add function unit tests locally (using Jest, MOCK Google APIs) to improve stability (running on CI/CD, combined with clasp pull & backup GAS Project); the AI’s mastery and accuracy in producing GAS code are nearly 100%.
If it were 2021…
If it were the pre-AI era, manually handling everything from design, slicing, programming logic development to deployment would take me about 30 hours; now with AI, it can be done within 3 hours.
Basically, I probably won’t develop GAS from scratch anymore, nor write AI code from zero. Instead, I’ll have AI build the complete product for me from the start (code? IDGAF).
Case (2) — Personal Stock Portfolio Management
Another recent AI case I tried was directly handling Google Apps Script. I asked it to convert my Google Sheet stock portfolio into a visual Web App, integrating Yahoo Finance to fetch the latest stock prices and display them in a table. Below the table, there’s a quick input area for buy/sell records, which then syncs back to the Google Sheet.
Further Reading
TL;DR These are all previously hand-coded GAS services and tools
-
Simple 3 Steps — Create a Free GA4 Automated Data Notification Bot
-
Slack Builds a Fully Automated WFH Employee Health Status Reporting System
-
Crashlytics + Big Query: Building a More Real-Time and Convenient Crash Tracking Tool
-
Crashlytics + Google Analytics Automatic Query for App Crash-Free Users Rate
-
Use Google Apps Script in 3 Steps to Create a Free GitHub Repo Star Notifier
-
10-Minute Quick Migration from Line Notify to Telegram Bot Notifications
Comments