Currently get_journeys lists journeys with pagination and state filtering, but there’s no way to retrieve the full definition of a single journey — including its node logic, branches, entry criteria, and linked campaigns.
Requested tool: get_journey (or get_journey_details)
Expected behavior: Given a journey ID, return the full journey object including nodes, transitions, and associated campaign IDs — mirroring what the Iterable API returns from GET /api/journey/{journeyId}.
B: Using Claude + the Iterable MCP to audit, document, and analyze lifecycle journeys end-to-end. Right now I can list journeys but can’t inspect their logic without leaving the AI context.
Iterable API reference: https://api.iterable.com/api/docs#journeys_getJourney
Currently get_journeys lists journeys with pagination and state filtering, but there’s no way to retrieve the full definition of a single journey — including its node logic, branches, entry criteria, and linked campaigns.
Requested tool: get_journey (or get_journey_details)
Expected behavior: Given a journey ID, return the full journey object including nodes, transitions, and associated campaign IDs — mirroring what the Iterable API returns from GET /api/journey/{journeyId}.
B: Using Claude + the Iterable MCP to audit, document, and analyze lifecycle journeys end-to-end. Right now I can list journeys but can’t inspect their logic without leaving the AI context.
Iterable API reference: https://api.iterable.com/api/docs#journeys_getJourney