The moment it happens
Add entries to a work log Doc
Anything you send to a link is added with a timestamp to the end of your log Doc.
- Runs
- The moment it happens
- Apps
- Google Docs
- AI
- Not needed
- Access
- read+write
Send this to your assistant
Create a ClickRuntime automation: give me a link that adds whatever text it receives, with the date and time, to the end of my Work Log doc.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
A site manager wants a single place to record what happened each day: deliveries, safety observations, visitors, decisions. People send updates by text and email, and half of them never get written down. Months later, when an insurer or client asks when a specific delivery arrived or who approved a change, there is no timeline, only scattered messages that nobody can reconstruct. The record is only as good as the memory of whoever tries to rebuild it.
Anything sent to a ClickRuntime trigger link is added to the end of your Google Doc with a date and time heading, using the Docs API to insert the text. Each entry lands in order, so the Doc becomes a chronological log that anyone with access can read, search and share.
Researchers, pilots and care workers keep similar logs for compliance and reflection.
What you get out of it
A reliable timeline for disputes
Each entry carries its date and time, so you can show what was recorded and when. When a client contests a delay or an insurer asks about an incident, the Doc provides a simple, consistent answer.
Updates are captured at the moment
Sending a line from a phone takes seconds, so the record is written while details are fresh. Memory fades quickly, and a note made the same day is far more accurate than one reconstructed on Friday.
One log for several contributors
Teams can all send to the same link, and entries appear in one document. There is no merging of notes from different people, and the log is complete even when someone is on leave.
Easy to search and share
A Google Doc can be searched with a keyword, shared with a link, or exported to PDF. You can answer a question about last March in seconds, without opening a database or asking around.
No app to learn
If you can send a text or fill a form, you can add to the log. Contributors who would never use a dedicated logging tool still keep the record up to date.
How it works
What happens, step by step
When you send a line of text to your trigger link, ClickRuntime receives it straight away.
It stamps the entry with the current date and time.
The entry is added to the end of your work log Google Doc, so the Doc becomes a running record of what you did.
Before it runs live
- Connect Google Docs
- Paste your automation's link into the other app's webhook settings
What you get
Build your own
Need it to work differently?
Your own rules
Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.
Any number of apps
One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.
AI where it helps
Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.
On a schedule or on each event
Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.
Changes you can ask for
- Act only on the items that match your own rules, and skip the rest
- Add an AI step, for example to summarize, sort or draft a reply
- Add another app, for example also send it to Slack
- Combine it with other Google Docs steps into one automation
Under the hood
The code that runs this automation
from google.oauth2.credentials import Credentials
from googleapiclient.discovery import build
from datetime import datetime
from zoneinfo import ZoneInfo
from clickruntime import on_event, credentials
DOC_ID = "work-log-doc-id"
@on_event
def handle(event):
text = ((event.json or {}).get("text") or event.body).strip()
stamp = datetime.now(ZoneInfo("Europe/London")).strftime("%Y-%m-%d %H:%M")
docs = build("docs", "v1", credentials=Credentials(credentials.connection("google", "work")), cache_discovery=False)
docs.documents().batchUpdate(documentId=DOC_ID, body={"requests": [
{"insertText": {"endOfSegmentLocation": {}, "text": f"\n{stamp} {text}"}}]}).execute()
return {"logged": stamp}FAQ
Common questions
Where in the Doc does each entry go?
Can several people send entries without overwriting each other?
Will a very long log slow the Doc down?
What permissions does it need?
Does it need AI?
How many runs does it use?
Can I change how it works?
Related
You might also like
Create a proposal from your template
Sending client details to a link creates a filled-in proposal or contract Doc.
See how it worksGet a first draft as a Google Doc from a brief
Send a topic or brief and get a structured draft saved as a new Doc in your folder.
See how it worksTurn a video into a summary Doc
Send a video link and get a summary and social posts in a Google Doc.
See how it worksKeep exploring
Set up “Add entries to a work log Doc” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.