What a trail pushes to your CRM

A trail pushes to one connected CRM, set on the push tile at the end of the chain. Your workspace can hold one connection per CRM. Each trail pushes one type of record, and rows are matched to records already in the CRM, as the table shows.

The push tile asks three questions about each row. The last only appears when matched records are updated.

The push tile has three tabs: What gets created, Who gets each lead and When it sends. Besides the questions below, What gets created sets what a single lead makes in your CRM. On Salesforce, a new person is a lead or a contact (a lead unless you change it). The lead's company is made, or found, unless you switch that off. A deal, an opportunity on Salesforce, is off until you pick a pipeline and an early stage; it is made for scores 4 and 5 unless you pick others, and for every lead on a trail with no Scorecard. A trail that pushes a list of deals uses the same pipeline and stage for every row, whatever its score. On HubSpot, each score can also set the contact's lifecycle stage.

Until these settings are saved, single leads wait in Operelio.

The Who gets each lead tab is a list of rules, first match wins, then Otherwise for every lead no rule picks. A rule tests one thing: a column of the lead's row, its Scorecard score, what the CRM check found (Already in the CRM, New person at an existing company, or New; for single leads and for files of people matched by email, and a row the check didn't reach matches no such rule) or where it came from, such as Webhook or Email, its location, or a free or blank email. Up to 50 rules; drag one by its grip, or use the arrow keys, to change the order.

Every lead shows which rule picked its owner.

On HubSpot, what the trail's mapping puts in Notes is added as a note on each contact the push creates. If your HubSpot has a Notes field of its own, it goes into that field instead. Attach a note also adds a column from the file as a note on each contact the push creates. When the mapping makes one too, both go into the same note. A blank cell adds nothing. On Pipedrive you do it in the formatting step instead: map the column to Notes, and the push attaches it as a note on each person or organization it creates. On Salesforce, and on HubSpot companies, a push attaches no notes.

Before a trail can switch on, an admin opens the formatter tile on the Sandbox tab, checks what it will send, and clicks Confirm this is what we send. Swapping the mapping, changing the CRM or the record type, or reconnecting the CRM clears this. A trail that is on stops, and someone has to confirm again and switch it back on. The one exception is signing in again to the same CRM account without disconnecting it first. That still clears the review, but the trail keeps running. If your CRM's fields change after a review, the formatter tile says so and offers Confirm again, and the trail keeps running.

The push policy decides what happens to a run with nothing flagged. Anything the safety checks or Bridgeant flag waits for you either way.

Just before it pushes, the trail checks the file against your CRM as it is then. It counts what it would create, update or skip, and what your CRM would refuse, and runs the safety checks on those counts.

If there is nothing to send, for example because every row is already up to date, the run finishes without pushing. If your CRM would refuse every row, the run fails.

If only part of a push lands, the run stops and says how many rows did not go. The run's page lists them, and Download the list gives you every row it can name (on HubSpot, the first 500). You cannot send just those rows again. An admin can edit a step before the push to send the whole file through again, and so can everyone if the workspace allows it. Rows that match a record already in your CRM then follow the trail's push settings.