• JOURNEY — journey definitions (id, name, app, status, steps, language/audience, created/updated dates)
• JOURNEY_STEP — the ordered steps within each journey
• JOURNEY_EVENT — per-visitor funnel events (sent, delivered, opened, clicked, goal achieved, unsubscribed, exited) with timestamps, mirroring the existing GUIDE_EVENT / POLL_EVENT pattern

Business impact
Without this, teams using Orchestrate for lifecycle/CS communications have to build a separate, custom pipeline against Pendo's API just for this one module, even though everything else in Pendo already flows through Fivetran. This breaks the "single ELT pipeline" model Fivetran is meant to provide and adds maintenance overhead for something that should be a straightforward schema extension.
Happy to share more detail on our specific use case (CS lifecycle reporting) if useful for scoping this.