If you build on top of DocSpace, version 3.7 is one to pay attention to. This release is less about UI polish and more about giving you real hooks to work with: webhooks for AI and form events, a richer plugin SDK, and AI features you can wire into larger workflows.
In this post, we'll walk through what's new from a developer's point of view — what each feature does, why it matters for integrations, and where you can start building. Here's what we'll cover:
- AI building blocks you can extend, including file generation and new providers
- Form Filling rooms as data pipelines, with external database export
- A bigger plugin toolbox: CSS, localization, selectors, and progress feedback
- New webhook events and the Embed SDK Uploader example
Let's dig in.
AI Features You Can Build Around
The AI layer in DocSpace got more capable and more flexible. For technical teams, that means cleaner integration and fewer manual steps.
File generation in AI chats. Agents can now produce DOCX files, PDF forms, and PPTX presentations straight from the chat, opening them in a new tab for editing. This turns the agent into a content-producing step in a workflow rather than just a Q&A box — useful when you want generated output to flow into the next stage of a process.
More providers. You can now connect DeepSeek, Google AI, and xAI alongside Anthropic, OpenAI, OpenRouter, Together AI, or a custom endpoint. Match the model to the task — cost, latency, or capability — without reworking your setup.
Default provider sync to editors. Set a provider and model once in DocSpace AI settings, and the editors' AI plugin picks it up automatically. No more configuring AI in two places.
Image upload in chat. Push images from DocSpace into the chat to give agents visual context for a task.
Extended thinking. For complex prompts, the chat can surface an extended thinking section, so you get more insight into how the agent reached its answer — handy when debugging prompt behavior.
AI disable controls. Admins can switch AI on or off across DocSpace and the editors. When off, settings and agents are hidden, but chat history stays intact. That's useful for staged rollouts or compliance windows.
A note on availability: File generation and provider sync ship by default for Cloud users. On server builds, these rely on the Automation API, which is currently available on request.
Form Filling Rooms: A Workflow and Systems View
Form Filling rooms picked up changes that matter well beyond the UI. If you treat forms as data pipelines, this is the section to read.
External database export. Responses still land in a spreadsheet by default, but you can now push them to an external database. Connect it via Settings → Integration → Third-party services, then enable "Export results to the database" in the room settings. Form data flows straight into your own systems instead of living in a single file.
Create and edit PDF forms in-room. No more uploading a finished form from a device or template library. You can build and edit PDF forms directly inside the room, which shortens the loop between designing a form and collecting data.
New Start filling flow. A form must be switched into filling mode with Start filling, available from the file context menu or the editor toolbar. Once active, every room member can complete it. Watch out for one thing: editing a form while it's in fill mode triggers a warning, since it leaves fill mode and becomes hidden for the Form filler role.
Sync responses to XLSX. A new option refreshes the XLSX file where responses are gathered, so your exported snapshot stays current.
Taken together, these give you a cleaner path from form creation to structured, queryable data.
New Options for Plugin Developers
If you write your own plugins, 3.7 gives you a lot more to work with — and lets your plugins feel like a native part of DocSpace rather than a bolt-on.
- CSS customization support. Style your plugin to match your brand or the surrounding interface, so it feels built-in instead of borrowed.
- Plugin localization support. Ship your plugin in multiple languages without forking the code for each region.
- Group menu actions for files, folders, and rooms. Add your own actions to the group menu, so users can run plugin logic across multiple selected items at once.
- Custom selectors. Build basic, file, room, group, and user selectors so your plugin can ask users to pick exactly the right object, using selection patterns they already know.
- Custom operations with custom icons in a floating progress bar. Long-running tasks can report progress through the floating progress bar with your own icons. Clear feedback is essential for any operation that isn't instant.
- Media viewer embedding. Embed your plugin inside the media viewer to add context, controls, or actions right where users preview files.
- Context menu actions on a specific file, folder, or room. Attach plugin actions to a single item's context menu, so the right action appears exactly where it's relevant.
Why this matters: together, these options close the gap between a plugin and the core product. You can style it to fit, translate it, hook it into the same menus and selectors users rely on, and give honest progress feedback during real work. The result is richer extensions and workflows that feel native.
To get started, check the DocSpace Plugins SDK.
Developer Tools and Webhooks
Developer Tools have moved out of Settings into their own section, making the SDKs and related options easier to find and work with.
Embed SDK now includes a new Uploader setup example that lets you specify the file save location and configure parameters for uploading files and folders. If your integration brings files into DocSpace from another system, this gives you a clear starting point for controlling where uploads land and how they behave.
New Webhook Events for AI and Forms
Webhooks let you trigger custom actions in any app or website based on what happens in DocSpace. This release adds events for both AI and form handling:
AI Agent createdAI Agent updatedAI Agent deletedForm SubmittedForm Filled OutForm Stopped
In practice, these open up some useful patterns:
-
Notify on submission. Fire a message to the team chat when a
Form Submittedevent arrives, so the right person reviews it fast. -
Kick off downstream processes. Create a ticket, update a CRM record, or start an approval flow on
Form Filled Out. -
Keep an audit trail. Log
AI Agent created / updated / deletedevents to track who changed what, and when. -
Protect dependent jobs. Pause or notify a connected service on
Form Stopped, so downstream tasks don't run against incomplete data.
Because webhooks reach any external endpoint, you can stitch DocSpace events into the tools your team already uses — no polling, no manual checks.
What Else Is New
Beyond the developer-facing changes, 3.7 also brings room grouping, the ability to replace default file templates, a unified Billing section, the latest editor versions, easier room tag management, and the option to prohibit creating external links — among other improvements.
Top comments (0)