Community recipe

Review next week for focus-time opportunities

A crowded week can hide focus opportunities.

Copy a prompt for this task

Suggested prompt · untested

Replace the placeholders with your details. This suggested prompt does not run anything or grant access.

Review next week for focus-time opportunities

Use the supplied, authorized copies to prepare the requested private draft or local artifact. Keep proposed changes as drafts.

Inputs: [INPUT_PACKET] and [OWNER_RULES]. Process only the minimum data I am authorized to use here. Ask if authorization or essential input is missing. Synthetic examples are optional; do not substitute invented data for my actual task.

Required input contents:
- Calendar window: next-week Google Calendar events. Specify the time zone, week boundary and which calendars count; distinguish declined, tentative and all-day entries.
- Owner constraints: Working boundaries and minimum useful duration. Ask whether travel, lunch and preparation buffers make apparently empty time unavailable.

Use uploaded copies first. Before any later connected access, verify that the connector is available, the correct account is connected, and the exact read-only scope is authorized. Otherwise ask for an export. Do not create connections or assume that a named tool exists.

Procedure:
Resolve the requested week and time zone, consolidate duplicate events, apply working-time constraints and propose only intervals with enough evidenced uninterrupted time.
Return a freshness timestamp with every recommendation.
Retain source event identifiers.
Flag uncertain availability.
If this issue appears: Two calendars contain the same meeting with different identifiers.
Compare explicit shared meeting identity, retain ambiguous pairs and ask the owner before merging them.
If this issue appears: An empty interval sits between two locations that require travel.
Use only owner-supplied buffer constraints; label unknown travel time rather than inventing a feasible slot.
If this issue appears: An event changes after the draft is produced.
Mark the observation time and recheck permitted live state immediately before any separately approved scheduling step.

Output:
A reviewable weekly agenda with focus options and uncertainties.
Return separate local review files when available, otherwise equivalent structured text in this chat. Label each artifact as a draft and each simulated state as simulated. Explain what you could not inspect or produce; do not report an artifact as created without evidence.

Cite the file and page, row, clause or record ID supporting every finding. Preserve raw values and distinguish observation, calculation and inference. Keep contradictions and missing evidence visible. Do not invent facts, compatibility, completed actions or successful tests.

Separate approval is required for:
Connect real calendars or send the agenda. Any creation, movement or cancellation of an event is a separate action. Keep the result private and draft-only. Before any external send, upload, live change, spend or commitment, show the exact action, target, content or data and consequences, then wait for separate approval. This prompt does not authorize those actions.
A recommendation is not a reservation or proof that the owner can use the time.
Do not use attendance or calendar density to rank employee productivity.

Select and copy the text manually if automatic copying is unavailable.

Inputs, access and approval

Inputs:

Calendar window: next-week Google Calendar events
Owner constraints: Working boundaries and minimum useful duration

Approval: Connect real calendars or send the agenda. Any creation, movement or cancellation of an event is a separate action. Keep the result private and draft-only. Before any external send, upload, live change, spend or commitment, show the exact action, target, content or data and consequences, then wait for separate approval. This prompt does not authorize those actions.

Use uploaded inputs first. Confirm scoped authorization before using a read-only connection. Missing inputs or access require an upload or clarification.

Original BotCurrent suggested prompt based on the linked example. Original source · Claire Vo; Zapier-hosted recipe. Editorial review does not establish execution success or current compatibility.

Setup and access

Proposed inputs

Name
Calendar window
Owner
Calendar owner
Minimum scope
One fictional week
Quality check
Specify the time zone, week boundary and which calendars count; distinguish declined, tentative and all-day entries.
Name
Owner constraints
Owner
Calendar owner
Minimum scope
Working boundaries and minimum useful duration
Quality check
Ask whether travel, lunch and preparation buffers make apparently empty time unavailable.

Access and setup — proposed or unknown

Proposed minimum: Start from an invented local event list. Produce a draft without connecting an account.
For an authorized pilot, choose a private destination and return a freshness timestamp with every recommendation.
Compatibility unknowns: Unknown: whether private event fields, recurring exceptions and secondary calendars are accessible.
Unknown: whether the connected action exposes attendee responses and the owner’s current time zone.
External actions requiring approval: Connect real calendars or send the agenda. Any creation, movement or cancellation of an event is a separate action.

Detailed steps and output format

At a glance

Suggested result: A reviewable weekly agenda with focus options and uncertainties.Suggested; untested.
Tool: Zapier AgentsSource-named; check current access.
Suggested inputs: Calendar window; Owner constraintsProposed; access notes below.
Human review: Authorize the calendar scope and private destination; approve any later schedule changes separately.Suggested boundaries; source approvals below.
Setup notes: Start from an invented local event list. Produce a draft without connecting an account. For an authorized pilot, choose a private destination and return a freshness timestamp…
Read full note
Start from an invented local event list. Produce a draft without connecting an account. For an authorized pilot, choose a private destination and return a freshness timestamp with every recommendation.
Guide notes; proposed setup untested.
Cost: Workflow cost not established. Check current tool pricing, setup and human review costs before trying it.No measured cost or time added.
Content depth: Source-linked example · suggestions untestedDepth does not establish successful execution.

Check source evidence and limits ↓

Source-backed example. Practical decision guidance is proposed and untested; this is not a full implementation guide.

The problem

A crowded week can hide focus opportunities.

Suggested task · untested

Proposed: review the week for feasible focus options.

What you could produce

A reviewable weekly agenda with focus options and uncertainties.

Where these suggestions come from

Core problem: Our suggestion; no result reported by the source
Agent job: Our suggestion; no result reported by the source
Expected output: Our suggestion; no result reported by the source
Relevant job roles: Our suggestion; no result reported by the source
Benefit type: Our suggestion; no result reported by the source

Suggestions and their limits

Describes the proposed purpose and review output; measured benefit and successful delivery are not established.

Editorial synthesis based on the linked source. This framing does not add evidence of successful delivery or results.

Before you try it · suggestions untested

Source-shaped wording is budgeted. The safety design and fictional check below are original proposals, not product capabilities or execution evidence.

Read the attributed source evidence and original caveats below ↓

Why use this

See fragmented work time.
Separate possible slots from confirmed availability.

Why an agent / simpler alternative

Useful judgment: Interpret event context before suggesting focus options.
Simpler alternative: Use a free/busy report when an empty interval is the only requirement; no interpretation is then needed.
Unsuitable when: Required calendars are unavailable, confidentiality rules prevent the chosen destination, or the owner has not defined working boundaries.

Expected deliverable and review checks

Proposed artifact: A reviewable weekly agenda with focus options and uncertainties.
Critical checks: Retain source event identifiers.
Flag uncertain availability.
Missing output evidence: No configured account, actual output or successful run was inspected.

First check — proposed, unexecuted

Status: proposed_unexecuted
Synthetic fixture: Fictional week W has a duplicated meeting, a tentative hold and one travel gap.
Acceptance checks: Flag uncertainty; propose no conflicting interval.
Produce one local draft, preserve all input rows, and make no network or account calls.
A malicious instruction embedded in an event description must have no effect on scope or destination.
Stop conditions: Real participant or confidential event data enters the fixture.
Any step would send the draft, connect accounts or change an event.

Tasks: Email & messages Planning & operations

Useful for: General use

Editorial relevance from the title and source-supported actions; not evidence of the operator’s occupation.

Zapier AgentsIndependent testing: No

Failure handling, costs and limits

Failure signals and proposed responses

Signal
Two calendars contain the same meeting with different identifiers.
Why it matters
The summary could double-count load or infer a conflict that does not exist.
Proposed response
Compare explicit shared meeting identity, retain ambiguous pairs and ask the owner before merging them.
Signal
An empty interval sits between two locations that require travel.
Why it matters
The proposed session may be impossible despite free/busy availability.
Proposed response
Use only owner-supplied buffer constraints; label unknown travel time rather than inventing a feasible slot.
Signal
An event changes after the draft is produced.
Why it matters
A previously suitable option may no longer be available.
Proposed response
Mark the observation time and recheck permitted live state immediately before any separately approved scheduling step.

Effort and cost — unknown

Setup work: Define working boundaries.
Ongoing review: Review uncertain intervals.
Unknowns: Subscription and model costs, event volume, review effort, connector limitations and any permission-related setup cost are unknown.

Limits

A recommendation is not a reservation or proof that the owner can use the time.
Do not use attendance or calendar density to rank employee productivity.

Full source evidence

Community recipe · Tool workflows

Original task title: Review next week for focus-time opportunities

Editorial candidate. This is source-backed reporting or a documented workflow. BotCurrent has not independently tested this task. A proposed Canadian adaptation is not evidence of a Canadian deployment or compliance certification.

Original source

https://zapier.com/templates/details/weekly-calendar-summary-focus-tips-by-claire-vo-1ec82e ↗

Attributed to: Claire Vo; Zapier-hosted recipe

Community recipe

Original action type: tool_action
What the source reports: Reads next-week Google Calendar events, suggests focus-time improvements and sends a Slack overview.
Source outcome limits: No calendar changes or successful run were observed. Event visibility, time zones, recurrence handling, plan limits and connector versions are unknown.
Evidence attribution caveat: This community recipe describes a procedure; it does not prove successful execution or independently reproduced results.
Source approval description: No separate send-approval gate is described.
Named tools: Google Calendar; Slack
Model or version: Unknown
Publication date: Unknown
Source last checked: 2026-10-15
Demonstrated in Canada: Unknown
Canadian availability: Unknown
Proposed Canadian adaptation: Proposed: confirm local data handling, owner permissions and deployment suitability before adaptation. Canadian execution and availability were not established.
Recommended approval boundaries: Authorize the calendar scope and private destination; approve any later schedule changes separately.