Every 30 minutes
Turn process notes into SOP documents
Drop rough process notes into a Drive folder and get a step-by-step SOP Google Doc, announced to the team in Slack.
- Runs
- Every 30 minutes
- Apps
- Google Docs, Slack
- AI
- Yes, uses the built-in AI allowance
- Access
- service account; chat:write
Send this to your assistant
Create a ClickRuntime automation: every 30 minutes, check my Process Notes folder for new docs, turn each one into a step-by-step SOP Google Doc in my SOPs folder and announce it in #ops.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
An operations manager at a growing e-commerce company knows the business needs written procedures for returns, stock counts and supplier orders. The knowledge exists in people's heads and scattered notes, but turning it into a clean document with numbered steps never makes it to the top of anyone's list.
When rough notes can be dropped into a folder and come back as a structured SOP, writing procedures stops being a project and becomes a habit. Operations leads, team managers and trainers use it to build a library of how things are done, one process at a time.
What you get out of it
Procedures actually get written
The hard part, turning notes into a clear document, is done for you. People are far more willing to jot down a process when that is all they have to do.
Every SOP looks the same
Each one has a purpose, who it is for, numbered steps and common mistakes. A consistent layout makes procedures quicker to follow and easier to review.
The team knows when something new exists
A message in #ops links to each new SOP. People learn about the procedure when it is published, not when they happen to stumble on it.
Faster onboarding
New starters can read how a task is done instead of waiting for someone to show them. Experienced staff spend less time repeating the same explanations.
How it works
What happens, step by step
Every 30 minutes, ClickRuntime checks your Process Notes folder in Google Drive for documents added since the last check.
Documents it has already turned into SOPs are skipped.
AI rewrites each new set of notes as a procedure with a purpose, numbered steps and common mistakes.
The SOP is saved as a new Google Doc in your SOPs folder, and a message with its link is posted in #ops.
Before it runs live
- Connect Google Docs
- Connect Slack, then invite the app to the channel (type /invite @ClickRuntime there)
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
- Change what the AI looks for, or how it writes the result
- Add another app, for example also send it to Google Sheets
- Combine it with other Google Docs and Slack 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 clickruntime import on_trigger, credentials, state, ai, notify, report_fetched
NOTES_FOLDER, SOP_FOLDER = "your-notes-folder-id", "your-sops-folder-id"
@on_trigger
def run(event):
creds = Credentials(credentials.connection("google", "work"))
drive = build("drive", "v3", credentials=creds, cache_discovery=False).files()
done = state.get("done") or []
files = [f for f in drive.list(q=f"'{NOTES_FOLDER}' in parents and mimeType='application/vnd.google-apps.document' and trashed=false",
fields="files(id,name)").execute()["files"] if f["id"] not in done]
report_fetched(len(files))
if not files:
return {"summary": "Nothing new"}
docs = build("docs", "v1", credentials=creds, cache_discovery=False).documents()
for f in files:
notes = drive.export(fileId=f["id"], mimeType="text/plain").execute().decode("utf-8")[:15000]
sop = ai.generate(f"Turn these notes into an SOP with sections Purpose, Who it is for, Steps (numbered), Common mistakes:\n{notes}",
max_output_tokens=1800).text
new = drive.create(body={"name": f"SOP: {f['name']}", "mimeType": "application/vnd.google-apps.document",
"parents": [SOP_FOLDER]}, fields="id").execute()
docs.batchUpdate(documentId=new["id"], body={"requests": [{"insertText": {"location": {"index": 1}, "text": sop}}]}).execute()
notify.slack(f"New SOP: {f['name']} https://docs.google.com/document/d/{new['id']}/edit", channel="#ops")
done.append(f["id"])
state.set("done", done[-500:])
return {"created": len(files)}
FAQ
Common questions
What format should my notes be in?
Can it create training material instead of an SOP?
Does it change my original notes?
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
Draft RFP answers in a Google Doc and share them in Slack
Send an RFP questionnaire to a link and get a Google Doc with a draft answer to every question, based on your company profile, posted to #sales for review.
See how it worksWrite a weekly competitor report into Google Docs and share it in Slack
Every Monday a research report on your competitors is written into a Google Doc, with a short summary and link posted in Slack.
See how it worksTurn deal form entries into proposal Google Docs
Submit a deal form and a client proposal is written from your template Doc, saved as its own copy, and the link is posted to Slack.
See how it worksKeep exploring
Set up “Turn process notes into SOP documents” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.