Make (Integromat) Scenario Library
40+ Make.com automation scenarios for e-commerce, marketing, finance, and operations with error handling and logging.
📄 Product Preview
Try the interactive reader and demo tools below, or get the full product with all content unlocked.
📖 Interactive Reader (Free Preview) ⚙ Try Demo Tools 📦 Download Free Sample📁 File Structure 34 files
📖 Documentation Preview README excerpt
Make.com Integration Library
40 ready-to-import Make.com scenario blueprints covering e-commerce, marketing, finance, and operations workflows. Each blueprint includes complete module configurations, error handlers, data transformations, and scheduling — just import, connect your apps, and activate.
What's Inside
E-commerce (7 scenario files, 15 scenarios)
| File | Scenarios | Use Cases |
|---|---|---|
ecommerce-orders-fulfillment.json | 5 | Order notifications, inventory sync, shipping tracking, abandoned cart recovery, returns processing |
ecommerce-catalog-sync.json | 5 | Product sync, price updates, stock alerts, image processing, category mapping |
review-monitor.json | 1 | Route reviews by star rating to marketing (positive) or support (negative) |
fraud-screening.json | 1 | Score orders for fraud signals, alert on high-risk purchases |
review-request-sequence.json | 1 | Post-delivery review request emails with follow-up |
loyalty-points-tracker.json | 1 | Award points per purchase, track tiers, send milestone notifications |
supplier-purchase-order.json | 1 | Auto-generate POs for low-stock items, email suppliers |
Marketing (7 scenario files, 15 scenarios)
| File | Scenarios | Use Cases |
|---|---|---|
marketing-lead-capture.json | 5 | Form-to-CRM, webinar registration, social leads, lead scoring, newsletter management |
marketing-campaign-automation.json | 5 | Email sequences, social scheduling, campaign reporting, UTM tracking, A/B test analysis |
content-calendar-publisher.json | 1 | Publish scheduled blog posts from Google Sheets to WordPress |
referral-tracking.json | 1 | Track referral codes, attribute purchases, generate reward discount codes |
webinar-followup.json | 1 | Segment attendees vs no-shows, send appropriate follow-up emails |
competitor-price-monitor.json | 1 | Daily competitor price checks, alert on significant changes |
customer-winback.json | 1 | Identify lapsed customers, send tiered win-back emails with escalating incentives |
Finance (5 scenario files, 5 scenarios)
| File | Scenarios | Use Cases |
|---|---|---|
invoice-generation.json | 1 | CRM deal closed → create QuickBooks invoice → log to tracking sheet |
payment-reconciliation.json | 1 | Match Stripe payments to QuickBooks invoices, flag unmatched for review |
expense-receipt-processor.json | 1 | Scan Gmail for receipts, extract amounts, categorize, log to QuickBooks |
overdue-invoice-reminders.json | 1 | Graduated reminder emails (gentle → firm → final) with Slack alerts |
revenue-dashboard-sync.json | 1 | Weekly Stripe revenue aggregation, MRR/ARR calculation, dashboard sync |
Operations (5 scenario files, 5 scenarios)
| File | Scenarios | Use Cases |
|---|---|---|
standup-collector.json | 1 | Send async standup prompts via Slack DM, aggregate responses |
approval-workflow.json | 1 | Multi-level approval routing via Slack with SLA tracking |
onboarding-checklist.json | 1 | New hire → Asana project with templated tasks → welcome email → team announcement |
incident-response.json | 1 | Classify severity, assign on-call, create incident record, alert via Slack |
scheduled-report-generator.json | 1 | Pull from multiple sources, compile executive report, email + Slack |
Total: 24 scenario files containing 40 scenario blueprints
Quick Start
Importing a Blueprint
1. Open Make.com and go to Scenarios → Create a new scenario
2. Open the desired .json file from this library
3. Follow the module flow to build your scenario — each JSON describes every module, its parameters, mapper fields, filters, and error handlers
4. Configure your connections (each module will prompt you to authenticate the relevant app)
... continues with setup instructions, usage examples, and more.
📄 Content Sample guides/data-store-usage.md
Data Store Usage Guide
Make.com Data Stores are lightweight key-value databases built into the platform. Many scenarios in this library use data stores to track state between runs — abandoned cart status, drip campaign progress, approval records, loyalty points, and more.
This guide covers creation, schema design, and common patterns.
What Data Stores Solve
Make.com scenarios are stateless by default — each run processes new data without remembering what happened in previous runs. Data stores add memory:
- Deduplication: "Have I already processed this item?"
- Multi-step workflows: "Which step is this contact on in the drip sequence?"
- Accumulation: "What's this customer's total loyalty points?"
- Coordination: "Has an approver responded to this request?"
Creating a Data Store
1. In Make.com, go to Data stores in the left sidebar
2. Click Add data store
3. Enter the name — use the exact name referenced in the scenario (e.g., abandoned_cart_tracking)
4. Set the data structure — see schema definitions below
5. Set the data store size — the free tier includes 1 MB storage; most tracking use cases fit easily
Defining the Schema
When you create a data store, you define its fields (called a "data structure"):
1. Click Add to create a new data structure
2. Name it (e.g., "Abandoned Cart Schema")
3. Click Generator and paste a sample JSON object to auto-detect fields, OR manually add fields:
- Name: Field identifier (e.g.,
checkout_id) - Type: Text, Number, Date, Boolean, Collection, Array
- Required: Whether the field must have a value
- Default: Value to use if not provided
Example: Creating the Abandoned Cart Tracking Store
Name: abandoned_cart_tracking
| Field | Type | Required | Notes |
|---|---|---|---|
checkout_id | Number | Yes | Used as the record key |
email | Text | Yes | Customer's email address |
cart_value | Number | No | Total cart value in dollars |
first_email_sent | Boolean | Yes | Default: false |
second_email_sent | Boolean | Yes | Default: false |
first_sent_at | Date | No | When the first reminder was sent |
second_sent_at | Date | No | When the discount follow-up was sent |
... and much more in the full download.