SpringRoll now has a connection for working with your apps from ChatGPT, a data explorer for checking what an app can read, and more ways to connect company systems. Action reviews explain the exact change before you confirm it, approvals show who still needs to decide, and your first successful deployment email takes you straight to the app.
Work with your apps from ChatGPT
The new SpringRoll connection for ChatGPT lets you find the apps you can use, check deployments and backing services, and prepare a deployment, promotion, restore or other app change. Each change comes back as a saved proposal to review in SpringRoll. Apps built with SpringRoll's record integration can also let you read, create and update their records through the connection, within your existing app access and the permissions you gave it. There is no separate collection approval, including after a new release, and every record change still needs its own confirmation. Availability depends on your client's connection settings and your workspace's hosting setup.
Why we built it: Asking about an app and acting on the answer should fit into the same conversation. The connection brings that work together while keeping each change tied to your identity, your current access and a proposal you can inspect before anything happens.
Action reviews that explain the change before you confirm
A ChatGPT action review now leads with the app, workspace, environment, connected account and what will happen. Deployment proposals explain the hosting plan, backing services, runtime limits and estimated cost, including when the estimate is incomplete. Record proposals show the fields to change, and the confirmation button names the action. You can confirm for yourself, or explicitly instruct your agent to submit that exact proposal through the same page. An agent submission must declare your current approval and include a short note, recorded in the audit trail. Changed or expired proposals need a fresh review, and existing governance approvals still need a person to decide them.
Why we built it: A confirmation should tell you what you are agreeing to and what happens next. Plain descriptions, a clear status and a record of who submitted the confirmation make it easier to delegate the work while keeping the decision yours.
Explore data before putting it in an app
Each data product now has Overview, Explore and Use in an app views. In Explore, choose fields, filters, sorting and a row limit, with totals and grouping where the source supports them. Structured queries work without an AI key, and Explain query checks a query without reading the source. Owners can preview a small sample, while app managers can choose an app and environment to see exactly what its current grant allows, including field restrictions, masking and row filters. Use in an app takes you to the access request and gives you copyable integration examples for the fields already approved.
Why we built it: A connection is only useful when you can check what comes back. Seeing a sample under the same rules the app will use helps owners publish the right fields and helps builders find access problems before they reach a working app.
More sources for approved company data
Data products now support MySQL, MariaDB, Oracle and SQL Server alongside PostgreSQL. Database connections check that their source account has read-only permissions. You can also publish selected fields from explicitly mapped JSON GET resources in a REST API, starting with an OpenAPI document or a manual mapping. You review the resources and fields before publishing, and newly discovered or changed fields stay unavailable until an owner reviews and saves them. Source credentials stay in SpringRoll.
Why we built it: Company data rarely lives in one database. Supporting more sources lets an app use the systems your team already runs, while the owner still chooses what to expose and the app receives only the access it was granted.
Use company APIs with approval for the exact endpoints
The Native APIs view in Data now lets an app request specific methods and paths in Notion, Salesforce, SAP, ServiceNow, Microsoft 365 and configured API gateways. The connection owner or an administrator reviews the endpoints, app environment, purpose, expiry and request budget. Your app keeps the platform's normal request and response format, and SpringRoll checks the grant before sending each request. Notion, Salesforce and SAP now use this route exclusively. If you previously used a data product for one of them, request native endpoints before moving the app over; an old field grant does not authorize API access. Native endpoint grants rely on the source account's permissions and do not apply data product field masking or row filters.
Why we built it: An existing API client should not need a new query language to work through SpringRoll. Approving the exact endpoints keeps that integration familiar and gives the data owner a concrete decision about what the app may do in each environment.
Connect your own Notion and Salesforce accounts
The Your accounts view in Data lets members connect Notion and Salesforce through their organization's registered integration. Administrators set up that registration in Connectors, and each member links their own account separately. ChatGPT can then use the supported Notion item and Salesforce Task actions within the approved sources and fields, with confirmation for every change. If you connected an account before it was linked to an organization registration, reconnect it through Your accounts. Changing or disabling the registration also requires reconnection.
Why we built it: A shared connection for an app should not quietly become permission to change someone's business records. Separate member accounts keep each action tied to the person asking for it and let the organization control which integration those accounts use.
Approvals that show who still needs to decide
Approval routing now names the people who can decide each request type, shows the Production and high-risk rules that apply, and warns when a reviewer role has nobody in it. Submitting a request tells you who it went to. When a request needs different reviewer groups, each group must be satisfied; two approvals from one group cannot fill another group's place. The inbox, navigation badge and waiting data requests now use the same rule for what still needs your decision. Data requests show who asked, why, the environment and each field's sensitivity before you grant access, and a direct data decision resolves its linked request too.
Why we built it: A request should never look finished while a required reviewer is still missing, or keep asking for a decision that has already been made. Showing the remaining people and keeping the counts consistent tells both the requester and the reviewer what needs to happen next.
Your first deployment email takes you to the app
The one-time email after your first successful deployment now names the app, workspace, environment, version and hosting provider. Open app takes you to the deployed app when a direct link is available, and View deployment takes you to its details and logs. The email also links to app access so you can review who may open it before sharing, with inviting a teammate as an optional next step. The deployment and your access are checked again before the email is sent.
Why we built it: When your first app is ready, the next thing you want is to open it. A useful receipt gets you there immediately and keeps the details and sharing controls close by, without making you find the deployment again.
Guides that follow the work you came to do
The public SpringRoll site now walks through deployment, the App Portal and governed data access with product views and examples. Learn brings together the docs, deployment and approval guides, managed hosting guidance, an operations dashboard example and comparisons with other approaches. Agent setup instructions and starter downloads are easier to find, and the public menu groups the same destinations on a phone.
Why we built it: Before connecting a coding agent or deploying an app, you need to know how the pieces fit together. Task-based guides and concrete examples let you follow the part that matters to you and see what using SpringRoll will involve.
Also improved
- Workspace navigation now shows Approvals and Agent connections when they are relevant to your role or existing work, with the same names on pages, menus and back links.
- App statuses, environments and approval decisions now use consistent plain words, so the same state reads the same way wherever you see it.
- Pages you cannot access explain the restriction inside your workspace and, where appropriate, name the administrators who can help.
- Related-app tag links and app tag filters now work without an error.
- All five app tabs fit on a narrow phone screen, and the workspace phone menu scrolls all the way to Sign out.
- ChatGPT action status now distinguishes a queued request, work in progress and an outcome that needs checking, with links to the app or deployment when available.
- If a self-hosted upgrade is missing required database updates, the ChatGPT connection now gives a setup explanation instead of a generic failure.