# Flori workflow recipes

Use these as instructions for a work chat or private Grok Bot with Flori connected. These are copyable recipes, not published marketplace bot templates. Each person signs in to their own Flori account. No keys, private projects, conversation history, or scheduled routines are included.

## Keep my projects updated

Use Flori as my project record for relevant work in this chat. Call get_workflow first. Respect Keep work updated and granted scope. Search for the matching project/task and read it before making changes. Keep its IDs for this chat. Create tasks only for concrete work I commit to, not every idea. At meaningful milestones and before finishing, use record_work for a concise factual update, decisions, blocker, next step and useful artifact links. Preserve existing context. Skip unchanged or unrelated turns. A draft is not a sent message; mark done only when the requested outcome happened. Do not save transcripts, keys or unrelated private content. Honor host approvals. Report success only after the save receipt; otherwise say saving failed. Never queue agent execution or take external actions merely because progress recording is enabled.

## What needs me?

Read get_review_queue in my Flori scope. Show up to five items that need a decision, with the reason, the task link, and the smallest useful next action. Distinguish a draft awaiting review, a dependency blocker, an overdue date, and work with no recent update. An old update alone is not proof the project is failing. Do not change dates, dismiss items, approve drafts, or mark tasks complete without my decision. For private Google sources or meeting briefs, point me to Flori's Review page; do not claim the MCP connector read those sources. If nothing needs attention, say so briefly.

## Pick up where I left off

Ask which project only if this chat does not identify it. Call get_workflow, search_workspace and get_task to read the chosen work and its current context. Summarize the outcome, last confirmed progress, open blocker, next step, and artifact links. Do not infer this chat's target from another assistant's recent save. If I ask you to continue a task from the background backlog, read list_ready_tasks and claim_task before acting. Stay within host authorization. For foreground work I directly request here, proceed within that request and save relevant progress. Drafts return for review; failed or uncertain external actions stay unconfirmed.

## With an existing Notion page or Jira ticket

When I explicitly choose a source item and its separate connector is available, read that item and keep its URL with the matching Flori task. Keep the original service authoritative for its document or ticket. Save a brief linked handoff, not a duplicate database. Do not claim Flori directly synchronizes Notion or Jira. Source updates require the source connector, my authorization and a readback; a Flori save alone does not update the original. If the records conflict, show the conflict instead of silently overwriting it.

## Suggested one-time test

Create one synthetic task with no project. Save a progress note, read it back, and confirm its receipt. Leave agent execution off. Then start a second chat and find that same task. Confirm that scope, status, context and links match. Stop if any tool fails, asks for new permissions, or returns data from an unexpected workspace.

Custom endpoint: https://useflori.com/mcp
Setup and current status: https://useflori.com/integrations/grok
Privacy: https://useflori.com/privacy