Automate, clean and verify
lead flow into your CRM.

A trail is an automation you build once on a canvas. A file lands in a folder, the trail cleans it, verifies it, checks it against your CRM and pushes the rows into HubSpot, Salesforce or Pipedrive. After that it runs on every file that arrives, and every run is recorded.

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 them into the folder the trail watches, email them to the folder's own address from a sender you have allowed, or upload through the API. A trail can also run on a schedule: every day, weekdays, weekly, or every 6, 8 or 12 hours, in your time zone.

Not unless you ask for it. A new trail waits for you on every push. You can tell a trail to send clean runs on its own, and 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.

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. Verifying spends verify credits and a Bridgeant review spends one message. 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.

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.

Counts, column names and CRM field names. Never the values in your file. It reads the brief you wrote, 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 run stops and asks which sheet, unless you told the trail in advance. It is one of the seven checks that cannot be switched off.

The push is worked out again against your CRM as it is now before anything sends. If more than 10% of the rows would now do something different, 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.

Yes. Lead routing is part of the push: one owner for everything, round robin between the people you name, or the rep named in a column of the file. With round robin every run is dealt between them in turn, like cards, so each person gets an equal share and an odd row goes to whoever is top of the list. The owner is set on each record in the CRM as it is created or updated, and the push panel shows each person the share they would get from a real run.

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