Recipes
Don't wire up the pipeline. Start from a recipe.
Each recipe is a ready-made pipeline built from real Zapinner capabilities — a proven sequence of steps for a common data job. Install one into a project, tweak the steps if you want, and run it over the API, an SDK, or MCP.
CRM
2 recipesPrep and route leads so your CRM stays clean and every deal reaches the right queue.
- Standardize Lead Data
Trim stray whitespace and standardize company, email, and phone fields so every lead record follows one consistent format.
2 steps - Route Leads by Value
Normalize deal amounts, then assign each lead a destination queue by value so high-value deals go straight to sales and the rest to nurture.
2 steps
Customer Data
2 recipesCanonicalize and de-duplicate the people records your product depends on.
- Normalize Contacts
Bring names, emails, phones, and company names into a single canonical format — the reusable first step for any contact dataset.
1 step - Dedupe Contact List
Normalize contact fields, then collapse near-duplicate people (same name/company/email) into a single record so a list can be imported cleanly.
2 steps
Imports
2 recipesTurn messy spreadsheet and customer imports into clean, load-ready data.
- Clean Customer Import
Take a raw customer import, drop empty padding, coalesce a display name, and normalize contact fields into a clean, load-ready shape.
3 steps - Tidy Spreadsheet Export
Clean a messy spreadsheet export: trim cells, lowercase email columns, and coerce numeric columns to real numbers.
2 steps
Quality
1 recipeRaise the baseline quality of any dataset with dependable standardization passes.
Privacy
2 recipesDetect, mask, and redact personal data before it is shared, logged, or displayed.
- Protect Customer PII
Detect and mask sensitive values (email, phone, SSN, credit card) across customer records so the data can be shared or displayed without exposing identifiers.
1 step - Redact for Sharing
Replace any detected personal data with clear [EMAIL]/[PHONE] labels so records can be pasted into tickets, logs, or shared docs safely.
1 step
AI
2 recipesMake data consistent and safe before it reaches a model — and tag it for triage.
- Prepare Data for AI
Normalize records and strip personal identifiers (emails, phones) so a dataset is safe and consistent to feed into an AI model or embedding pipeline.
3 steps - Classify Support Notes
Read each record's free-text note and tag it with a best-fit category (renewal, complaint, question) so tickets can be triaged automatically.
2 steps
