Building a pipeline from scratch is fine for novel use cases, but most teams reach for a template - the platform ships with industry-tailored pipelines that drop the build time from days to minutes. This guide covers what's in the template library, how to fork one, and the common customisations.
What ships in the template library
- Real Estate transaction processing - document ingestion, title-deed extraction, regulatory checks, approval routing tuned for India + GCC markets
- KYC verification - identity verification, sanctions screening, risk scoring, audit-trail generation (Indian regulator + ISO 27001 controls)
- Invoice Processing - PO/GRN match, three-way reconciliation, ERP posting via the connector mesh, exception handoff to human reviewers
- Lead Qualification - inbound lead scoring, ICP fit + intent signal, auto-routing to the right rep based on territory rules
- Employee Onboarding - account provisioning, equipment dispatch, first-week scheduling, manager handshake email sequence
- Helpdesk Triage - inbound ticket classification, SLA assignment, knowledge-base-backed first reply draft, escalation rules
Forking a template
- Sidebar > Suites > Solution > Workflow Canvas > New from Template
- Pick the template; the platform copies the entire pipeline (every node, every edge, every guardrail) into your tenant as a fresh draft
- Renaming the forked pipeline is optional but recommended - prefix it with your team identifier so the original template stays clearly separate
Customising for your fields
The templates use generic field names (vendor_name, amount, customer_segment, etc.). Use the Field Mapping panel on each node to rebind to your tenant's specific schema - the names you use in your Enterprise App's TenantAppConfig. The platform validates the mapping at Publish time; mismatches show up as red dots on the canvas.
Common customisations we see
- Approval thresholds - the platform defaults are conservative (USD 10k for invoice approval); most tenants raise these to match their internal policy
- Routing rules - swap the platform's default territory matrix for your sales-ops version
- Notification channels - templates default to email + in-app; many tenants add Slack/Teams notifications on specific events
- Guardrail tightening - some tenants add extra content filters or per-vertical compliance checks (e.g., HIPAA-aware redaction for healthcare workflows)
When to roll your own from scratch
Templates work for ~80% of the cases we see. If your workflow is genuinely novel - say, a regulated process specific to your industry, or a multi-tenant orchestration across white-labelled accounts - start from blank canvas. The build is more work, but trying to bend a template into a fundamentally different shape usually costs more than starting clean.