Turn a Polarsteps trip into a blog post

1. Open the trip on polarsteps.com and click the first step on the timeline.
2. Copy the step title and story into the blog editor, then fix the line breaks and add the date and place as a heading.
3. Find the photos of that step on your phone or computer, since Polarsteps step photos have no captions to carry over.
4. Go back to the trip, open the next step and repeat until the last one.
5. For the map, click Share on the trip on the desktop website and paste the embed link. A trip with dozens of steps means dozens of copy rounds, and steps are easy to skip or paste out of order.

Turn my Japan trip into a draft blog post: one section per city, the best two photos of each step, and a map embed at the top.

1. 01

   Check who may see the trip

   The agent reads the trip with get_trip first. If its privacy is Only me, it asks before drafting, because a public post would show places and stories you kept private.

2. 02

   Plan the sections

   From list_steps it groups steps by city, country or week, as you asked, and keeps travel order. Steps that are only a dot on the route, with no story and no photos, become a line in the itinerary, not a section.

3. 03

   Read the full stories

   It calls get_step for each step that has text, because the list holds only a preview. Long stories are tightened for the web, but names, prices you noted and your own phrasing stay.

4. 04

   Pick photos and write captions

   For each section it picks the photos you asked for and writes alt text and captions from the step story, since the photos themselves carry no caption.

5. 05

   Hand over a draft, not a post

   The agent saves Markdown or HTML for your blog editor, with a placeholder for the Polarsteps map embed. Publishing stays with you or another tool you connect.

Draft: "Three weeks in Japan by rail" (2,950 words)
Sections: Tokyo, Nikko, Kyoto, Nara, Hiroshima, Osaka
Steps used: 27 of 34 (7 route-only steps listed in the itinerary)
Photos: 12 picked, alt text written for each
Note: trip is set to Followers; check before publishing the Nikko hostel name
Saved: ~/blog/drafts/japan-by-rail.md

• The Polarsteps embed link comes from the Share button of the trip on the desktop website and shows a basic map of the trip.
• The Polarsteps plugin for WordPress is built by a third-party developer, and Polarsteps warns it could break when either side changes things.
• Polarsteps photos cannot have individual captions; Polarsteps suggests describing photos in the step text instead.
• A Polarsteps trip set to Only me is visible to you and your Travel Buddies, and followers see every trip on your account except those.

Every tool here only reads, so it can run on a schedule from n8n, Make, Zapier or cron without waiting for your OK.

Sources: Polarsteps Help: Can I embed my Polarsteps trip on my website? · Polarsteps Help: How do I add photos to my trip? · Polarsteps Help: Who can see my Polarsteps account and trips?

curl https://cotlet.dev/api/v1/polarsteps/get_step \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"step_id":"231908554"}'

{
  "step_id": "231908554",
  "trip_id": "18452237",
  "title": "Fado night in Alfama",
  "story": "Got lost in the old town, then found a tiny fado bar with six tables.",
  "place": "Alfama, Lisbon, Portugal",
  "coordinates": {
    "lat": 38.711,
    "lon": -9.1304
  },
  "date": "2026-10-09T19:30:00+01:00",
  "media": [
    "https://example.com/photos/alfama-1.jpg",
    "https://example.com/photos/alfama-2.jpg"
  ]
}

MCP: add https://cotlet.dev/mcp/v1 with the same key; the tool is polarsteps_get_step. Example data.

• Export a single Polarsteps trip as GPX or Markdown
• Import a past trip into Polarsteps from a spreadsheet
• Proofread a Polarsteps trip before printing a Travel Book
• Polarsteps API and MCP server: every tool
• All use cases