Generate daily timesheets from Gmail, Calendar and GitHub with AI

See What's Earning in AI Automation Freelancing.
DigiNo helps new AI automation freelancers earn faster by tracking what clients actually pay for.

Freelance developers and consultants lose real money every time they reconstruct a workday from memory. This AI automation pulls activity from email, meetings, and code commits and writes a finished timesheet into Google Sheets before the client asks for it.

What This Automation Does

Scans Gmail each evening and logs only substantive client emails, filtering out newsletters and automated no-reply messages automatically
Captures confirmed Google Calendar events with duration and attendees, turning meeting time into documented, billable line items
Reads GitHub commit history and pull request activity across chosen repositories and converts them into plain-language work entries
Uses OpenAI to compress each activity into a concise summary of 120 characters or fewer, then writes every row into a month-specific tab in Google Sheets

Tools Used

Gmail
Google Calendar
Google Sheets
OpenAI
n8n

Where to Get Hired for This Skill

On Contra, top freelancers across this stack have earned 189 combined verified reviews from real client projects.

Source: Contra freelancer search · refreshed 26 May 2026

Start Earning as a Freelancer on Contra

Contra is a commission-free professional network for independents. Browse live AI automation work and keep what you earn.

Join Contra Free →

How To Build It

Scope the three data sources

Define which Gmail label or sender patterns represent client work, which Google Calendar event types count as billable, and which GitHub repositories should be tracked, so the automation captures only relevant activity from the first run.

Configure the daily collection schedule

Set a recurring evening trigger so the workflow pulls that day's emails, calendar events, and commits automatically, giving clients a same-day record without any manual initiation from the freelancer.

Build the filtering and merging logic

Layer conditions that drop promotional emails, declined calendar invites, and bot-generated commits before combining the three streams into a single ordered list of work activities ready for summarisation.

Connect OpenAI to summarise each activity

Pass each activity through GPT-4o-mini with a prompt that constrains output to 120 characters, producing consistent, client-readable descriptions that can appear verbatim on an invoice without further editing.

Write rows into a month-keyed Google Sheets tab

Configure the output so a new sheet tab is created automatically on the first run of each calendar month and every subsequent daily run appends rows to that tab, keeping timesheet history clean and separated by billing period.

Pitfalls

Google OAuth tokens for Gmail and Google Calendar expire or lose scope after credential changes, silent credential failures cause entire days of activity to be skipped with no error surface unless you add an explicit failure alert.
OpenAI summarisation truncates cleanly to 120 characters in testing but drifts on edge cases like multi-repo commit messages or very long meeting titles, leaving malformed rows in the sheet that must be caught before invoice submission.
GitHub API rate limits drop sharply on accounts tracking more than a handful of repositories in a single daily run, so freelancers managing five or more active repos will hit throttling and need request batching or a staggered trigger time.

FAQ

Can I build this without coding?

Mostly yes. The Gmail filtering and Google Sheets output are configured through form fields and toggles. The one exception is a small variables block where you set repository names and calendar filter rules, which requires editing a few plain-text values rather than writing functions.

How long does it take?

A focused build with credentials already authorised typically takes two to four hours. Most of that time goes into testing the filtering logic to make sure only genuine client work reaches the sheet, not configuring the core connections.

What can I charge?

Pricing is your call based on the client relationship and scope, but the workflow has a clear ROI story: a consultant who bills hourly can show a client exactly how the automation pays for itself in recovered tracking time, which makes the conversation straightforward.

Which tool is required vs optional?

Gmail, Google Calendar, Google Sheets, and OpenAI are required for the core flow to produce any output. GitHub is optional and can be removed entirely for non-developer clients or swapped for another activity source like Slack or Jira without rebuilding the rest of the workflow.

This is original DigiNo analysis. The underlying automation pattern is a community workflow template – view the original on n8n.