Entries are companies or contacts that already exist in Gleap — whichever the pipeline tracks. You're not creating new records, you're putting existing ones on a board.
The button at the top right of the board reads Add company or Add contact depending on what the pipeline holds. It opens a picker with two tabs, and a dropdown next to them that decides which stage everything lands in.
Search, tick the records you want, add them. This is the everyday path: an account signs, it goes on the onboarding board.
On company pipelines, searching also offers Add all results, which takes everything the search matches rather than only the rows you ticked.
The faster way to fill a new board. It works differently for the two record types.
For companies, you build conditions on the spot — name, plan, domain, value, last seen, created, country and city. The modal counts the matches as you type, so you see how many records the button is about to add before you press it.
For contacts, you pick a saved contact view instead of building conditions here. If the segment you want doesn't exist yet, save it in Contacts first.
At the bottom of the picker is Run automations for these companies (or contacts), and it is off by default. Leave it off when you're backfilling a board with accounts that are already halfway through the process — otherwise a welcome email fires at two hundred customers who onboarded months ago.
Turn it on when the add itself is the start of the process and the automation should treat it that way.
After a bulk add you get a count of what was added, plus two things worth reading:
“already on the pipeline” — those records were skipped. A record can appear on a pipeline only once, so re-running an add is safe and won't create duplicates.
“stopped at 1000 — there may be more matches” — a single bulk add tops out at a thousand records. Narrow the filter and run it again for the rest.
Every contact and company has a Pipelines tab listing the pipelines it's on and the stage it sits in, with Add to pipeline next to it. Only pipelines built for that record type are offered, and ones it's already on are left out.
A workflow can add a record to a pipeline when something happens, which is how a board stays current without anyone maintaining it. That has its own article.
The failure mode for pipelines isn't being empty — it's being full of things nobody is working on. Entries that stopped mattering don't remove themselves, and a board where half the cards are stale gets ignored entirely.
Deciding what leaves the board is as important as deciding what joins it, and it's worth agreeing before you add two hundred records to something new.
