Leads cleaned, scored and routed
into your CRM.

A trail is an automation you build once on a canvas. A file or a single lead arrives, and the trail cleans it, scores it if you add a Scorecard, checks it against your CRM and pushes it into HubSpot, Salesforce or Pipedrive. A file's emails can be verified and its companies checked on the way. After that it runs on everything that arrives, and every run is recorded.

No. A trail is for a source, not one spreadsheet, so each file from that source can name its columns a little differently. When a file calls a column something else, like Mail address for Email, the trail finds it and the run says which column it used. After a real run uses it, the trail remembers the name for the next file. If two columns could both fit, the trail never guesses: the run waits and asks which one, and remembers your pick. A tidy-up step like Find & Replace whose column is missing is skipped, and the run says so. A step that decides which rows go on, like Deduplicate, stops the run instead. You can change that for each step. With Map sources on, each new source's columns are mapped onto the trail's once, and a source that can't be matched for sure waits for you.

Running repeated data jobs, such as moving, cleaning and checking records, without someone doing each step by hand. A trail does it for the files that feed your CRM: each file that arrives runs the steps you chose, such as cleanup, verification and routing, then goes to HubSpot, Salesforce or Pipedrive.

HubSpot, Salesforce and Pipedrive, and both kinds of record: HubSpot contacts and companies, Salesforce contacts, leads and accounts and Pipedrive people and organizations. People are matched on email address, companies on website or name. The CRM Formatter can shape a file for eight CRMs, and you can download the result for any of them; the push into the CRM is for those three.

Drop a file into the folder the trail watches, email it to the folder's own address, or upload it through the API. Emailed CSV, Excel, PDF and Word files are read, and a PDF or Word file is read for its tables. Single leads come in one at a time: posted to the folder's webhook, or as an email with no file. You can limit which senders the folder accepts. A trail can also run on a schedule: every day, weekdays, weekly, or every 6, 8 or 12 hours, in your time zone.

Only if the trail is set to send clean runs on its own. A new trail waits for you on every push, unless its template or your workspace's default says otherwise. Even then, anything the safety checks or Bridgeant flag waits for you. Nothing ever sends from a dry run or a test run.

In two places. The Deduplicate step removes rows that repeat a person or a company inside the file, with exact, smart or similarity matching. Then the push matches every row against what your CRM already holds, usually on email address, so existing records are updated rather than created again, and a value your CRM already has is kept unless you allow it to be replaced.

Yes. A Free workspace gets one trail and the whole sandbox: build it, dry run it, test run it on a file of your own and download the result. The paid parts stay on the canvas with a padlock. Switching a trail on so it runs by itself starts on Starter. A lead that arrives while the workspace is on Free is kept for 24 hours. Move up to Starter by then and it goes to your CRM.

Ordinary jobs, the same as running the tools by hand. The cleaning steps run as one job, and each stage after them (Company Active Check, verifying emails, the CRM Formatter) is a job of its own. A full email check spends verify credits, and a Bridgeant review spends one message when it reads words you wrote. Switches and failsafes on their own are checked by Operelio for free. A dry run costs nothing.

The trail holds the file, emails the people you named once, and shows the reason on the run page with what it would have done. Fix the cause, then resume the run or discard it. If the same problem happens again, the trail switches itself off and tells you. A missing column never switches it off: it stops only that run.

Yes, there is a template for it: Cognism, Apollo, ZoomInfo and the like. It drops companies that look inactive, sends only verified email addresses, screens the list against your Do Not Contact list, and Bridgeant reviews the push before you see it.

When the review is switched on for a trail, Bridgeant is given counts, column names, CRM field names and the instructions you wrote, word for word. Never the values in your file, so keep names and addresses out of your instructions. It runs once a run after the safety checks, and the only thing it can do is hold the push. There is no answer that means send it.

The trail uses one sheet and holds the push so you can check it was the right one. It is one of the nine checks that cannot be switched off.

The push is worked out again against your CRM as it is now before anything sends. If a row would now replace a value it did not before, a new reason to hold turns up, or too many rows would now do something different (10% by default, set on each trail), the run is held again and tells you why.

Those are general tools: you connect steps and build the checks yourself. A trail does one job, getting a file into your CRM safely, and comes with the cleaning, verification, matching, checks and approval already built in. There is nothing to code and no one to hire to set it up.

Every lead in one list, checked against your CRM: sent, waiting for your yes, or held with its reason. See lead management.

Yes. Routing is part of the push: an ordered list of rules where the first one a lead matches decides, then Otherwise for the rest. Rules test a column, the score, the source or the CRM check. They send to a person, a team in turn, the company's owner, the owner a column names, the review queue, no owner, or drop the lead. A team in turn keeps its place between runs. A trail with no rules yet works as before: one owner, the rows of each file dealt between people in turn, like cards, starting from the top of your list, or the rep named in a column.

Mostly the words. Lead distribution usually means sharing leads out across a team, like round robin. Lead routing is the wider job: deciding who gets each lead by rules, such as its score, its source or who already owns the company. A trail does both in one list of rules.

Yes, with a Scorecard: points rules you write and can read, adding up to a score from 1 to 5. Each score sends the lead on, puts it in the review queue, holds it in Operelio, drops it or hands it to the routing rules. No model scores your leads.

A rule that names someone who isn't active in your CRM any more holds the lead on the Leads tab with that reason. Pick another owner or send it with no owner, and it goes on. A company owner or a column that names nobody active falls through to the next rule instead.

Yes. Each one is checked against Pipedrive, routed by your rules and made a person at its organization, with a deal if you turn deals on. Lists go to Pipedrive too, checked the same way.

In a trail's first week, every single lead waits for your yes or no. After that each lead runs on its own as it arrives, unless a rule or its score sends it to review. The Leads tab shows your speed to lead, from a lead arriving to it reaching its owner.

When a folder's webhook gets over 60 leads a minute or 1,000 an hour, the extra leads are gathered every 10 minutes into one run. That run uses one job and gets the same checks, scoring and routing as a list. The push still waits for your OK unless you let clean runs send on their own.

Only an admin can create or change a trail. Anyone on the workspace can review a held run and approve it.