CRM pipelines.

A pipeline is a board over the companies or contacts already in your Gleap workspace. Each pipeline has its own stages, custom fields, totals, and automations. Use the sales, customer onboarding, or renewals template - or start from a simple three-stage board and shape it as you go.

No. Pipelines run on the same companies and contacts your Gleap SDK already identifies, so records carry real context: plan, value, members, and conversation history. You can also add records manually in the dashboard or push them via the REST API.

Text, number, and currency fields (EUR, USD, GBP, and CHF). Each field can show a per-stage calculation - sum, average, min, max, or count - live in the board's stage footers and in the table view.

Pipelines plug into Gleap workflows with two triggers: when an entry is added and when its stage changes. Actions include creating a ticket, emailing the contact, notifying a teammate, moving the stage, setting a field, adding the record to another pipeline, calling a custom API, and passing to another workflow - plus conditions and delays.

Support tickets can be linked to pipeline entries in both directions. A pipeline entry lists its linked conversations, the ticket sidebar shows the customer's pipeline and stage, and you can create a follow-up ticket straight from an entry - or automatically on a stage change.

Standalone CRMs live next to your support stack and need constant syncing to stay truthful. Gleap pipelines run on the records your support platform already maintains, so the deal, the SLA, and the conversation are the same object. If you need deep sales ops like forecasting or sequences, a dedicated CRM still has its place - Gleap covers the customer-facing pipelines: sales, onboarding, and renewals.

Yes. The Gleap API exposes pipelines and entries, and the Gleap Admin SDK for Node.js ships helpers like getPipelines, addPipelineEntry, and updatePipelineEntry - so your product or billing system can move records through stages automatically.