A Weekly Grok Workflow Built Around One Skill and One Connector
Most people who try Grok's newer features, Skills and Connectors, set one up, use it once, and drift back to plain conversations by the following week. The setup itself isn't the hard part. Building it into an actual weekly rhythm is. If either feature is new to you, the Complete Beginner's Guide to Grok is worth reading first; this is about wiring one of each into a real week.
Here's the workflow for a real role: an operations lead at a small logistics company who manages a five-person team, tracks open items on a shared Notion board, and spends every Friday afternoon writing a status update for leadership that always ends up in roughly the same format anyway.
Call her Priya. Everything below follows her through one invented week, using an invented board, so you can see what goes in and what comes out at each stage.
The input: what Priya's board looks like
This is the state of the shared Notion board as of Monday morning, illustrated. Everything on it is made up for this example.
Priya's team board on Monday morning, illustrated with invented items
| A | B | C | D | |
|---|---|---|---|---|
| 1 | Item | Owner | Status | Due |
| 2 | Chicago warehouse delayed shipment | Marcus | In progress | Wed |
| 3 | Routing software vendor pricing | Priya | Blocked | Last Fri |
| 4 | Reassign Route 7 after driver resignation | Yusuf | Not started | Thu |
| 5 | Update driver onboarding checklist | Elena | In progress | Next Mon |
| 6 | Q3 fuel cost summary | Marcus | Done | Tue |
The two pieces, and why just one of each is the point
The temptation once you've discovered Skills and Connectors is to set up several of each. Resist that for the first few weeks. One Skill that handles a genuinely recurring task, and one Connector to the account that task actually depends on, is enough to build a real habit around. Adding more before the first pair is second nature just creates more things to remember to use.
The Skill handles how a recurring task gets done: the format, the tone, the structure that shouldn't have to be re-explained every week. The Connector handles what account Grok can actually see: the current state of the Notion board, not a manually copied snapshot of it from three days ago.
Setting up the Connector first
- 1
Connect the Notion workspace
From grok.com's Connectors settings, authorize Notion through its own OAuth screen. Review the permissions the connector requests and, where Notion lets you choose, keep them to the shared team workspace the recap needs, since this workflow is about reading the board's current state, not having Grok edit it directly.
- 2
Test it with a question you already know the answer to
Ask something like which items on the board are currently marked blocked, and confirm the answer matches what you'd see if you opened Notion yourself right now, not a stale or partial read.
Building the Skill second
Create a Skill called "Friday Ops Recap." When I ask for this week's recap, pull the current state of our team's Notion board and combine it with any rough notes I paste in. Structure the output as: a one-line summary at the top, a section called "Completed This Week," a section called "In Progress" with an expected date for each item if one exists, and a section called "Needs Attention" for anything blocked or overdue, only include this section if something actually qualifies. Keep the tone factual and direct, no filler phrases like "great progress this week." Each line should be one sentence.
”Notice this Skill's instructions explicitly reference pulling from the connected board, that's what makes the Skill and the Connector work as one system instead of two separate features used side by side.
The actual week
| Day | Prompt type | Tools involved | What Priya gets back |
|---|---|---|---|
| Monday | Short question | Connector only | A list of blocked or overdue items |
| Wednesday | Short question | Connector only | What moved since Monday |
| Friday | Named Skill plus rough notes | Skill and Connector | A structured recap ready to send |
- 1
Monday: quick board check
A short prompt using the Connector, no Skill needed yet: "Anything on the board marked blocked or overdue as of today?" This catches a stuck item early in the week instead of discovering it Friday.
- 2
Wednesday: midweek gut check
Same short Connector-only question. This is intentionally lightweight, the point is catching drift early, not writing a report twice a week.
- 3
Friday: the recap, using both together
Paste in whatever rough notes exist from the week and invoke the Skill. Because the Connector is already read into the Skill's instructions, this single request pulls current board state and combines it with the notes automatically.
A representative Monday answer from the Connector, illustrated
That answer is small, and that is the point. It takes ten seconds and turns two silent risks into things Priya can act on Monday, such as chasing the vendor and asking Yusuf to start on Route 7 today rather than Thursday.
Friday Ops Recap. This week's rough notes: closed out the delayed shipment issue with the Chicago warehouse, still waiting on the new routing software vendor to confirm pricing, one driver route needs reassigning after a resignation, team meeting Wednesday went fine.
”Because the Skill's own instructions already point at the connected board, this one message produces a recap that reflects both the notes just pasted in and whatever the board currently shows, without a separate step of manually checking Notion first and copying anything over.
A representative Friday Ops Recap output, illustrated
Notice what the output does and does not contain. The Q3 fuel cost summary appears even though Priya never mentioned it in her notes, because the board did. The Wednesday meeting does not appear at all, because nothing in the Skill's structure asks for it. And the Needs Attention section is present because two items actually qualify. If nothing had been blocked, the Skill's own instructions would have left it out.
Why it works: the Skill fixes the format so Priya never re-explains it, the Connector supplies the current facts so she never copies them, and her rough notes supply the part only she knows. Next move: read the recap once against the board before sending, since the Connector reads what is on the board, and a stale board produces a stale recap. If the recap format needs to change, edit the Skill once. Building a Custom Grok Skill and Setting Up Grok Connectors for GitHub, Notion, and Google cover both pieces in depth.
Common mistake
Setting up the Connector and the Skill in the same session and never testing them together before the first real Friday. Run a low-stakes test earlier in the week, a Wednesday check-in is a good moment, so any gap between what the Skill expects and what the Connector actually returns gets caught before it matters.
Where this breaks down
The most common failure isn't technical, it's habit. People set this up once, get a good result, and then forget to invoke it the following week because typing the recap from scratch was the default behavior for months before that. Naming the Skill something memorable and specific, not "recap" or "report," makes it easier to remember it exists. The second common issue is granting the Connector write access it doesn't need for this workflow, when read access is enough for pulling board state into a recap; widen the scope only if a later task genuinely requires Grok to update the board itself.
Start with exactly one Skill and one Connector, not several of each, until the pairing is a real habit.
Approve only the access the workflow actually needs, and check what the Connector requests before you authorize it, since a recap doesn't need to edit the board.
Write the Skill's instructions to explicitly reference the connected account, so the two work as one system.
Test the pairing on a low-stakes day, like a Wednesday check-in, before relying on it for the real Friday recap.
Give the Skill a specific, memorable name so the habit of using it actually sticks.