Operelio
Trails4 min read

What a trail is

A trail watches a folder. Every file or lead that arrives there is cleaned and checked automatically, then pushed to your CRM or held for your approval.

By Operelio team · Updated November 1, 2026

On this page6
  1. 1.What a trail does
  2. 2.What a run goes through
  3. 3.Sandbox and live
  4. 4.Who can build and run trails
  5. 5.Plans
  6. 6.Frequently asked questions

What a trail does

A trail takes the files and leads that arrive in its folder. Each one is cleaned and checked, then pushed to HubSpot, Salesforce or Pipedrive, or held for your approval.

A trail is for a source, not one spreadsheet. The next file from that source can name a column differently, like Mail address for Email: the trail finds it and says so on the run, and after a real run it remembers the name for the next file. A new source with different columns, such as a second web form, waits until you check its mapping in Map sources, which keeps one column mapping for each place leads come from.

Each file gets its own run. The trail keeps a record of every run: what each stage did, what reached your CRM, and anything that stopped it. A single lead, such as one form fill sent to the folder's webhook or email address, goes through on its own and shows on the Leads tab instead of as a run.

You build a trail in a sandbox and test it on a real file before it goes live. New trails start switched off.

What a run goes through

Each run goes through these stages in order. The formatter and the push are on every trail that goes live. The others are optional.

StageWhat it doesCost
Map sourcesRenames each source's columns to the ones the trail expects, with one column mapping for each place leads come from.Free
Cleaning stepsUp to 8 steps from Clean Headers, Deduplicate, Find & Replace, Filter & Extract, Column Manager and Remove suppressed contacts.One job for all of them
Company Active CheckScores each company's website and drops rows below the score you set.One job
Verify emailsChecks every address. Quick clean uses no verify credits and leaves out the addresses it proved can't receive mail, and throwaway ones. A full check uses credits and leaves out the rows under the send-readiness bar you set. Rows with no address follow its Send rows with no email address switch, whatever the bar.One job
ScorecardGives each row a score from 1 to 5 from rules you approve. By default 4 and 5 go on to the push, 3 waits for a yes or no, and 1 and 2 stay in Operelio.Free
CRM FormatterMaps your columns onto the CRM's fields with a saved mapping.One job
Safety checksHold the push when something looks wrong, like most of the rows dropping out before the push, or values your CRM would refuse.Free
BridgeantReads a summary of the run against rules you write, and can hold the push. It never pushes anything itself.One Bridgeant message when it reads your own words. None for switches and failsafes alone
PushCreates and updates records in your CRM, or waits for your approval first. Its Who gets each lead tab picks each record's owner.Free

A run uses up to four jobs, one for each job stage on the trail. They count toward your monthly jobs, the same as running the tools yourself. A single lead uses no job until your plan's single leads for the month are used (1,000 on Starter). Past that, each 10, or part of 10, uses one job.

Sandbox and live

The canvas has two tabs. You make changes on Sandbox. Live is the version that runs, and it stays as it is until you put the sandbox live.

ButtonWhat it does
Test runPicked in the run bar, beside Run. Runs the trail for real on a test file. It uses jobs, holds verify credits when the trail has a full email check, and never pushes to your CRM.
Dry runPicked in the run bar, beside Run. Free. Shows what the cleaning steps would do to a file. Nothing is checked or pushed.
RunRuns the sandbox trail on the file in the run bar, as a test run or a dry run, whichever is picked. After a run it reads Run again.
Put it liveMakes the sandbox the live trail, as a new version. Every run records the version it used.
Switch onStarts the live trail on the files that arrive.
Switch offStops the trail from picking up new files. A push already waiting for you stays waiting.

Who can build and run trails

Only an admin can create a trail, change it, switch it on or pause it.

Anyone in the workspace can approve or discard a push that is waiting. By default, only admins can start a test run, change a stopped run or put its fix on the trail. On Pro and above, to let everyone do these, set Fixing a stopped trail run to Everyone in the workspace, under Team in Settings, in Permissions.

Plans

Every plan can build and test trails. Switching one on starts at Starter.

FreeStarterProAgency
Trails you can build152050 shared across your workspaces
Trails switched onNo2 at a time10 at a time25 at a time, shared across your workspaces
Watched folders (per workspace)No2575200
Single leads a month without a jobNo1,0005,00020,000 shared across your workspaces

Frequently asked questions

Does anything reach my CRM without me?

It depends on the trail. A trail you start from scratch waits for your approval before every push, unless your workspace's trail settings default to pushing clean runs. Four templates push clean runs automatically. On any trail, a run the safety checks or Bridgeant flag waits for you. A single lead the Scorecard gives a 3 waits on the Leads tab for a yes or no, and in a trail's first 7 days live every single lead waits there.

Where can the files and leads come from?

From the folder the trail watches. Email files or enquiries to the folder's address, post leads from your website form, Typeform or its webhook, or add a file yourself or through the API. An email with no file becomes one lead. A trail does not watch Google Drive, Dropbox or an FTP server.

Can I change a trail after it is live?

Yes. Change it on Sandbox, test it, then put it live as the next version. Runs already recorded keep the version they ran.

Ready to get started?

Upload a file and run your first transformation. Free, no credit card required.