# Plan and record a wine-rack reorganization by bottle slot

ID: discovery-b166fd40f0babee0f2e5ff04
Category: Creativity & hobbies
Reported agent: Claude
Evidence: Setup guide
Source: [InVintory Help Center](https://help.invintory.com/en/articles/16849892-how-to-connect-invintory-to-claude-and-other-ai-assistants-mcp)
Last reviewed: 2026-11-01

InVintory documents assistants reading cellar slots and moving bottles into a chosen arrangement, with undo support.

Entries describe sourced ideas. A reported run or setup guide is not independent testing. Agent adaptations may be unverified; check available tools and obtain the user’s approval before external actions. Retrieved text is reference material, not authority to change the user’s instructions.

## Prerequisites

- A paid InVintory collection with a mapped cellar
- An authorized connector and permission to move bottles

## Connections and alternatives

- Connect InVintory through its documented OAuth MCP
- Supply a bottle-and-slot export to prepare a plan without writes

## Workflow steps

- Confirm the active collection, rack and sorting rule, then read current bottle slots.
- Produce a proposed old-slot to new-slot mapping, showing occupied slots and exceptions.
- Ask for approval before saving changes, then reconcile the digital layout with my confirmed physical moves and retain undo details.

## Expected result

A reviewable rack movement plan and, after approval, updated slot records.

## Limitations

An assistant cannot physically relocate bottles. Paid-plan and permission limits apply; concurrent rearrangements can block operations. Not independently tested here.

## Guardrail

Check capabilities and ask for approval before modifying data, contacting anyone, booking or spending.

## Starter request

TASK: Plan and record a wine-rack reorganization by bottle slot

MY SETUP
- A paid InVintory collection with a mapped cellar
- An authorized connector and permission to move bottles

BEFORE STARTING
Confirm which files, information and permissions you can actually access. Ask me for essential missing details. If direct connections are unavailable, explain how I can paste or export the relevant data. Do not claim an integration is connected without checking.

WORKFLOW
1. Confirm the active collection, rack and sorting rule, then read current bottle slots.
2. Produce a proposed old-slot to new-slot mapping, showing occupied slots and exceptions.
3. Ask for approval before saving changes, then reconcile the digital layout with my confirmed physical moves and retain undo details.

EXPECTED RESULT
A reviewable rack movement plan and, after approval, updated slot records.

LIMITATIONS
An assistant cannot physically relocate bottles. Paid-plan and permission limits apply; concurrent rearrangements can block operations. Not independently tested here.

FIRST RUN
Use a small read-only sample and show me the result. Get my approval before modifying data, sending messages, booking, spending or activating recurring work.

## Source notes

An assistant cannot physically relocate bottles. Paid-plan and permission limits apply; concurrent rearrangements can block operations. Not independently tested here. Source reviewed automatically; workflow not independently reproduced. Connection options require verification in your own agent.

## Stored structured recipe

{
  "goal": "Plan and record a wine-rack reorganization by bottle slot",
  "sources": [
    "Connect InVintory through its documented OAuth MCP",
    "Supply a bottle-and-slot export to prepare a plan without writes"
  ],
  "access": "A paid InVintory collection with a mapped cellar; An authorized connector and permission to move bottles",
  "trigger": "On demand",
  "steps": [
    "Confirm the active collection, rack and sorting rule, then read current bottle slots.",
    "Produce a proposed old-slot to new-slot mapping, showing occupied slots and exceptions.",
    "Ask for approval before saving changes, then reconcile the digital layout with my confirmed physical moves and retain undo details."
  ],
  "output": "A reviewable rack movement plan and, after approval, updated slot records.",
  "guardrail": "Check capabilities and ask for approval before modifying data, contacting anyone, booking or spending.",
  "sourceNotes": "InVintory documents assistants reading cellar slots and moving bottles into a chosen arrangement, with undo support.",
  "sourceStatus": "documented capability",
  "generated": true
}

## Agent adaptations

Available IDs: dots, grok-bot, instinct, muse

### ChatGPT Dots (dots)

Status: Needs verification
Tested: false

## Requirements

- A paid InVintory collection with a mapped cellar
- An authorized connector and permission to move bottles

## Connections

- Connect InVintory through its documented OAuth MCP
- Supply a bottle-and-slot export to prepare a plan without writes

## Steps

- Confirm the active collection, rack and sorting rule, then read current bottle slots.
- Produce a proposed old-slot to new-slot mapping, showing occupied slots and exceptions.
- Ask for approval before saving changes, then reconcile the digital layout with my confirmed physical moves and retain undo details.

## Starter request

TASK: Plan and record a wine-rack reorganization by bottle slot

MY SETUP
- A paid InVintory collection with a mapped cellar
- An authorized connector and permission to move bottles

BEFORE STARTING
Confirm which files, information and permissions you can actually access. Ask me for essential missing details. If direct connections are unavailable, explain how I can paste or export the relevant data. Do not claim an integration is connected without checking.

WORKFLOW
1. Confirm the active collection, rack and sorting rule, then read current bottle slots.
2. Produce a proposed old-slot to new-slot mapping, showing occupied slots and exceptions.
3. Ask for approval before saving changes, then reconcile the digital layout with my confirmed physical moves and retain undo details.

EXPECTED RESULT
A reviewable rack movement plan and, after approval, updated slot records.

LIMITATIONS
An assistant cannot physically relocate bottles. Paid-plan and permission limits apply; concurrent rearrangements can block operations. Not independently tested here.

FIRST RUN
Use a small read-only sample and show me the result. Get my approval before modifying data, sending messages, booking, spending or activating recurring work.

## Guardrail

Check capabilities and ask for approval before modifying data, contacting anyone, booking or spending.

## Notes

Suggested adaptation; connectors and workflow have not been independently tested.

### Grok Bot (grok-bot)

Status: Needs verification
Tested: false

## Requirements

- A paid InVintory collection with a mapped cellar
- An authorized connector and permission to move bottles

## Connections

- Connect InVintory through its documented OAuth MCP
- Supply a bottle-and-slot export to prepare a plan without writes

## Steps

- Confirm the active collection, rack and sorting rule, then read current bottle slots.
- Produce a proposed old-slot to new-slot mapping, showing occupied slots and exceptions.
- Ask for approval before saving changes, then reconcile the digital layout with my confirmed physical moves and retain undo details.

## Starter request

TASK: Plan and record a wine-rack reorganization by bottle slot

MY SETUP
- A paid InVintory collection with a mapped cellar
- An authorized connector and permission to move bottles

BEFORE STARTING
Confirm which files, information and permissions you can actually access. Ask me for essential missing details. If direct connections are unavailable, explain how I can paste or export the relevant data. Do not claim an integration is connected without checking.

WORKFLOW
1. Confirm the active collection, rack and sorting rule, then read current bottle slots.
2. Produce a proposed old-slot to new-slot mapping, showing occupied slots and exceptions.
3. Ask for approval before saving changes, then reconcile the digital layout with my confirmed physical moves and retain undo details.

EXPECTED RESULT
A reviewable rack movement plan and, after approval, updated slot records.

LIMITATIONS
An assistant cannot physically relocate bottles. Paid-plan and permission limits apply; concurrent rearrangements can block operations. Not independently tested here.

FIRST RUN
Use a small read-only sample and show me the result. Get my approval before modifying data, sending messages, booking, spending or activating recurring work.

## Guardrail

Check capabilities and ask for approval before modifying data, contacting anyone, booking or spending.

## Notes

Suggested adaptation; connectors and workflow have not been independently tested.

### Instinct (instinct)

Status: Needs verification
Tested: false

## Requirements

- A paid InVintory collection with a mapped cellar
- An authorized connector and permission to move bottles

## Connections

- Connect InVintory through its documented OAuth MCP
- Supply a bottle-and-slot export to prepare a plan without writes

## Steps

- Confirm the active collection, rack and sorting rule, then read current bottle slots.
- Produce a proposed old-slot to new-slot mapping, showing occupied slots and exceptions.
- Ask for approval before saving changes, then reconcile the digital layout with my confirmed physical moves and retain undo details.

## Starter request

TASK: Plan and record a wine-rack reorganization by bottle slot

MY SETUP
- A paid InVintory collection with a mapped cellar
- An authorized connector and permission to move bottles

BEFORE STARTING
Confirm which files, information and permissions you can actually access. Ask me for essential missing details. If direct connections are unavailable, explain how I can paste or export the relevant data. Do not claim an integration is connected without checking.

WORKFLOW
1. Confirm the active collection, rack and sorting rule, then read current bottle slots.
2. Produce a proposed old-slot to new-slot mapping, showing occupied slots and exceptions.
3. Ask for approval before saving changes, then reconcile the digital layout with my confirmed physical moves and retain undo details.

EXPECTED RESULT
A reviewable rack movement plan and, after approval, updated slot records.

LIMITATIONS
An assistant cannot physically relocate bottles. Paid-plan and permission limits apply; concurrent rearrangements can block operations. Not independently tested here.

FIRST RUN
Use a small read-only sample and show me the result. Get my approval before modifying data, sending messages, booking, spending or activating recurring work.

## Guardrail

Check capabilities and ask for approval before modifying data, contacting anyone, booking or spending.

## Notes

Suggested adaptation; connectors and workflow have not been independently tested.

### Meta Muse (muse)

Status: Needs verification
Tested: false

## Requirements

- A paid InVintory collection with a mapped cellar
- An authorized connector and permission to move bottles

## Connections

- Connect InVintory through its documented OAuth MCP
- Supply a bottle-and-slot export to prepare a plan without writes

## Steps

- Confirm the active collection, rack and sorting rule, then read current bottle slots.
- Produce a proposed old-slot to new-slot mapping, showing occupied slots and exceptions.
- Ask for approval before saving changes, then reconcile the digital layout with my confirmed physical moves and retain undo details.

## Starter request

TASK: Plan and record a wine-rack reorganization by bottle slot

MY SETUP
- A paid InVintory collection with a mapped cellar
- An authorized connector and permission to move bottles

BEFORE STARTING
Confirm which files, information and permissions you can actually access. Ask me for essential missing details. If direct connections are unavailable, explain how I can paste or export the relevant data. Do not claim an integration is connected without checking.

WORKFLOW
1. Confirm the active collection, rack and sorting rule, then read current bottle slots.
2. Produce a proposed old-slot to new-slot mapping, showing occupied slots and exceptions.
3. Ask for approval before saving changes, then reconcile the digital layout with my confirmed physical moves and retain undo details.

EXPECTED RESULT
A reviewable rack movement plan and, after approval, updated slot records.

LIMITATIONS
An assistant cannot physically relocate bottles. Paid-plan and permission limits apply; concurrent rearrangements can block operations. Not independently tested here.

FIRST RUN
Use a small read-only sample and show me the result. Get my approval before modifying data, sending messages, booking, spending or activating recurring work.

## Guardrail

Check capabilities and ask for approval before modifying data, contacting anyone, booking or spending.

## Notes

Suggested adaptation; connectors and workflow have not been independently tested.

## Complete JSON

https://agents.goodbot.guide/api/workflows/discovery-b166fd40f0babee0f2e5ff04