Package Information
Available Nodes
Documentation generating…
Documentation
n8n-nodes-camp-trip-planner
An n8n community node for camp cooks. Camp Trip Planner estimates the water,
stove fuel and cooler ice a group needs, returns a 42-item camp kitchen packing list, and turns a
Markdown packing checklist into a progress summary.
- No credentials, no network calls, no runtime dependencies: everything runs inside the node.
- Deterministic: the same input always gives the same output.
- Every number comes from a stated rule. The rules are returned with each result and can be overridden.
Typical workflows: a form (n8n Form Trigger, Typeform, Google Forms) → Plan Supplies → email or
Slack message with the shopping amounts; Packing List (Markdown) → Notion, GitHub issue or e-mail;
a shared checklist → Parse Checklist → reminder for the items still left.

Installation
In n8n (self-hosted): Settings → Community Nodes → Install, enter n8n-nodes-camp-trip-planner,
and accept the community-node notice. See the
community nodes installation guide.
Manual install (for example in Docker or a queue-mode setup):
cd ~/.n8n/nodes
npm install n8n-nodes-camp-trip-planner
# restart n8n
Operations
Plan Supplies
Inputs: People, Nights, Meals per Day, Hot Drinks per Day, Climate (Temperate / Hot),
Stove Type (Canister / Liquid fuel), and an optional Assumptions collection to override any rule.
Real output from n8n 2.48.5 for 4 people, 2 nights, 3 meals and 2 hot drinks a day, hot climate,
canister stove (shortened: sources and notes are also returned):
{
"people": 4, "nights": 2, "days": 3, "climate": "hot", "stoveType": "canister",
"water": {
"drinkingCookingGallons": 24, "drinkingCookingLiters": 90.8,
"washGallons": 6, "washLiters": 22.7,
"totalGallons": 30, "totalLiters": 113.6
},
"fuel": {
"stoveType": "canister", "litersHeated": 24, "amount": 360, "unit": "g",
"description": "about 360 g of canister fuel (isobutane-propane), approximate",
"approximate": true
},
"ice": { "pounds": 36, "kilograms": 16.3, "ruleOfThumb": true },
"assumptions": {
"daysMode": "nightsPlusOne",
"drinkingCookingGallonsPerPersonPerDay": 1, "hotClimateWaterMultiplier": 2,
"washGallonsPerPersonPerDay": 0.5, "cookingLitersPerPersonPerMeal": 0.5,
"litersPerHotDrink": 0.25, "canisterGramsPerLiterBoiled": 12, "liquidMlPerLiterBoiled": 20,
"fuelReserveMultiplier": 1.25, "iceLbPerPersonPerDay": 2, "hotClimateIceMultiplier": 1.5
}
}
With a liquid-fuel stove the same trip gives "amount": 600, "unit": "ml" of white gas (checked in the unit tests).
Packing List
Returns the built-in camp kitchen list: 42 items in 7 groups (Cooking gear, Sink and water, Eating,
Food storage, Lighting, Cleanup, Safety and misc).
- Output: One Item per Entry gives 42 n8n items, for example
{"group": "Cooking gear", "item": "Stove", "checked": false}…{"group": "Safety and misc", "item": "Cooler thermometer", "checked": false}. - Output: Markdown Task List gives one item:
{
"markdown": "# Camp kitchen packing list\n\n## Cooking gear\n- [ ] Stove\n- [ ] Fuel (plus a spare)\n- [ ] Frying pan\n...",
"itemCount": 42,
"groupCount": 7
}
The Title option sets or removes the top heading.
Parse Checklist
Input: Markdown with # / ## section headings and - [ ] / - [x] task items (*, + and
numbered 1. items work too). Items before any heading go to (no section).
Input used in the test run:
# Camp kitchen packing list
## Cooking gear
- [x] Stove
- [x] Fuel (plus a spare)
- [ ] Frying pan
## Sink and water
- [x] Water tank or jug
- [ ] Biodegradable soap
## Food storage
- [x] Cooler with block ice
Real output:
{
"total": 6, "packed": 4, "left": 2, "percentPacked": 66.7, "complete": false,
"sections": [
{ "section": "Cooking gear", "packed": 2, "total": 3, "left": 1 },
{ "section": "Sink and water", "packed": 1, "total": 2, "left": 1 },
{ "section": "Food storage", "packed": 1, "total": 1, "left": 0 }
],
"itemsLeft": [
{ "section": "Cooking gear", "item": "Frying pan" },
{ "section": "Sink and water", "item": "Biodegradable soap" }
]
}
The Markdown from Packing List can be fed straight into Parse Checklist.
Assumptions and sources
Trip days = nights + 1 (arrival and departure days); switch to "Nights Only" in Assumptions → Days
Counting. All per-day figures are multiplied by people × days.
| Field | Default | Source / status |
|---|---|---|
| Drinking and cooking water | 1 gal per person per day | Ready.gov: store at least one gallon per person per day |
| Hot climate water multiplier | × 2 (drinking and cooking water only) | Ready.gov: in very hot temperatures, water needs can double |
| Wash water | 0.5 gal per person per day | Assumption for dishwashing and hand washing, not a published standard |
| Water heated per meal | 0.5 L per person per meal | Assumption |
| Water per hot drink | 0.25 L | Assumption (one mug) |
| Canister fuel | 12 g per liter brought to a boil | Rule of thumb; real stoves use roughly 8–15 g/L in mild, calm weather |
| White gas | 20 ml per liter brought to a boil | Rule of thumb; liquid-fuel stoves usually burn more per liter, plus priming |
| Fuel reserve | × 1.25 | Assumption for wind, cold, simmering and spills |
| Ice | 2 lb per person per day | Rule of thumb for a well-packed, shaded cooler, not a measurement |
| Hot climate ice multiplier | × 1.5 | Rule of thumb |
Fuel = liters heated × fuel per liter × reserve, rounded up. Liters heated = person-days ×
(meals × 0.5 L + hot drinks × 0.25 L).
Fuel and ice figures are approximations: stove model, pot, wind, altitude, cold and how often the
cooler is opened all change the real numbers. Test your own gear before a long trip, and keep cold
food at or below 40 °F (4 °C) (USDA). The packing list is the one used in the
Camp Kitchen US camp kitchen checklist.
Compatibility
Tested on n8n 2.48.5 (Node.js 26.13.1). Uses n8nNodesApiVersion 1 and sets usableAsTool, so AI Agent nodes can call it
(the agent-tool path was not part of the test run).
Development and tests
npm install
npm run lint # official n8n node linter (@n8n/node-cli)
npm test # builds dist/ and runs 23 unit tests with node --test
The calculation logic is a separate module, nodes/CampTripPlanner/planner.ts, with no n8n imports.
The unit tests live in test/ and are not part of the npm package.
How the node was tested in a real n8n: the packed tarball was unpacked into the custom folder of a
throwaway N8N_USER_FOLDER, four workflows (one per operation and output mode) were imported and run
with n8n execute, and the editor screenshots in docs/ were taken from the same local instance.
License
Developed with help from an AI assistant (Claude Code), then tested on n8n 2.48.5 as described above.