CloudFiles for midstream oil and gas
Midstream teams track tracts, pipeline projects and shippers in Salesforce. Easements, drawings and contracts still sit in email and shared drives. CloudFiles files, maps and generates them on the record, so answers come fast.
From an easement in a file box to a current tract record
Tracts, pipeline projects and shippers live in Salesforce. Easements, drawings and contracts are kept elsewhere and keyed in by hand. CloudFiles organizes, shares, reads and generates those documents on the record itself.
The manual way
- Land teams keep each landowner's easement, survey map and letters in shared-drive folders, outside Salesforce. When a landowner calls about a payment or a pipeline crossing their land, the agent on the case cannot see what was signed.
- Project managers set up the same folder structure by hand for every pipeline or facility project, and each team names files its own way. Drawings and inspection records go missing between phases, and handover to operations waits on a search.
- Commercial teams send shippers their contracts, invoices and tariff notices as email attachments from the account. Copies reach the wrong contact, nothing shows who opened what, and disputes start from conflicting versions of one document.
- Land administrators type each signed easement's grantor, recording details and payment terms into the tract record by hand. Records fall behind the field, and landowner payments go out late or on the wrong terms, which strains the relationship.
- Contract administrators rebuild each shipper's transportation service agreement from the last one, retyping volumes, rates and terms from the opportunity. Errors reach signed contracts, and first flow waits while a corrected version is agreed.
The CloudFiles way
- CloudFiles gives every tract on a pipeline project its own folder, nested under the project and opened from the tract's record in Salesforce. Land teams answer landowner calls with the signed easement and survey map in front of them.
- CloudFiles builds each new project's folder tree from the company's template the moment the project record is saved. Drawings, permits and inspection records have a set place through every phase, so handover to operations starts from a complete set.
- CloudFiles shares each shipper's documents through secure links from the account, limited to the shipper's email domain. With email verification on, each view is recorded, and a link can be switched off the moment the relationship changes.
- CloudFiles maps each signed easement onto its tract record, filling the grantor, recording details and payment terms. The run waits for a land administrator's approval before anything is written, so landowner payments follow the signed terms.
- CloudFiles puts current volumes, rates and terms into every transportation service agreement, straight from the opportunity and account. Shippers sign in one e-signature request, and the signed agreement is filed on the account before first flow.
Every tract and shipper file, in place from survey to service
Each job runs in Salesforce Flow on the project, tract and shipper records midstream teams already use. CloudFiles does the document work.
Pipeline project folder templates
CloudFiles builds each new pipeline or facility project's folder tree from the company's template, so engineering, construction and operations file into one structure every time.
- The copy resources flow action clones the template folder tree when a project record is created
- Construction teams file drawings and inspection records into the same sub-folders on every project
- The operations team opens the full project set from the project record at handover, with nothing missing
Pipeline tract folders
CloudFiles creates a folder for every tract on a pipeline project in Salesforce, nested under the project. Each easement, survey map and landowner letter sits with the tract it covers.
- Each tract record added to a pipeline project gets its folder from the create folder flow action
- Land teams open the tract's signed easement while they work a landowner case in Salesforce
- Every tract folder sits inside its project's, so a project's whole land file is in one tree
Secure document sharing with shippers
CloudFiles shares contracts, invoices and notices with shippers through secure links from the Salesforce account. Links are limited to the shipper's domain, and views are recorded with verified email.
- The create link flow action shares each contract or invoice limited to the shipper's email domain
- With email verification switched on, each view of a shared file records the viewer's email address
- Commercial teams switch a shared link off from the Salesforce account when a contact or contract changes
Easement processing in Salesforce
CloudFiles processes signed easements in Salesforce, mapping each easement's grantor, recording details and payment terms onto its tract record, with a land administrator's approval before anything is written.
- Signed easements uploaded to a tract record in Salesforce go through the document mapper flow action
- The tract record receives the grantor, recording details and payment terms from the easement
- Land administrators approve the run before the record changes, so payments follow what was signed
Construction packet splitting
CloudFiles splits combined construction and inspection packets received as one PDF into separate documents in Salesforce. It classifies each one and files it in the right sub-folder of the project.
- The split document using AI flow action breaks a contractor's combined PDF into its documents
- Inspection reports, test records and as-built drawings come out labeled by type and named for the project
- Every document lands in the right sub-folder of its project record, ready for handover to operations
Transportation agreement generation
CloudFiles produces transportation service agreements for shippers straight from Salesforce opportunity data, with volumes and points filled in, then collects signatures and files the signed agreement on the account.
- Volumes, rates, receipt and delivery points fill the agreement from the opportunity, with nothing retyped
- Each shipper's agreement is built on the company's own template by the generate document flow action
- Signed agreements return to the shipper's account folder in Salesforce before service starts
Key documents we handle for midstream oil and gas
These six come up on nearly every record. CloudFiles handles every other document a midstream company keeps in Salesforce as well.
Easements and survey maps
Signed easements and survey maps for each tract, filed under the pipeline project that crosses the land.
Landowner correspondence
Letters and notices sent to each landowner, kept in the tract's folder for the agent working the case.
Inspection and test records
Construction inspection reports and test records, split from contractor packets and filed by project phase.
Construction drawings
Alignment sheets and as-built drawings for each project, kept in the template folder tree from design to handover.
Transportation service agreements
Shipper terms, volumes and rates, produced from the opportunity and returned signed to the shipper's account.
Shipper invoices and notices
Monthly invoices and tariff notices shared with each shipper through domain-limited links from the account.
Stay industry compliant
CloudFiles is independently audited for SOC 2 Type II, certified to ISO 27001 and compliant with HIPAA and GDPR. Data residency is supported in the US, EU, UK and AU. Your files stay in your own storage. CloudFiles never re-hosts them, and they are not used to train our AI models.
Frequently asked questions
CloudFiles creates a folder for every tract on a pipeline project in Salesforce as soon as the tract is added, nested under its project. Each easement, survey map and landowner letter sits with the tract, and land teams open it from the record. Admins build this with the create folder flow action.
Yes. CloudFiles connects Salesforce to the storage the company already uses, whether that is SharePoint, Google Drive, Azure Blob, Amazon S3 or another provider. Project and tract folders open from their Salesforce records, and engineering keeps working in the same libraries.
CloudFiles shares each shipper's contracts, invoices and notices through secure links from the account in Salesforce, limited to the shipper's email domain. With email verification on, every view records who opened it, and the commercial team switches a link off when a contact changes.
Yes, with CloudFiles. Each signed easement uploaded to a tract is mapped onto the tract record in Salesforce, with the grantor, recording details and payment terms filled in. The run waits for a land administrator's approval before anything is written, so payments follow the signed terms.
Yes. CloudFiles splits a combined construction or inspection packet into its separate documents. It recognizes each inspection report, test record and drawing and files it in the right sub-folder of the project in Salesforce. The project's handover set stays complete and sorted.
CloudFiles copies the company's template folder tree, starter files included, into storage for every new pipeline or facility project the moment the project record is saved. Every team files into the same structure on every project. Admins set this up with the copy resources flow action.
CloudFiles produces each transportation service agreement from the Salesforce opportunity and account on your own Word or PDF template, with volumes, rates and terms filled in. The shipper receives one e-signature request, and the signed agreement returns to the account's folder.
Yes. CloudFiles runs on the custom project, tract and landowner objects midstream teams build, as readily as on accounts and opportunities. It installs from AppExchange as a managed package and adds document steps to the flows and record pages land and commercial teams already use.
Book your personalized demo
Bring a signed easement, a project template and a shipper agreement. Watch CloudFiles map, file and generate them in your own Salesforce org.