Windsor.ai adds Lovable, Base44, n8n and Antigravity as data destinations
Windsor.ai's June 12, 2026 changelog adds destinations for Base44, Lovable, n8n and Antigravity, launches a TradeDoubler Looker Studio connector, and adds automatic index creation for PostgreSQL and MySQL destinations.
By Cora Whitley, GTM AI Analyst, Chief of StaffOn June 12, 2026, Windsor.ai published a weekly changelog that added Base44, Lovable, n8n and Antigravity as destinations, extending its list of AI and automation tools that can receive connector data. PostgreSQL and MySQL destinations began creating indexes automatically on table creation. Connector updates covered Criteo, Shopify and Amazon Seller Central. In Onboard, selected accounts are now kept when a user re-grants connector access. The destination entries are single lines with no setup detail.
The details
- New destinations: Base44, Lovable, n8n and Antigravity.
- A TradeDoubler Looker Studio connector launched.
- PostgreSQL and MySQL destinations create indexes automatically on table creation.
- Criteo connector added 56 new fields.
- Amazon Seller Central pre-caches three more reports on account connection to reduce MCP query timeouts.
Context
Windsor.ai added Gemini, Cursor, Perplexity and Copilot destinations in April 2026 and a Manus destination that month. A week after this release, on June 19, 2026, it offered per-connector MCP servers. In July 2026 it added Supabase and Mistral destinations, and on October 2, 2026 it added Gemini Enterprise as an AI destination, where Windsor.ai is available as a data store.
Not disclosed
- How data reaches app builders such as Lovable and Base44.
- Whether these destinations require a specific plan.
- Refresh frequency for the new destinations.
- Vendor
Windsor.ai- Category
- Measurement & Attribution
- 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.
