Livestorm rebuilds its Pipedrive integration ahead of legacy API shutdown
Livestorm rebuilt its Pipedrive integration after Pipedrive scheduled its legacy API to be deprecated on December 31, 2025; the previous Livestorm integration stops working from January 1, 2026.
By Cora Whitley, GTM AI Analyst, Chief of Staff
Image: Livestorm press materials, from the announcement
Livestorm released a new Pipedrive connector on December 18, 2025, built on what it calls a modern, stable foundation because Pipedrive is retiring its legacy API at the end of 2025. Customers using the old integration need to migrate, since it stops working on January 1, 2026. The new connector adds field mapping for registration form data, syncs engagement metrics to Pipedrive fields, enriches the contact timeline with participant journey events, and pulls in questions asked by attendees.
The details
- Pipedrive's legacy API deprecation date is December 31, 2025, according to Livestorm.
- The previous Livestorm integration no longer works from January 1, 2026.
- Registration attributes, including custom Livestorm attributes, map to Pipedrive contact fields.
- Synced engagement metrics include attendance rate and number of questions asked.
Context
The Pipedrive rebuild was one of several CRM and marketing integration updates Livestorm shipped in late 2025, following a rebuilt HubSpot integration in November and a Brevo integration in December. In 2026 Livestorm moved toward AI tooling, with an MCP server in February, a Claude connector in August and AI Studio clips in October.
Not disclosed
- Which Livestorm plans include the Pipedrive integration
- Whether historical data from the old integration carries over automatically
- Sync frequency between Livestorm and Pipedrive
- Vendor
- Livestorm
- Category
- Events & Webinars
- Announcement type
- Feature update
Report an error
Vendors and readers can flag a factual error in this story, or ask for an image or logo to be removed. Email Cora, the editor, with the link. Image and logo removals happen within one business day. For factual corrections, Cora replies with next steps and a ForgeX lead approves the fix before it is published.
