Journey Builder Platform Upgrade & Node Deprecation
As part of our efforts to enhance the Journey Builder platform, Gupshup is transitioning all projects to a more modern and scalable infrastructure. This document outlines upcoming node updates, deprecations, user-facing changes, and next steps for all customers and partners.
📅 Effective From: Post Console 19.0 Release
A deprecation notice will begin appearing in the Console UI Journey listing page for the following legacy nodes:
| Node | Action Required |
|---|---|
| Code Node | Replace with Expression Library (for simple logic) or migrate to JB Pro (for complex functions) |
| Database Node | Use supported integrations or migrate to JB Pro for external DB support |
| Send Message Node | Use dedicated message-type nodes (Audio, Sticker, Location, etc.) |
| Clear Context Node | Used in limited cases, supported in JB Pro if required |
These nodes will continue to work temporarily, but will be fully deprecated in a future release_(Tentatively post 2 months)_. Sufficient time will be provided for migration.
Sample Screenshots of the Notice:
Notice on the Journey Listing Page
After Clicking View Effected Journeys
Journey Canvas with deprecated node
Project that doesn't contain any deprecated node(s)
Note: The notice will show on reload of the page even if the Project doesn't contain any deprecated nodes. Please ignore for such cases.
🔄 Migration Pathways
🧩 Use Alternate Nodes in JB V2
If your journey uses simple logic or API integrations, you can refactor your journeys using:
- Expression Library in Modify Variable node for manipulating runtime data
- JSON Handler node for parsing API responses or JSON Objects
- New Message-Type Nodes (Audio, Sticker, etc.) for sending WA specific message types
These features are available within JB V2(Newer Version) and require no code or migration support.
🚀 Upgrading to JB Pro (For Advanced Use Cases)
Projects that rely on custom logic or backend execution (via Code Node) can be migrated to JB Pro.
Key Notes:
- JB Pro supports Function Nodes built on Gupshup's Solutions Platform
- Migration is done only for projects managed by Gupshup Devs
- A migration script will be used to replace Code Nodes with Function Nodes
- Manual pre- and post-migration testing will be conducted by the Bot Solutions team
- Once migrated, projects cannot be reverted to JB V2
- JB Pro projects will be maintained and upgraded by Gupshup Bot Solutions only
- 📩 If your project is managed by Gupshup, please contact your Project Manager or CSM to initiate the JB Pro upgrade.
- ⚠️ Projects managed by customers directly are not eligible for JB Pro migration at this time.
✅ Next Steps for Users
- Review your journeys: Check for usage of deprecated nodes.
- Refactor using JB V2 nodes: Use Expression Library, JSON Handler, and message-type nodes wherever possible.
- Contact Support: If you require help with identifying deprecated node usage or migration options.
Stay updated: Final deprecation timeline and enforcement dates will be shared soon!
📘 Need Help?
Contact: [email protected]
For JB Pro upgrades: Reach out to your Project Manager or Customer Success Manager (CSM)
We encourage you to begin reviewing and refactoring your journeys now to avoid last-minute migration or journey failures when the final deprecation goes live.
Thank you for your continued support.
Updated about 3 hours ago