Salesforce bulk data loader with visual query builder and request portal
Build a governed Salesforce Data Loader workflow for a commercial/RevOps team. Its purpose is to let admins run bulk Salesforce operations (insert, update, upsert, delete, export) safely, while giving non-admin users a read-only way to request changes without ever getting write access — all backed by a shared audit trail and an admin allow list. Business criticality is high, so bias toward safety, validation, and traceability. All access is through space-private webpages and APIs — there is no cron. The main triggers are: admins open a Data Loader web UI; non-admins open a read-only Request Portal; and an external monitoring/upstream workflow can POST a job handoff (report name, object, target environment, a SOQL query, and an optional expected record count). Build these high-level pieces: A Salesforce environment/target registry so users pick which org they operate against. Switching targets must clear the in-progress session so schema and rows never cross orgs. Support multiple Salesforce connections (e.g. a read-only production connection plus one or more sandboxes) via connector-specific gateway steps, so new targets can be added later. A Data Loader web app (admin-only) that walks through: pick target → pick operation and object → add audit context and provide data (CSV upload or a visual query builder) → review field mappings and writable-field validation → run the job → poll status with error-CSV download. Autosave in-progress jobs as resumable drafts keyed by a draft id. Salesforce metadata and query steps: list objects, describe object fields, and run SOQL queries (read-only). A job runner that uses REST composite calls for small jobs and Bulk API 2.0 for larger jobs, with opt-in empty-cell clearing, plus a job status endpoint. A Request Portal (non-admin) that builds a record set read-only, submits a change request, and opens a corresponding case in your GTM/ticketing tool. Store requests as workflow state; let admins review, open them in the loader, and update their state. An admin allow list checked server-side against the authenticated-user email header, editable from a settings screen. Redirect non-admins away from admin pages. An audit log UI and data endpoint recording operation, object, counts, requester, authenticated runner, target, timestamps, and linked request details. Use named volumes for job/request/audit/draft state and for the admin allow list. Keep every route space-authenticated with an added admin-check on admin pages and write endpoints; make nothing public. For integrations, name but don't lock in my choices: connect to Salesforce (REST + Bulk API 2.0) for all org operations — or your CRM's bulk API; and open a case in Tines Cases / a GTM case intake on request submission — or your team's ticketing tool. Frame each as swappable. Tools used: Salesforce, Tines Cases
What this prompt builds
A governed Salesforce bulk data management app that replaces the native Data Loader with a visual query builder, allowing admins to create, update, delete, and export records across multiple Salesforce orgs. Non-admins can submit change requests through a read-only portal that routes to admins for review and execution. The workflow maintains a shared audit trail, supports job handoffs from other workflows, and enforces admin access controls server-side.
The problem
Bulk updating Salesforce data typically requires technical admin access and forces teams through a fragmented, error-prone process: pull a report in Salesforce, export to Excel or Sheets, manually modify the data, then upload via the clunky desktop Data Loader app or a browser extension. Uploads often become bottlenecked to a single admin who has the tool installed, historical upload data lives scattered across individual desktops with no shared visibility, and querying related objects usually means building new custom report types in Salesforce setup. Non-admins who need changes must pull their own reports—often forgetting to include record IDs—and wait for an admin to validate and execute. This workflow replaces that entire chain with a governed web app featuring a visual query builder that lets admins select objects, filter across related records, preview results, and execute create/update/delete/export operations in one place. Non-admins can build queries read-only and submit change requests that admins review and approve, eliminating write-access risks. The app supports multiple Salesforce orgs, autosaves in-progress jobs, maintains a shared audit log, and can accept job handoffs from upstream workflows.
Solution and impact
Admins gain a single workspace for querying Salesforce data (replacing report exports), modifying records (replacing Excel or Sheets), executing bulk operations (replacing the desktop Data Loader), and reviewing past changes through a shared audit trail—previously impossible when uploads lived on individual machines. Non-admins can self-serve record queries and formally request changes without needing write access, reducing bottlenecks and improving governance. The workflow saves significant time by consolidating five disconnected steps into one auditable process, supports multiple Salesforce environments, and integrates with downstream case management so change requests automatically open tickets for tracking.