Make (Integromat) Scenario Library
40+ production-ready Make.com automation scenarios organized by domain: e-commerce, marketing, finance, operations, and customer support. Every scenario includes error handling, logging modules, and detailed configuration guides so you can import and deploy in minutes.
Key Features
- 40+ ready-to-import scenarios across 5 business domains
- Error handling built in — every scenario includes error routes with notifications
- Connection-agnostic — swap in your own app connections without rebuilding logic
- Logging modules — each scenario logs execution data for debugging and audit trails
- Modular design — scenarios are composable; chain them for complex workflows
- Data mapping documentation — every field mapping explained with transformation notes
- Rate-limit aware — built-in delays and batching for API-heavy workflows
What's Included
| Category | Scenarios | Description |
|---|---|---|
| E-Commerce | 10 | Order sync, inventory updates, shipping notifications, refund processing |
| Marketing | 9 | Lead capture, email sequences, social posting, analytics collection |
| Finance | 7 | Invoice generation, expense tracking, payment reconciliation |
| Operations | 8 | Document processing, team notifications, data backup, reporting |
| Customer Support | 6 | Ticket routing, satisfaction surveys, knowledge base updates |
make-integration-library/
├── README.md
├── config.example.yaml
├── src/
│ ├── ecommerce/
│ │ ├── order_to_crm.json
│ │ ├── inventory_sync.json
│ │ ├── shipping_notification.json
│ │ └── ...
│ ├── marketing/
│ │ ├── lead_capture_to_email.json
│ │ ├── social_scheduler.json
│ │ └── ...
│ ├── finance/
│ │ ├── invoice_generator.json
│ │ ├── expense_tracker.json
│ │ └── ...
│ ├── operations/
│ │ ├── daily_report.json
│ │ ├── document_processor.json
│ │ └── ...
│ └── support/
│ ├── ticket_router.json
│ ├── satisfaction_survey.json
│ └── ...
├── examples/
│ ├── import_guide.md
│ └── chaining_scenarios.md
├── docs/
│ └── QUICKSTART.md
└── LICENSE
Quick Start
- Log in to Make.com and navigate to Scenarios
- Click "Import Blueprint" (the three-dot menu → Import Blueprint)
-
Upload the JSON file from the relevant
src/category folder - Configure connections — click each module and connect your accounts (Shopify, Slack, etc.)
-
Update variables — replace placeholder values using
config.example.yamlas reference - Run once with test data to verify the flow
- Turn on scheduling — set the scenario to run at your desired interval
Example: Order-to-CRM Scenario
{
"name": "Shopify Order → CRM + Notification",
"modules": [
{ "id": 1, "app": "shopify", "module": "watch_orders", "config": { "status": "paid", "limit": 10 } },
{ "id": 2, "app": "router", "routes": [
{ "label": "New Customer", "filter": "customer.orders_count = 1" },
{ "label": "Returning Customer", "filter": "customer.orders_count > 1" }
]},
{ "id": 3, "app": "airtable", "module": "create_record", "config": {
"base_id": "YOUR_BASE_ID", "table": "Orders",
"fields": { "Order ID": "{{1.order_number}}", "Customer": "{{1.customer.email}}", "Total": "{{1.total_price}}" }
}},
{ "id": 4, "app": "slack", "module": "send_message", "config": {
"channel": "#orders", "text": "New order #{{1.order_number}} — ${{1.total_price}}"
}}
],
"error_handler": {
"type": "break", "max_retries": 3,
"notify": { "app": "email", "to": "admin@example.com", "subject": "Make Scenario Failed: Order Sync" }
}
}
Configuration
# config.example.yaml
make:
organization: "your-org-name"
team: "your-team-name"
# Connection credentials (configure in Make.com UI)
connections:
shopify: { store_url: "https://your-store.myshopify.com", api_key: "YOUR_SHOPIFY_API_KEY" }
airtable: { api_key: "YOUR_AIRTABLE_API_KEY", base_id: "YOUR_BASE_ID" }
slack: { webhook_url: "YOUR_SLACK_WEBHOOK_URL" }
stripe: { api_key: "YOUR_STRIPE_API_KEY" }
google_sheets: { spreadsheet_id: "YOUR_SPREADSHEET_ID" }
# Scenario execution settings
execution:
max_operations: 100 # Per run (controls cost)
operation_delay_ms: 200 # Prevents rate limiting
log_retention_days: 30
# Error handling defaults
error_handling:
default_strategy: "break" # break, resume, ignore, rollback
max_retries: 3
error_notification: "email"
error_email: "admin@example.com"
# Scheduling presets
scheduling:
realtime: "immediately"
frequent: "every 5 minutes"
daily: "every day at 06:00 UTC"
Best Practices
- Always include an error handler — scenarios without error routes fail silently
- Use routers for conditional logic — cleaner than multiple filters on each module
- Add a Sleep module before API-heavy apps (Google Sheets, Airtable) to avoid rate limits
- Set "Max number of results" on every Watch module to prevent runaway executions
- Use Data Stores for deduplication — track processed IDs to avoid duplicate actions
- Test with "Run Once" before enabling scheduling — always verify with real data
- Monitor your operations count — each module execution counts against your plan quota
Troubleshooting
| Issue | Solution |
|---|---|
| Scenario stops after first module | Check that the Watch module has data and the connection is authorized |
| Duplicate records created | Add a Data Store to track processed IDs; filter out already-processed items |
| "Rate limit exceeded" errors | Add Sleep modules (1-2 seconds) between API calls to the same service |
| Error handler not triggering | Verify the error route is connected (orange line) — unlinked routes are ignored |
| Webhook not receiving data | Check that the webhook URL is active — Make deactivates after 5 days of inactivity |
| Data mapping shows "undefined" | Verify the field path — use Make's mapping panel to browse available fields |
This is 1 of 11 resources in the No-Code Builder Pro toolkit. Get the complete [Make (Integromat) Scenario Library] with all files, templates, and documentation for $29.
Or grab the entire No-Code Builder Pro bundle (11 products) for $129 — save 30%.
Top comments (0)